Search Issue Tracker
Fixed
Fixed in 6000.5.0b7, 6000.6.0a4, 6000.6.0a5
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"
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.6.0a4):
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.5.0b7):
Fixed in 6000.5.0b7