Search Issue Tracker
Fixed
Fixed in 6000.5.0a7
Votes
0
Found in
6000.0.66f2
6000.3.6f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133606
Regression
No
“Client And Server” shown without spaces in Active Scenario window
Steps to reproduce:
1. Create new Unity project
2. Open Multiplayer Center window (Window > Multiplayer > Multiplayer Center)
3. Select Game Specifications (for example, Genre of your Game - Adventure, Number of Player per Session - 2)
4. Once installed, open Play Mode Scenarios window (Press on “Default” button next to Play Mode Control buttons > Configure Play Mode Scenarios)
5. In Play Mode Scenarios window press “” to add Play Mode Scenario
6. In “Additional Editor Instances” press “”
7. In Multiplayer Role, select “Client And Server”
8. Open Active Scenario window
9. Observe Player 2 section in Active Scenario window
Actual results: “Client And Server” is missing spaces in Active Scenario window, show as “ClientAndServer”
Expected results: “Client And Server” is missing not spaces in Active Scenario window, show as “Client And Server”
Reproducible with versions: 6000.0.66f2, 6000.3.6f1, 6000.4.0b7, 6000.5.0a6
Tested on (OS): Ubuntu 24.04, macOS Silicon Tahoe 26.2 (M1)
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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7