Open arnuschky opened 10 years ago
CAAT seems to require that actors are rendered (setVisible / setFrameTime) well beyond the end of the last behavior.
If you call setVisible(false) directly at or shortly after the end of an animation, CAAT will get into an inconsistent state:
actorBehavior.setFrameTime(scene.time, 1000); actor.setFrameTime(scene.time, 1000);
causes the problem, while
actorBehavior.setFrameTime(scene.time, 1000); actor.setFrameTime(scene.time, 1010);
seems to work fine. (Same result when using a timer and setVisible(false))
CAAT seems to require that actors are rendered (setVisible / setFrameTime) well beyond the end of the last behavior.
If you call setVisible(false) directly at or shortly after the end of an animation, CAAT will get into an inconsistent state:
causes the problem, while
seems to work fine. (Same result when using a timer and setVisible(false))