Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.5.0a9
6000.6.0a1
Issue ID
UUM-136892
Regression
No
Column reordering indicator line is offset when dragging "Flare" column in Lighting Search window
Steps to reproduce:
- Create a new project using Universal 3D template
- Go to Windows > Rendering > Lighting Search
- Click on the "+" button and add "Flare" column
- Click and drag the Flare column header to change its position in the table
- Observe the blue line that indicates where the column will be placed
Actual results: The blue indicator line is visibly offset from the column edge, giving an incorrect impression of where the column will be placed
Expected results: The blue indicator line is aligned with the column edge and appears exactly where the column will be dropped
Reproducible with versions: 6000.5.0a9
Can’t test with versions: 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a7 (Flare column option not available)
Tested on (OS): Windows 11
Notes:
- Additionally, the Flare property does not seem to be the correct size or type, because it should have a field for attaching GameObject but object picker is not visible
- Sometimes this makes dragging other columns also have an offset indicator, or sometimes it fixes itself
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:
Backlog cleanup:
- No bandwidht for these minor cosmetic issue
- I tried to repro on my side but wasn't able to. I guess it is not related to the Flare column directly and that the behavior (or repro steps) are not 100% accurate.
Resolution Note (6000.6.X):
Backlog cleanup:
- No bandwidht for these minor cosmetic issue
- I tried to repro on my side but wasn't able to. I guess it is not related to the Flare column directly and that the behavior (or repro steps) are not 100% accurate.