Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0b1
6000.6.0a1
Issue ID
UUM-137992
Regression
No
Column order resets after switching filters in Lighting Search window
Reproduction steps:
1. Create a project
2. Window > Render > Lighting Search
3. Click “Toggle Saved Searches Panel” button in the Lighting Search window
4. Select any search filter
5. Change the order of the columns
6. Select a different filter and then return to the previous one
Actual result: Column order resets to its default arrangement
Expected result: Column order remains the same
Reproducible with: 6000.5.0a7, 6000.5.0b1, 6000.6.0a1
Couldn’t reproduce with: 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0a6 (No Lighting Search window)
Reproduced on: macOS Sequoia 26.2 (M4)
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.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.