I should add that I tested it after the 1.0.47 patch, and the issue persists.