Not 100% true. I have determined through a few tests that it has basic position extrapolation for players. But as far as PBs are conserned, it doesn't.
Mine GO BOOM - Wed Jun 11, 2003 8:34 pm
Post subject:
If you have the location set to be known on radar (Soccer:BallLocation:1), the ball will know where the ball is every Soccer:SendTime / 100 seconds. The between times, you'll have to do physics with walls and such.
tikiman - Thu Jun 19, 2003 1:38 am
Post subject:
The bot does not know the location of the ball unless its being carried by a player. I've tested this many times.
Try having the bot print out the location of the ball every Ballmove event. While the ball is carried the location will be changing according to where the player and the ball are. But after the ball has been fired, the location will remain the last location in which it was carried (ie where it was fired from) until it is again picked up by a player. Changing BallLocation=1 and lowering the Sendtime seem to have no effect on this from my experience.
Unless you guys are doing something I'm not there is no way to know the exact location of the ball at all times unless you emulate continuum's physics perfectly.
Doggeti - Thu Jun 19, 2003 2:20 am
Post subject:
struct PBall
{
Uint16 x, y;
Sint16 xvel, yvel;
Uint16 team;
Uint16 ident;
Uint16 carrier;
Uint32 time; // Local timestamp on event (not constant)
Uint32 hosttime; // Remote timestamp on event (constant until new event)
Uint32 lastrecv; // Last update recv time (for timeout)
}; |
Why can't you use x and y to locate the ball?
tikiman - Mon Jul 28, 2003 7:20 pm
Post subject:
Whew haven't checked this board in a while sorry....
But as I said, x and y will be unchanged while the ball is not being carried... For example, I am carrying the ball and I fire it from 512 512 to the left. No matter where the ball goes after that the ball->x and ball->y coords will stay at 512 512 until the ball is once again picked up. Once its picked up the coords will once again be accurate to its actual position until the ball is again fired. The same goes for the velocity: ball->xvel and ball->yvel will be whatever velocity the ball was fired at and will not change while the ball is in flight.