Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0
Issue ID
UBRMPPM-20
Regression
Yes
Virtual Player times out when using system regions that use the ',' symbol as a decimal point
How to reproduce:
1. Make sure to set the system region to one that uses the ',' symbol as a decimal point
2. Open the “VirtualPlayerTimeoutJSONIssue“ project
3. Open the Multiplayer Play Mode window (Window > Multiplayer Play Mode)
4. Create a new Virtual Player
Expected result: A new Virtual Player is created
Actual result: No Virtual Player is created, the “Timeout reached for client message ‘OpenPlayerWindowMessage’” warning is thrown and a “UnityException: SJSON Parse Error (memory)” error is thrown in the Virtual Player
Reproduced with: 1.0.0 (6000.0.0b14)
Not reproduced with: 0.6.0 (2023.2.18f1, 6000.0.0b14) 1.0.0-pre.4 (6000.0.0b14)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Full error and warning logs are provided in the internal comments
2. Reproduced with the system region on Windows set to “France (Canada)”
3. Not reproducible after upgrading the Multiplayer Play Mode package from an older version
4. Sometimes the reproduction can be inconsistent and might require the “Library” folder to be deleted
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Resolution Note:
Will be fixed in 1.1.0