Search Issue Tracker
Fixed
Fixed in 2.0.0
Votes
0
Found in [Package]
2.0.0
Issue ID
MTTB-1617
Regression
No
Play Mode Scenarios are not ordered correctly
Reproduction steps:
1. Create a new project
2. Open Package Manager (Windows > Package Management > Package Manager)
3. Install Multiplayer Play Mode package
4. Open Play Mode Scenarios window (Window > Multiplayer > Play Mode Scenarios)
5. Keep pressing “+” button to create a lot of new Play Mode Scenarios and observe their ordering in the window
Actual result: Play Mode Scenarios are ordered by the first digit in their name (e.g. (1),(10),(11),(12)…)
Expected result: Play Mode Scenarios are ordered by numeric sequence (e.g. (1),(2),(3)…)
Reproducible with: 1.3.2 (6000.0.25f1), 1.6.1 (6000.0.59f1, 6000.2.7f1), 2.0.0-pre.1 (2021.3.57f1, 2022.3.67f1, 6000.3.0b4, 6000.4.0a1)
Couldn’t reproduce with: 1.3.1 (6000.0.25f1) (No Play Mode Scenarios window)
Reproduced on: macOS Sequoia 15.4 (M4), Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment