This issue should be fixed in the newest hotfix v.0.1.1 . Thank you for bringing this to my attention!
