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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment