Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.6.0b2
Issue ID
589792
Regression
No
SetAsFirst actually moves it to the last position (index childCount-1), and SetAsLast moves it to the first position (index 0)
To reproduce:
1. Open project, load Scene, there should be a Main Camera with 4 GOs inside (A, B, C, D)
2. Open Custom->Open to show the editor window
3. Click Set As First, notice how it actually sets it as the last (index childCount-1)
4. Click Set As Last, notice how it actually sets it as the first (index 0)
Expected result: SetAsFirst/SetAsLast should set it as first/last
Actual result: SetAsFirst/SetAsLast sets it as the last/first
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment