Regular freezes for all clients in a flight in MP

[Harker]

For about a month now, maybe a little more, myself and others have been experiencing very frequent freezes in MP. Specifically, DCS will freeze for all clients in a flight, most often when we're returning to the carrier.

Because DCS freezes, no useful logs or crash reports are generated and the game needs to be terminated via the Task Manager. This post is meant to draw attention to the fact that the freezes occur simultaneously for all clients in a flight. As of now, I'm unsure if it's related to the fact that we're in a flight or to the fact that we're at the same location or same distance from something, when the freeze occurs.
 
Sometimes it'll occur when we're in the stack, just orbiting, but most often it'll occur when we're still a little further out and approaching.
 
I'm aware of the crash related to the Tomcat, but in my case, and the cases of the rest of my flight, we're flying the Hornet. It could be that the crash occurs when we're approaching Tomcats though, as our group flies both.
 
For what it's worth, our Tomcat players also experienced freezes like that (all clients in the flight), but I can only speak for the Hornet, as that's what I fly.

[silverdevil]

  

On 7/14/2022 at 5:34 AM, Flappie said:

That's weird. Anyway, chances are it's linked to the Tomcat. Heatblur is on it.

 

 

[PravusJSB]

I have not found this happening, do you have custom code running in the server? First port of call would be to check for any functions that might run infinitely if they throw and have no catch, or you have a function doing other odd things that crashes the Lua VM. ED exceptions are good, but they are not a catch all.

It's also interesting to note that if you have a poorly written function that blocks ED code and runs significantly longer than frame time it is possible to destroy net-sync, and it will never recover.

Edited July 16, 2022 by PravusJSB

[Harker]

I have not found this happening, do you have custom code running in the server? First port of call would be to check for any functions that might run infinitely if they throw and have no catch, or you have a function doing other odd things that crashes the Lua VM. ED exceptions are good, but they are not a catch all.
It's also interesting to note that if you have a poorly written function that blocks ED code and runs significantly longer than frame time it is possible to destroy net-sync, and it will never recover.

Hi, sorry for the late reply.

We don't have any custom scripts running on the server, the only script is the Tacview export. Also, the server is fine, it doesn't crash. Only specific clients do (not always the same people and not all clients in the session), but the odd thing is that they crash simultaneously (e.g. the flight lead and all wingmen crash within a few seconds of each other) and it usually happens when they're returning to the carrier.

I'll still show your comment to the guy running our server though, thanks for the reply.