self.IsFalling Priority

Post your Feature Requests here...
Post Reply
User avatar
Markman
Posts: 21
Joined: Sat Jan 14, 2006 2:28 pm

self.IsFalling Priority

Post by Markman »

Is it possible to give the special Variable self.IsFalling a higher update-priority ?

So that the system checks more often if the Pawn has landed.
At the moment, I did not find a way to play a landing Animation in time.
There is always a gap of nearly a whole second.

Or maybe it is possible to check the Distance to the ground structure via a new Script-Variable. At the moment it is already possible to check for the Texture under the Pawn, but for the Distance...?
Jay
RF Dev Team
Posts: 1232
Joined: Fri Jul 08, 2005 1:56 pm
Location: Germany

Post by Jay »

I don't know but it could be that the script does not check every frame for a landing.
if you'Re in LowLevel,
change self.ThinkTime to
self.ThinkTime=0.01;
if this problem still occours then i think you're right.
Everyone can see the difficult, but only the wise can see the simple.
-----
User avatar
Markman
Posts: 21
Joined: Sat Jan 14, 2006 2:28 pm

Post by Markman »

It happens in a single looping Low Level Order with 6 Lines.
I never had use for the self.ThinkTime, cos most of the time the scripts are already tending to be slow. Which can be seen in Movements and Rotations.

Maybe for a controler script, with extremely low priority, I guess I would use self.ThinkTime.
User avatar
Ransom
Posts: 30
Joined: Sat Jan 14, 2006 7:16 pm

Post by Ransom »

I had difficulting getting smooth results with self.IsFalling as well. But I think the problem is not how often the command is updated, but rather what is considered "falling" or not. Try placing a - if(self.IsFalling) = do whatever - command in your character's walk cycle, you'll find the pawn "falling" when you'd thought it was touching the ground.
User avatar
Juutis
Posts: 1511
Joined: Thu Jan 12, 2006 12:46 pm
Location: Finland

Post by Juutis »

For me it works perfectly. I've set self.ThinkTime = 0 so it will check every frame if it has landed. And please let me know if I'm wrong, but I think if you want to be sure of these things, you should have a "self.ThinkTime = ..." line in every lowlevel order.

Another solution: there is a command that checks for the collision distance between the pawn (or a bone of the pawn??) and a specified point. So you could check if the distance between the pawn and a point directly downwards of him is less than X texels.
Pain is only psychological.
Post Reply