Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137246
Regression
No
Some Lighting Search premade filters are not ordered correctly
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Rendering -> Lighting Search
3. Click the "Toggle Saved Searches Panel"
4. Go to Lighting Settings -> Max Lightmap Size
5. Observe the order of filters
Expected results: The order is "32 - <256", "256", "512" and etc.
Actual results: The order is "1024", "2048", "256" and etc.
Reproducible with: 6000.5.0a9, 6000.6.0a1
Can't test with: 6000.0.71f1, 6000.3.11f1, 6000.4.0b12 (No Search integration)
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: Reproducible with the majority of the queries under the "Lighting Settings"
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