Forum rules - please read before posting.
Remember Moveables bug with nested moveables
Hi Chris,
I believe I encountered a loading bug with nested moveables.
I have Moveable A and a child Moveable B.
On both Moveables is a RememberMoveable component.
I move the Moveables by a relative amount.
When loading Moveable B (the child) is not on the correct position. It seems like it loads the world position of B before A, so when Moveable A is loaded it offsets the nested B.
A fix could be to save the local position instead of the global position. Makes sense?
AC Version 1.75.4, Unity 2020.3.33f1
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
Welcome to the official forum for Adventure Creator.
Comments
Any additional details you'd like to share of your situation would help fully understand things, but yes - it does make sense.
Remember components aren't processed in a particular order - it might be that another situation has A load before B.
You can test out the change by manually replacing the RememberMoveable script's .position mentions with .localPosition, but I agree on the need for such an option officially.