Posts: 1,556
Threads: 77
Joined: May 2011
07-08-2014, 04:46 PM
(This post was last modified: 07-08-2014, 04:57 PM by A-Man.)
Exactly. Apparently, opointing happens somewhere before the "UpdateStats()" function too. While my anticipated algorithm agrees that there shouldn't be any collision there either, we (actually you since I couldn't get the FPS changer to work :P) can't quite prove that yet; since the spark might take one frame to actually appear; thus it would look as if the second frame caused it. One thing you can do is give the first frame a next:1000 and see if it works (that wouldn't be a solid proof too, because an object might need a frame to completely delete itself from the scene).
Edit: V: That's what we've been saying.
Thanks given by:
Posts: 233
Threads: 13
Joined: Oct 2008
It seems like one frame, but keep in mind that the first TU of an attack isn't really shown. I used Someone Else's one-frame pause trick to test this out. You have to at least use wait:1 for the first frame for it to show.
To live a life of power, you must have faith that what you believe is right, even if others tell you you're wrong.
The first thing you must do to live a life of power is to find courage. You must reach beyond the boundaries of time itself.
And to do that, all you need is the will to take that first step...
Ask not what others can do for you, but what you can do for others.
Thanks given by: