quote:
Yes, i'm worried about not being able to make the time frame cutoff if I start adding to much stuff like that with to much memory access and stuff.
i wouldn't be *too* worried about not making the time limit. currently, when i run my bot (in debug or release mode) i have several layers of complexity (perceptual system, reactive system, internal map, decision making system), some of which are currently implemented *very* poorly with regards to speed/memory access (in my perceptual system, for instance, each time a query is made to GetObjectsInSight() i new up a bunch of percept objects, then at the end of the update i delete them all (i know it's bad...i will fix it)! plus, i run a debugging window which displays the bot's internal map, his planned navpoints, his goal point, and prints out any debug info all using the windows GDI (which as we all know is slow as hell). on top of this i write info to a log file. the kicker is, i don't even wait till shutdown to write the log...i just write it every update!! this is a relatively slow operation...opening a file, appending stuff to it and closing it. with all of this slow, crappily implemented stuff my bot almost never goes over the time limit. usually if it does, it's cause of a disk seek (i'm guessing that it is at least, cause usually i'll hear the drive do something, then i'll get the time limit message).
quote:
I'm also worried about going through hoops trying to get something to work with a bad system, if he's going to be changing stuff still... might have to change to much crap, or maybe it will become easier, etc.
yeah, this is currently holding my bot back too...to move on and implement more functionality, my bot needs to handle wall detection and a few other things. while i know i could spend a night or two working to implement a system that detects walls and keeps my bot informed of errors in it's internal map using the current interface, i know it will be *much* simpler to do this once we have a better method of sensing walls. another thing that i'm waiting on is the fact that even if a tad less than half of an object is in your FOV, if the center isn't in the FOV, you can't see it. kevin has said that he intends to fix this. once i have these changes, i will get cracking on my bot again. so i understand your feelings of frustration.
-------------------------------------------------------
A headache, ancillary; an hourglass auxiliary.
"something witty, blah, blah, blah"
--That One Witty Guy (remember? that one dude?)
(author of DustBot)
[edited by - drreagan on August 15, 2003 9:22:23 PM]
------------------------------------------------------- A headache, ancillary; an hourglass auxiliary."something witty, blah, blah, blah" --That One Witty Guy (remember? that one dude?)(author of DustBot)
.
