Opened 17 years ago

Closed 14 years ago

Last modified 14 years ago

#178 closed task (fixed)

Decouple entity simulation and actor animation

Reported by: Philip Taylor Owned by:
Priority: Should Have Milestone:
Component: Core engine Keywords:
Cc: Patch:

Description

Let the entity code simply tell the actor to switch to a certain animation state, and not worry about any timing details itself. The actor should handle looping, randomisation, and potentially things like blending. The animation speed should be determined just by the actor XML.

Change the entity XML files to store only a Rate (units per second) for actions, rather than Speed+Rate. Update the simulation world at a fixed frequency, independent of the animation speed.

Experiment with the same for attack animations to see if it still looks alright, but at least keep projectile launches synchronised.

Change History (3)

comment:1 by Philip Taylor, 17 years ago

See r4880. Still need to change entities to use Rate where possible, and to run animations at a speed dependent only on the actor (not on the entity).

comment:2 by Philip Taylor, 14 years ago

Resolution: fixed
Status: newclosed

New simulation system takes a slightly different approach to this - see AnimationSync.

comment:3 by (none), 14 years ago

Milestone: ASAP

Milestone ASAP deleted

Note: See TracTickets for help on using tickets.