Hi @Aegarain - I believe this issue should have been fixed with the release of version 1.3.1.2. Can you verify whether this is still an issue? Thanks!
