Game Development Community

SetMoveDestination's failure to return to it's starting point

by Ronald V Rieger · in Torque Developer Network · 08/20/2007 (1:55 pm) · 3 replies

I probably am missing something obvious, but when I use "setMoveDestination" (TGE) to move my bot to a position, the bot will go to different locations depending on where he starts. As an example, I can move him to, say, "30.0 -440.0 1.0", send him to "30.0 -447.0 1.0", and then attempt to send him back to "30.0 -440.0 1.0", but he will head off and go to a different location.

I am new to TGE, so any thoughts on how to correct this rather annoying issue would be very much appreciated.

I have not used any forum before, and may have posted this to the wrong forum. If so please let me know and I will post it elsewhere.

Thank you for your time.
NextNext Thread
PrevPrevious Thread
More from Torque Developer Network


Torque Owner Ehab Yosry Amer
#1
09/09/2007 (6:14 pm)
Try to use setAimLocation( point ) for a start to c if where the point u sent is.
do u give the location from the code directly or u use some mouse picking to move around ??
post the code that doesn't run properly here so we could go through it together

Torque Owner Ronald V Rieger
#2
09/11/2007 (5:30 pm)
Ehab,

Thank you for the kind offer. I discovered (after some rummaging around) that the engine uses the eye location as the bot's current position. This turns out to create some inaccuracies (bad engine math calculations) when working in close quarters with very specific position requirements. I replaced this in the engine, for setMoveDestination only, with a getPosition call instead. This corrected the problem.

Associate Orion Elenzil
Real Life Plus
#3
09/11/2007 (5:35 pm)
Good to know; thanks.