Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!
quote: Original post by TechnoGoth
The grenedes range is passed on the angle its thrown.
-----------------------------------------------------
Writer, Programer, Cook, I''m a Jack of all Trades
Current Design project
Chaos Factor Design Document
quote: Original post by particleG
no problems, your navigation system is just broken!
int iNumObjsInSight = g_pCore->GetNumObjectsInSight();for(int i = 0; i < iNumObjsInSight; i++){ g_pCore->GetObjectsInSight(i, ObjectType, Angle, Distance, ObjDirection);}switch(ObjectType){ case... // blah blah blah}int ObjectType[16];float Angle[16];float Distance[16];float ObjDirection[16];int iNumObjsInSight = g_pCore->GetNumObjectsInSight();for(int i = 0; i < iNumObjsInSight; i++){ g_pCore->GetObjectsInSight(i, ObjectType, Angle, Distance, ObjDirection);<br>}<br><br>for(int i = 0; i < iNumObjsInSight; i++)<br>{<br> switch(ObjectType)<br> { <br> case… // blah blah blah}<br> }<br>}<br> </pre> <br> </i> 
quote: Original post by T2kquote: Original post by liquidAir
Oh no! I tested my code in the GDArena 0.2, the same I used in 0.1 where it reacted almost perfectly, except for the walls. The thing now is, most of the time, it only sees the walls, but not the objects in it''s fov. You can download my bot from here and test it to see what I mean. I used the taunt function to display the object it''s currently looking at with the angle and distance. And another thing is that it doesn''t react as it did in version 0.1Is it my code that is buggy? or it''s the Arena''s code???
hmm my code works, so its your bot (iam actually fighting with an error flooding my object-storage ;D but i think i will find it in the next 8 hours, grml... try to use the constant deltatime of 0.02222secs (see readme)
i hope the above picture is working xD
edit: Debug mode causing Timeout ("Bot took to long") xD but only on Player1, nice handicap ...
T2k
[edited by - T2k on August 8, 2003 5:12:14 PM]
quote: What I'm curious about is whether his map is always upright with the world. I'm getting an axially-referenced orientation working, but it has to assume the first wall it sees is the east wall, and reference from there
and then i use a weighted center of all stored objects (bcuz i was to lazy to inplement something more complex), its just for debugging and the map isnt realigned when the debugwindow is off (no need for it)quote: if not, how are you doing it?!
quote: Original post by Anonymous Poster
1. The north, east, and west walls can all be detected from up to 160 units away. The south wall can only be detected from 80 units away.
quote:
2. As previously mentioned, a bot''s radar cannot directly detect a wall; it can only detect a point on the wall which is the player''s projection onto the wall. An example of where this becomes a problem: My bot is running northeast (up-right) and runs into the northern (top) wall. He grinds against the wall as he slides along it, but does NOT detect it; this is because the wall itself cannot be detected. The bot''s projected point onto that wall (which lies directly north of the bot, and is the only piece of the wall that can be seen by radar) is outside my east-northeast facing view cone. Thus it is possible to be "facing" a wall, close to it, even touching it and running into it, and yet not detect it even though it is in plain view. This may be a defect or it may be the intended behavior. KHawk''s comments:
"If you aren''t getting any objects returned from GetNumObjectsInSight, then chances are you are either in a corner or at the edge"
and
"I figured that if you are not getting any returns from GetNumObjectsInSight(), then you _have_ to be in a corner."
...seem to indicate that this is as-intended, but his comment:
"although if you''re at an edge, you should get a return from GetObjectsInSight with one of the objects being a wall."
...is slightly confusing since this is not true in the current build (as per my above example). KHawk, can you help clarify the issue at all?
quote:
3. Theta angles returned for detected wall objects are given in right-handed polar coordinates (positive yaw to the left) while all other objects are given in left-handed polar coordinates (negative yaw to the left). This seems like a plain-old defect, but KHawk''s comment:
"It''s sort of an experiment. I thought it made a little more sense to have the direction this way for walls, but I wanted to see everyone''s reaction. If people want it to be the same as the other objects, I can do that."
...seems to indicate that it was intentional. Right now I''m simply inverting the theta on any object of type OBJ_WALL I detect, but that seems silly and I was wondering what the benefit was of reversing thetas for wall objects.
