I just tried it on v5.2.2.0.b and it still happens. I have reverted to v5.1.4 and am no longer having the issue. I guess I’ll be using this version until it gets fixed in a future update.
I just tried it on v5.2.2.0.b and it still happens. I have reverted to v5.1.4 and am no longer having the issue. I guess I’ll be using this version until it gets fixed in a future update.
