EntitiesTouchingBounds warning

[Fidcal]

I'm getting total freeze within minutes of map start which I now realize is actually about 1 frame per half minute or so. So Esc eventually got me back to the console where I see lots of these...

 

WARNING: idClip::EntitiesTouchingBounds: max count

Entered water with murkiness 0.100000.

 

I'm nowhere near water so baffled by that. What could have entered water? There are entities in the water at game start. Could it relate to spawning entities in-game > 4096? I know the offical max is 8192 but maybe 4096 is hard coded somewhere. I have 3800 in the map at start. Just added another 20 or so. Maybe I tipped it over the edge?

 

I'm just going to try killmonsters at game start.

[Fidcal]

Also just remembered I do have an objective location clip brush and AI do patrol through it. Maybe related?

[Tels]

Also just remembered I do have an objective location clip brush and AI do patrol through it. Maybe related?

 

Maybe you have a large terrain and there are alot of entities touching it?

 

I have improved the message to now say what the max_count is, it looks like the code calling this routine can ask for a specific number of touching entities and the code warns if there are actually more than that. Maybe somewhere in our code we call this with "give me all touching, but only 16" and it overflows because it has 17?

 

After someone recompiled, you might get a better error message.

[Fidcal]

Yes, killmonsters stopped the freeze up so either AI related or too many entities. I suppose I could delete a ton of entities somewhere else and see what happens.

[Fidcal]

Made some other changes. Logged out of Windows and back. Didn't dmap. Played full screen (before I was in window mode with DR and web browser and others running.)

 

No freeze. This is likely because the AI are mostly walking in circles because AAS out of date. So this might support the AI cause the freeze theory.

 

I did have one situation. I was noclip flying around checking stuff. When I hit noclip off then it wouldn't go off not nohow. It showed in console but I didn't drop. I flew to areas completely clear of clipping but when I switched off noclip I remained in mid-air.

[stumpy]

its mentioned in the wiki

 

http://wiki.thedarkmod.com/index.php?title=Clip_Functions_to_check_Specific_Models

[Fidcal]

Might have been related to a phantom rendering error because now I've fixed it I've not seen the error since. I test played through the entire FM today and it never froze. Fingers crossed that's my motto.