You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
I created a basic "template" level scene with the following node hierarchy:
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.
The text was updated successfully, but these errors were encountered: