Why are scenes non-unique?

Bobit

Just came across this. As I understand this means that I can edit an instanced scene's root node as much as I want, but the instant that I modify any of its children, even via a script, it has to affect all other instances of that scene.

So if I have a Person scene, I cannot move its arms separately from another person's arms. Am I doing something wrong here? Exactly how do Inherited scenes and Instanced scenes differ? I could explain how this relates to my code in detail, but it's so complex...

Bobit

Alright here's my problem:

The big ring reveals enemies. The little ring damages enemies. Both are set to adjust their child Area node's size (specifically $Area/Collision.shape.radius) to their size in their ready() function. But as you can see, both damage and vision take the larger radius, apparently because both share the same Area child because that's how instanced scenes work. Furthermore, if I move the damage node down on the tree, it uses the smaller ring for both damage and vision, because the damage node is loaded after. Is there no workaround to this?

Bobit

SOLVED. Apparently the solution was to check the "local to scene" box on $Area/Collision.shape. Apparently instanced scenes use the same_subresources_, but make copies of their nodes.

I would still like a detailed description of what instanced scenes share though. Is there any way I can tag this post as answered, or does a mod need to do that?

TwistedTwigleg

@Bobit said: ... Is there any way I can tag this post as answered, or does a mod need to do that?

I changed this topic from a discussion to a question. Now you should be able to mark any of the posts as the answer :smile: