patpatpowercat Posted October 15, 2024 Posted October 15, 2024 (edited) Our group had a couple large client crashes this weekend during an event. In both cases, the server did not crash. Members in gamemaster/spectator slots did not crash or disconnect. There were no lag spikes or issues prior to the client crashes. We did not add any new scripts/mods that we have not been using in the past. In all cases, the clients froze up, then crashed. In all cases, the client's crash log points to an access violation from the transport.dll. As you can see, they all occurred at the same time. No large event/battle occurred at this time. Attached are 3 client crash logs all showing the same thing, however I can happily produce more client crash logs showing the same. There is also a full log from another client. The server log showed nothing of note. This mission was run through multiple times in SP, and never had any issues. It seems to be only in MP that there are issues, and only for clients that are occupying module slots. pat_dcs.log-20241013-015641.zip matth_dcs.log-20241013-015641.zip cblou_dcs.log-20241013-015641.zip OGA04 Client Crash.log Edited October 15, 2024 by patpatpowercat
patpatpowercat Posted October 15, 2024 Author Posted October 15, 2024 Crashes occurred in clients occupying multiple different modules from multiple different module makers: F-18, 16, AH-64, F-15, F-14 were all effected the same way at the same time.
patpatpowercat Posted October 17, 2024 Author Posted October 17, 2024 We've removed *all* scripts and this crash still occurs. Always related to the transport.dll. dcs.log-20241015-192648.zip dcs.log-20241017-191650.zip
Sknusk Posted October 20, 2024 Posted October 20, 2024 I'm having this same issue and MP is unusable now.
sleighzy Posted October 23, 2024 Posted October 23, 2024 (edited) These logs show a large number of custom mods, including integrity check failures and errors in scripts. You've stated that the clients all crashed at once, and that you cannot replicate in SP. Have there been any other changes made, no matter how insignificant (including DCS upgrade), recently? This mission has always worked in the past and is just a recent crash, or is the first time you've used this mission in a multiplayer context? Edited October 23, 2024 by sleighzy AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Recommended Posts