Takyon wrote:Is there any way to compensate for framedrops while running scripts? I tend to get varying results each time I run it, which i'm guessing is because of dropped frames. fixedtime 8 is the closest cvar I've found to what i'm looking for, but it doesen't work for some reason. The cvar host_framerate 0.001 (for 1ms frame length) in quake 1 / half-life does exactly this.
I would also be grateful if someone could send me a modified client with optimal strafing and autojump for use with botted runs. I've only used the default game game cmds/cvars thus far, +forward;+moveright;+right;cl_yawspeed x;wait y; ... etc.
dqopb wrote:Takyon wrote:Is there any way to compensate for framedrops while running scripts? I tend to get varying results each time I run it, which i'm guessing is because of dropped frames. fixedtime 8 is the closest cvar I've found to what i'm looking for, but it doesen't work for some reason. The cvar host_framerate 0.001 (for 1ms frame length) in quake 1 / half-life does exactly this.
I would also be grateful if someone could send me a modified client with optimal strafing and autojump for use with botted runs. I've only used the default game game cmds/cvars thus far, +forward;+moveright;+right;cl_yawspeed x;wait y; ... etc.
fixedtime 8 is exactly what should help. Offline of course, and in devmap mode. It won't help online though. If your attempts are not identical with fixedtime 8, try to refine your script... A bot engine may have calculation error from time to time, but q3 itself, running a script with fixedtime 8, should execute the commands accurately. And you don't even have a bot. Try to not use lengthy wait values. I noticed that scripts with actions like "wait 250" fail more often that those with "wait 20". And replay scripts with "wait 2" only are 100% accurate on my engine. But then you can hit the pitch/yaw turn speed inaccuracy. Default q3 doesn't have a simple and accurate way to set pitch/yaw instantly.
A modified client with optimal strafing and autojump is usually referred as a strafebot. Although there are some strafebots spread among the community, sharing them is not a common practice. q3df team puts efforts to constraint strafebot abuse on the servers (and setting a strafebot record when logged in leads to ban, as far as I know).
I would encourage you to write an own bot though, if you can program or want to learn to. I could answer your questions, and would be glad to see a new bot scripter around.
I noticed that everyone who wrote an own bot (those who I know) had slightly different approaches, and everyone brought his own little innovations. And they usually were more productive in scripts than those who just obtained someone else's bot.
Sharing ideas, not the binaries, works for the common good.
I'm curious what you achieved with the default q3 commands! Do you mind to upload some demos?
P.S. Sorry for that much philosophy in 1 post.
© 2011 q3df.org. Designed by Zeences. All Right Reserved.
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Prostylize Darkgrey style by Ishimaru Design