Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.3.2f1
6000.4.0b2
6000.5.0a3
Issue ID
UUM-130714
Regression
No
Section separator renders in the wrong place in Search Journaling and Archetypes windows
Reproduction steps:
1. Create a new project
2. Install Entities package in Package Manager
3. Window > Entities > Journaling
4. Press Search Journaling button which is next to Toggle details view button in the Journaling window
5. Observe Search Journaling window separator
6. Window > Entities > Archetypes
7. Observe Archetypes window separator
Actual result: Section separators appear in a random place in both Search Journaling and Archetypes windows
Expected result: Section separators appear in between sections
Reproducible with: 1.4.3 (6000.0.64f1, 6000.3.2f1), 6.4.0 (6000.4.0b2), 6.5.0 (6000.5.0a3)
Reproduced on: Ubuntu 24.04, macOS Tahoe 26.1 (M4)
Notes:
- Issue in Search Journaling window only reproduces for the first time
- Issue is not reproducible on other Editor windows
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.