Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
8
Found in
4.6.0p1
Issue ID
653948
Regression
No
GetSiblingIndex always returns zero in standalone builds
To reproduce:
1) Open the test scene in editor
2) Start the play mode and see the sibling index is 1.
3) Build the project and run it.
4) Notice the sibling index is zero
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
kotoezh
May 07, 2024 12:20
Still exists in 2022.3.21f1 LTS.
Causes bugs with Mirror Network when sorting spawn positions by their sibling index.
Demigiant
Oct 03, 2015 09:12
Also, SetSiblingIndex is not working for objects in the root (Unity 5.2.1)
Xtro
May 16, 2015 16:15
This bug is really annoying me for many many months and it disrupts my workflow :( :(
Xtro
Jan 26, 2015 16:18
I reported this bug but the title says something missing.
It returns zero for only scene root objects. It works good for non-root objects.