0 Members and 1 Guest are viewing this topic.
Hi King, I had the same issue - it is a known bug on a previous build.If you update to the latest release, this bug is fixed
I use the BETA (otherwise known as "unstable") release