It was mentioned in the forums that the issue has been corrected in the latest developer build, with a manual fix also posted by a member of our community. It's ultimately up to you if you prefer to wait for the fix to be implemented in the next actual release. Thanks.