Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inherited scene saving parent nodes in incorrect order #3945

Closed
Tracked by #4778
bojjenclon opened this issue Mar 6, 2016 · 3 comments
Closed
Tracked by #4778

Inherited scene saving parent nodes in incorrect order #3945

bojjenclon opened this issue Mar 6, 2016 · 3 comments
Milestone

Comments

@bojjenclon
Copy link

I created a basic "template" level scene with the following node hierarchy:

Level
  -> Player
    -> Shapes

I then created a new scene that inherits from this template scene. When I add a new Shape to the Player/Shapes node, it appears to be added correctly in the editor. However, if I try to run the scene it throws an error (without any text) in the debugger and doesn't display the shape. Upon inspecting the tscn file, I noticed the shape's parent is set as "Shapes/Player" when it should be "Player/Shapes."

Also, if I save the scene, close it, and reopen it, the shape is gone from the scene (likely due to it not knowing where to place it).

This exact same setup works perfectly fine in an identical scene I set up that doesn't use an inherited template scene as its base.

@akien-mga akien-mga added this to the 2.1 milestone Mar 6, 2016
@DriNeo
Copy link

DriNeo commented Mar 7, 2016

I found an error without text on a inherited scene too.

inhsceneerr

@bojjenclon
Copy link
Author

I went back and looked at it again, and I realized I had the base scene saved as a .tscn with the child scene saved as a .scn. That could potentially have been part of the issue. However, I feel this shows that there really needs to be a "default scene format" option so users don't have to always remember to add the "t" when saving their scenes.

Edit: Scratch that, problem persists regardless of file type.

@reduz
Copy link
Member

reduz commented Jun 26, 2016

this was fixed recently

@reduz reduz closed this as completed Jun 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants