|
I’d like to get some insight in why these sort of things happens:
Pseudocode
1. FBGotToFrame(10);
2. int xValue = character.GetPositionX();
Switching to a frame on the timeline(row 1) and ask for a certain value(row 2). Motionbuilder will be able to evaluate row 2 before row 1 has finished executing, giving me the wrong value.
I’ve found alot of situations where this happen, but the question is why does this happen? Is it due to Motionbuilder being very “thread-heavy” and this i caused because the two rows are evaluated in different threads?
Most of these i’ve been able to get passed by going another way where in don’t have to ask motionbuilder to do something for me… So no need for answers how i solved this specific problem.
|
|
|
|
Change frame in python won’t automatically invoke the scene evaluation. You need to call FBScene.Evaluate() to ensure the animation get updated.
|
|
|
