02-12-2014, 05:51 PM
Sorry for the late reply!
I can confirm this bug has been fixed in current stable version 1.3.0s1121.
Thanks a lot!
I can confirm this bug has been fixed in current stable version 1.3.0s1121.
Thanks a lot!