07-03-2014, 09:56 PM
(07-03-2014, 09:52 PM)Ramond Wrote: I myself believe as well that wait: 0 represent a 1-frame duration, wait: 1 will take 2 frames, wait: 2 will last 3 frames and so forth. I cannot back this up with hard proof sadly, but I recall that when coding certain timing-critical moves in RAEG! LF2, it always worked out when I calculated the total frame time with the above.
I am pretty sure that's how it works too. Also, quoting my edit of my previous quote so no one misses it:
(07-03-2014, 09:32 PM)A-MAN Wrote: So what wait: value will have a frame wait for exactly 1 second?
Edit: http://www.lf-empire.de/lf2-empire/data-...characters
Got my answer (wait:29 makes a frame last one second as I thought).
Then either, wait:0 ==1/30th of a second, or LF2 doesn't run at 30 FPS. Supposing its the first, then a (1/30)*3 != (2/30), right?
![[Image: signature.png]](http://s3.postimg.org/wedqxlk3n/signature.png)
A-Engine: A new beat em up game engine inspired by LF2. Coming soon
A-Engine Dev Blog - Update #8: Timeout