Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.6.0a2
Issue ID
UUM-137849
Regression
No
Hierarchy v2: Reordering scene nodes issues
Scenario 1 repordering in-memory scene
Steps to reproduce:
- Add a new in-memory scene by right click an existing scene header
- Try to reorder this in-memory scene
Actual results: in-memory scene barely moves
Expected results: user should be able to move/reorder in-memory scenes
-Scenario 2 repordering scenes when searched/filtered-
-Steps to reproduce:-
- -Load multiple scenes in hiearchy-
- -search for a common letter to allow all scenes appear-
- -reorder scenes-
-Actual results: scene fail to move and appear undraggable-
-Expected results: user should be able to move/reorder scenes-
Reproducible with versions: 6.3 and up
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): mac
Notes:
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