Thanks for the report!
The issue should have been addressed with the recent 1.4.1 patch.
If it should still happen to you, please let me know.
The issue should have been addressed with the recent 1.4.1 patch.
If it should still happen to you, please let me know.