the strangest crash

[SoUlFaThEr]

i was testing my new map(remake of my sf_columns) with as_ and es_ scenarios.
I finished a waypoint for it......threw in some bots......and when the vip actually made it out of there.......HL crashed with this HL window message:

sz_getspace:overflow without FSB_ALLOWOVERFLOW set on server reliable datagram

WTF is that ???

anybody have a clue?

Originally Posted by SoUlFaThEr

i was testing my new map(remake of my sf_columns) with as_ and es_ scenarios.
I finished a waypoint for it......threw in some bots......and when the vip actually made it out of there.......HL crashed with this HL window message:

sz_getspace:overflow without FSB_ALLOWOVERFLOW set on server reliable datagram

WTF is that ???

anybody have a clue?

Sounds definitely like an HL error, map errors are usually showed in the console or noted on compile. So your map is making HL.exe have a fit instead... maby a memory error, but what is sz_getspace:Overflow ?

[SoUlFaThEr]

this question has already been answered and it had to do with the podbot dll i had at that time.
not with hl.exe

PM said it best :

This message means that the bot tried to send too much of "special" network messages to your client. Special network messages are messages that are not handled in the standard "pack" that makes up the HL network protocol. These special messages can be player chat, or temporary entities which are displayed server-side (not client-side temporary entities like smoke puffs or gunshot decals). An example of these are the beams that are displayed in the waypoint editor. Each beam is a temporary entity with a lifetime of 1 second, and the bot re-creates them every second. Your computer crashed because the bot tried to send too much of them to your client in the same frame.

If you were running with the waypoints enabled, try not displaying the waypoints next time. If it still fails, try disabling bot chat.

Such crashes can also happen randomly if the program writes at incorrect memory offsets. This happens for example when the programmer attempts to write beyond the limit of an array. There is one thing I can think of that I have changed in the bot source code, that might cause that: I've changed the team number identifiers (they were 0 for T and 1 for CT) to 1 for T and 2 for CT, so as for the bots to use the same numbers when selecting their team in the menu. It's not a big deal, but I thought this was cleaner. I ensured that everytime these team numbers were used to index an array, I was substracting 1 in order to get them back into the 0-1 range, but maybe I've missed one out. It can be true for the radio chat times array, for example. Check it out, coders

[Pierre-Marie Baty]

It's a network problem. The game sent too much information in one single frame to a particular client and the client didn't empty his buffer soon enough, and some frames which were flagged as important were lost, thus leading to the engine giving up.

perhaps you have too many bots/too many waypoints/too many sprites to display/too many entities/too many lights/too many whatever stuff that would have to be reset all at once at round restart and your listenserver couldn't handle them all.

[TruB]

cool.. "too many of whatever stuff"

[SoUlFaThEr]

ok.....19 bots+me
a func_escapezone
a func_vip_safteyzone
6 func_illusionaries
1 map_parameters
16T spawns
16CT spawns
maybe 15 armor_entities.

thats all the map had going.......its a really simple map. i run 19 bots on very complicated maps like cs_waterside with its millions of sprites and modles everywhere let alone the multiple hostaes and 6 rescue zones........and dont get this problem.

i really begin to think that an as_mission and an es_mission are not compatible with each other like with cs_ and de_

[Pierre-Marie Baty]

It's noteworthy that POD-Bot is NOT designed to support multiple objective maps. The bot selects its mission and behaviour according to the map type, and it only knows cs_, as_ or de_. If the mission is not specifically like the bot expects it to be things may mess up very easily in the internals.

[SoUlFaThEr]

ok thanks

ill make a as_de_ out of it

[Pierre-Marie Baty]

hmm you didn't get me right.
The problem is not that POD-bot doesn't support es_ missions, the problem is that it can't handle multiple missions at once at all.

If you make an "as_de_" map, the bot will believe it's an as_ map only.
But if you call the same map "de_as_" instead, the bot will believe it's just a de_ map only.

There's nothing you can do about it but to change the way the bot works...

[TruB]

change bot!