Search Issue Tracker
Fixed
Fixed in 6000.4.0b5, 6000.5.0a5
Votes
0
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131454
Regression
No
Long Player Tag names overlap text in Active Scenario window
Steps to reproduce:
1. Create new Unity project
2. Open Multiplayer Center
3. Select Genre of the Game > Arcade, Platformer, Sandbox and Number of Players per Session > 2
4. At the bottom right corner press “Install Packages”
5. Open Project Settings window
6. Select Multiplayer > Playmode section
7. In the Player Tags > List create a new tag pressing “+” button
8. Add a Tag named “TestingTagNamingTestingTagNamingTestingTagNamingTestingTagNaming”
9. Save the Tag Name
10. Close Project Settings window
11. Press on “Default” button in Play Mode controls
12. From the menu select “Configure Play Mode Scenarios”
13. Create a new Play Mode Scenario
14. Once created, add a newly created tag in Editor > Tag in Play Mode Scenarios window
15. Open “Active Scenario” window (Window > Play Mode > Active Scenario)
16. Observe Tag in Active Scenarios window > Main Editor section
Actual results: Long tag names overlap text in Active Scenario window
Expected results: Long tag names should be truncated and text should not overlap in Active Scenario window
Reproducible with versions: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Tested on (OS): macOS Tahoe 26.1 (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
- 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
Resolution Note:
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5