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
7
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
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
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.