BUG: Cloned parent actors aren't behaving in a compiled app even when unlocked!
synthesis
Member Posts: 1,693
We have apparently uncovered a small (but illusive) bug in the parent-child actor relationships.
Our example:
I built a simple actor called "button" which had some basic button type rules in it. I then use this actor and then unlock it and modify it as needed for a button in the scene.
Well...when I used it once as a static image actor, where I inserted a static image, changed its size and then unlocked it and deleted ALL of the parent rules and behaviors to an empty actor...it began taking on the behaviors of the parent seed - even though the actor was entirely void of rules or behaviors.
The actor works correctly in both the editor preview and the player but once compiled - the button behavior develops even though the actor should have no function.
Our example:
I built a simple actor called "button" which had some basic button type rules in it. I then use this actor and then unlock it and modify it as needed for a button in the scene.
Well...when I used it once as a static image actor, where I inserted a static image, changed its size and then unlocked it and deleted ALL of the parent rules and behaviors to an empty actor...it began taking on the behaviors of the parent seed - even though the actor was entirely void of rules or behaviors.
The actor works correctly in both the editor preview and the player but once compiled - the button behavior develops even though the actor should have no function.