Triggers
by Xavier "eXoDuS" Amado · in Torque Game Engine · 04/11/2002 (10:54 am) · 12 replies
I created my own trigger element, called CapturePoint, but if i place two of these only one of them works, the other one is completely ignored, ie, the Trigger::onEnterTrigger() function is never called (im talking about the parent trigger function) :(
Anyone have any ideas what's needed?
Anyone have any ideas what's needed?
About the author
#2
Obviously we're either doing the same thing incorrectly or we're doing the same thing and the engine isn't behaving the way we expect.
I'll investigate this further and post what I find within the next hour or two.
04/14/2002 (1:03 pm)
Hrm, I thought I was the only person having this problem, but I guess I'm not.Obviously we're either doing the same thing incorrectly or we're doing the same thing and the engine isn't behaving the way we expect.
I'll investigate this further and post what I find within the next hour or two.
#3
When triggers are created, the polyhedron which identifies the shape of the trigger should be:
polyhedron = "0 0 0 1 0 0 0 -1 0 0 0 1";
but at times it is something like:
polyhedron = "0 0 0 1 0 0 0 0 1 0 -1 0";
I'm not sure what causes this problem. If you replace the line in the offending trigger with:
polyhedron = "0.0000000 0.0000000 0.0000000 1.0000000 0.0000000 0.0000000 0.0000000 -1.0000000 0.0000000 0.0000000 0.0000000 1.0000000";
then your trigger will work properly.
Can someone (GG?) determine what's causing this problem?
04/14/2002 (2:41 pm)
Ok, I've identified the problem, but I'm not exactly sure how to fix it in the code, but I can fix it by modifying the mission file.When triggers are created, the polyhedron which identifies the shape of the trigger should be:
polyhedron = "0 0 0 1 0 0 0 -1 0 0 0 1";
but at times it is something like:
polyhedron = "0 0 0 1 0 0 0 0 1 0 -1 0";
I'm not sure what causes this problem. If you replace the line in the offending trigger with:
polyhedron = "0.0000000 0.0000000 0.0000000 1.0000000 0.0000000 0.0000000 0.0000000 -1.0000000 0.0000000 0.0000000 0.0000000 1.0000000";
then your trigger will work properly.
Can someone (GG?) determine what's causing this problem?
#4
04/14/2002 (4:48 pm)
yes i found that fix when i created this thread doing a search on the forums... and yes i used that "fix" to make them work... but i dont know about the editor fix
#5
04/14/2002 (10:01 pm)
Dang, it kinda sux that I spent nearly two hours on this when I could've spent a few minutes searching the forums... heh.
#6
04/15/2002 (10:29 am)
i spent ... couple of days :D
#8
04/15/2002 (2:08 pm)
yeah :D
#9
Which is was, for a while, it's broke again now though :)
Anyone tried the new HEAD? Seen alot of editor stuff getting tweaked but have not compiled :)
04/15/2002 (3:17 pm)
To be a little fair, depending on when you actually did the search, one of the posts claims that it was fixed :)Which is was, for a while, it's broke again now though :)
Anyone tried the new HEAD? Seen alot of editor stuff getting tweaked but have not compiled :)
#10
04/15/2002 (7:39 pm)
mark just fixed it in the new head
#11
04/15/2002 (8:27 pm)
W00t! Thanks.
#12
keep in mind that the only search you can do on these fourms ( advanced search is disabled du to it boging down the server ) is a search on subject line in the message ....
so for everyones benifit Please try to keep your posts as discriptive of a subject as possable.
not that their are tons of posters that dont do this allredy .. but not everyone is aware of this limitation on the fourm and it helps to point it out every so often :-)
04/25/2002 (1:55 pm)
Got a problem? Search the forums first!keep in mind that the only search you can do on these fourms ( advanced search is disabled du to it boging down the server ) is a search on subject line in the message ....
so for everyones benifit Please try to keep your posts as discriptive of a subject as possable.
not that their are tons of posters that dont do this allredy .. but not everyone is aware of this limitation on the fourm and it helps to point it out every so often :-)
Torque 3D Owner Xavier "eXoDuS" Amado
Default Studio Name