Bug : GetSiblingIndex always returns zero on scene root game objects in build runtime.

Unity Engine
1

I reported this bug via Unity bug reporter tool long time ago but it was never fixed.

Bug record:
http://fogbugz.unity3d.com/default.asp?653948_lhpsonb8akqhg7n7

Issue tracker:

Bug description:
GetSiblingIndex always returns zero on scene root game objects in build runtime.

It’s working good for parented objects.
In editor play mode runtime, it’s working perfect for both root and parented objects. The only problem is in build runtime for only root objects.

Steps: (test project was included in bug record when I reported it via bug reporter tool)

  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 which is a huge bug!!!
Runtime Inspector and Hierarchy [Open Source]
2

Can I get attention from a Unity Team member please? :slight_smile:

3

Bump :frowning:

4

It’s been days but I couldn’t get any response from the Unity Team :frowning: :frowning:

5

Hello… I’m talking about a serious API bug here.

6

Since you sent this a while ago, have you verified this is still reproducible in the latest patch? Download Archive

7

I verified it with 4.6.1p2 but I did’t see any patch note about it for the other patches. Also, my bug report record is still “open”

Do you want me to verify it on 4.6.1p4?

And, why can’t I find this bug in issue tracker?

8

Yes please if you could just to make sure.

I actually had passed this on but let me give the guys another gentle prod.

9

Verified. It still exists in 4.6.1p4

10

Will I be able to see it in issue tracker soon? Because trying to track it on the forum is not so cool :slight_smile:

11

I know Unity team is very busy but…
Can I get an update about this serious API bug?
I reported it months ago. :frowning:

12

Here is the issue tracker link, you can use your bug number to search in the Issue Tracker Unity Issue Tracker - GetSiblingIndex always returns zero in standalone builds

It’s currently still an active bug.

13

This is a serious API bug and it’s not being fixed :frowning: :frowning:
It’s been almost a year since I reported this bug. Please give some priority to this bug…!!

14

Also, SetSiblingIndex is not working for gameObjects in the root (Unity 5.2.1)

15

Can we get an update from UT please? Is there a specific reason for ignoring this very obvious API bug?

16

Its not being ignored. I will poke the core team on Monday and see what the status is.

Can you file a bug report for this please.

17

Done. Case 733344.

1 Like
18

@karl_jones

Were you able to poke the core team about the status?

19

Sorry Yes I was. Its not actually a bug as such, its using editor only features and so disabled at run time. We basically have a scene root object that does not exist outside of the editor. This could potentially be addressed with the future changes being made to the scene system at the moment but its not something that can be quickly fixed. Its now back with the core team to look at. As a workaround whilst you wait you could create a single GameObject as a scene root if you needed to replicate the behavior.

20

That’s very bad to hear :frowning: Yes I’m aware of the workaround which is very ugly :frowning:

Btw, why would a runtime API would use editor feature by default?