There was an issue introduced with patch 1.6.2, we've rolled it back to 1.6.0 until we fix the issue.