Triggers, preemptive?
by Phillip O'Shea · in Torque Game Builder · 09/15/2007 (3:19 pm) · 3 replies
I just found something interesting in my work.
I knew collisions were preemptive, but so too are triggers? If not, then I don't know how to explain the weird bug I get.
I've been using triggers for one way platforms, everything works fine when I jump from below, but when I land on the top it acts wacky. It will enable and disable the platform continuously, while the player does not move at all.
When I find the coords of the player's feet, I find that he is actually *above* the top of the trigger's collision box. To rectify this, I just check to see if the player is within the bounds of the trigger, but I find it messy that there is a continuous collision with the trigger.
Does anyone know how I could rectify this, other than moving the trigger down?
I knew collisions were preemptive, but so too are triggers? If not, then I don't know how to explain the weird bug I get.
I've been using triggers for one way platforms, everything works fine when I jump from below, but when I land on the top it acts wacky. It will enable and disable the platform continuously, while the player does not move at all.
When I find the coords of the player's feet, I find that he is actually *above* the top of the trigger's collision box. To rectify this, I just check to see if the player is within the bounds of the trigger, but I find it messy that there is a continuous collision with the trigger.
Does anyone know how I could rectify this, other than moving the trigger down?
About the author
Head of Violent Tulip, a small independent software development company working in Wollongong, Australia. Go to http://www.violent-tulip.com/ to see our latest offerings.
#2
09/15/2007 (11:58 pm)
Don't you think its a bid silly having collisions process prior to intersection though? 
Torque Owner DragonSix