BotAim 2 announced. Best aiming ever.

[@$3.1415rin]

to emulate 'real play restrictions', pmb is using some more code to couple e.g. pitch and yaw to some degree, I think this isnt necessary ... anyway, the pictures above are all done using discretizations, but I used linear interpolation for plotting. the numbers below show the number of the frame, only with the topmost picture, there is a missing 10^4 or 10^5 on the screenshot, therefore it is maybe looking nondiscrete

the improvement I was testing in the 2 pictures below was 4th order runge kutta if that tells you anything. main reason to implement such an algorithm would be better stability of aiming against low framerates, @50fps you see hardly a difference. I guess for our purposes an adaptive step size control like "if we are below 20fps, run as any iterations in one frame that it looks like 20fps for the algorithm" would be sufficient

[KWo]

Can someone care a bit also about the compatibility such plugins like botaim with mm plugins increasing FPS on the server (like booster or such)? Such plugins "lies" all bots aiming algorythims based on msec code. More info about booster (and similar plugins) Hullu (ghost_of_evilspy) may give You, guys...

[@$3.1415rin]

I guess that's just an issue of the time measurement resolution. maybe try to use other timebases, like RDTSC or anything else.

but who needs that booster stuff anyway

[[NvT]_KaszpiR_]

people add it because of lack of knowledge

[KWo]

I'm browsing some forums like AMX or AMX X forum and when the people post their running plugins - booster is still listed as used by them...

[ghost of evilspy]

Booster Lite actually does same on win32 as '-pingboost 3' on linux (stop sleep on network IO event). Booster 2.x by Buzzkill does include Booster 1.x and Lite sourcecode, but I don't think lite code path is default.

Why does bots try to think on every StartFrame? Clients send 30 packets/sec by default to server and that's fps that server operates on clients. My HPB_bot modification works perfect (no difference) with BotThink run at 30 fps and uses much less CPU. Actually my old K6-2 couldn't run HPB_bot v4.0 without me adding think-fps-limiter.

[Pierre-Marie Baty]

RACC won't have that problem since it uses its own engine-independent time measurement stuff. The only concern is when the framerate drops at very low values, but as aspirin points out a simple solution is to double the algorithm passes in this condition.

Originally Posted by ghost of evilspy

Why does bots try to think on every StartFrame?

Very true. When all the bot brain is based on timers, when nothing typically frame-dependent remains, it is possible (and even recommended) to make it think at 15Hz (or 30Hz to cheat a bit). I believe the human brain waves are at 15, aren't they ?

[@$3.1415rin]

most bots don't "think" every startframe I guess, but the movement code needs to be called every frame, and there a lot of bot coders also update their aiming. using this DGL stuff this results e.g. in a better precision

[ghost of evilspy]

Originally Posted by @$3.1415rin

... but the movement code needs to be called every frame ...

It doesn't, not for HPB_bot atleast.

[Pierre-Marie Baty]

Well, it SHOULD. pfnRunPlayerMove() should be called every frame, no matter what the bot is doing.