Who's Online 2 Members, 0 Anonymous, 49 Guests (See full list)
12 bots? well, I'm running 30-34 bots on EACH server. Running great for a year, and the 3 servers are running right now without the authtoken.
Also there's bots and theres more intelligent bots... bots to play DM/TDM are a lot lighter than bots from Frontlines that do everything the mod have, like play all the 52 gametypes, can plant clays, work as medic, defuse explosives, etc, etc, etc...
How more smart the bots are, more processing they will use, simple math.
But anyway, the main problem that was working fine few months ago, and now I need to remove the authtoken to work. This shouldn't be related in any way right?
Like I said above, already pointed few changes that I noted in the last updates that might causing this right now.
Check this change for example:Quote
One of the changes in COD4X is that if we test if a bot can see (bullettrace, playerphysicstraces, etc) something, if the destiny origin is INSIDE a solid (player or object), doesn't matter if have several walls between them, now this return as true with the final origin like doesn't have nothing between them, when before that used to return false as supposed to, first hit origin in between (like walls). Was working fine since the first bot functions released in COD4X.
Maybe create a dedicated function to this like I requested a loooong time ago might solve this and have even best behaviors and performances, the ones most important are canSee(something) right now the bot can see through brushes, and the other would be canWalk(until something) checking if the bot have a clear way to go direct to that origin.
Or at least just fix all the Traces as was working before. This would be a great start to make better performance of bots.
And of course, check and fix why the authtoken/server query and using so much CPU to cause lags. This should not use almost ANY amount of CPU right?Edited by Hajas
21 hours ago, Sheryl said:
For the heli, set it to high. You dont need to add anything to the hitbox model line.
Now working Thank you very much!
SkC 0On 12/25/2020 at 1:18 AM, Fraggy said:
Have you tried to reset the config files in %LOCALAPPDATA%\Callofduty4mw\profiles
I found out the error comes out of the miniconsole updating routine. I assume here an illegal value for a dvar controlling behaviour of the console.
Months later I check back lol but yes that fixed the issue, thanks man.
here it is with 3 cod4x servers(New Experience / Botwarfare running on each) with 12 bots in each all controlled with B3 bot and 2 IW4x servers with 9 bots in each.
I get the hitch warning but don't get any lag (Hitch warning: 1974 msec frame time)
Can only assume something wrong your end
I am running 2 servers (usually have 3 running) with 12 bots in each both with authtoken with no problems.
also running 2 IW4X servers at same time