Hello,
This seems to have been fixed together with another similar issue, i am unable to reproduce it in the latest test build.
Thanks for the report!
This seems to have been fixed together with another similar issue, i am unable to reproduce it in the latest test build.
Thanks for the report!