I have the same error, it most likely has something to do with patch 2.1