Reply To: Possible [BUG] Transform.SetParent Methods not keeping global orientation

[holoreel]

*Solved*

I believe I finally tracked down what was exactly happening and its not a Setparent issue (thank you for responding) or losing reference to GlobalBlackboard like my above post suggested but turned out to be a very small execution timing change that is effecting my project in this new Node Canvas build.

My scene is procedural so once its generated and then rendered at runtime, the Setparent asset behavior was suppose to come in and reparent certain game objects before other behaviors continue through the rest of the loading process.

Originally the Setparent asset behaviours had a simple condition to only run once it was active and that has served me well as a safeguard for the assets execution order up until now.

It seems somehow with the latest update however the reparent asset behaviours were getting ahead of themselves and reparenting game objects before my procedural generator had a chance to render them and thus every game object would come up with global transform position of 0,0,o regardless as to whether WorldPositionStays was checked or not.

I did a temporary fix by just adding 0.5 sec wait time before the reparenting asset behaviour begins and now generator has time to generate and render scene first and then the reparenting asset begins and grabs the correct global orientation and works correctly.

No idea why the change occurred exactly as the update was the only thing that changed in my project but glad to get back on track.  Anyways sorry about the two previous shots in the dark as to what was happening and thanks again for checking Setparent execute function.

 

Thanks.