Dread091

Oh I forgot to mention that we are on Pretense Syria. We are trying a mission with some more units but not Pretense yet. Would it be useful for you if you have access to our server when we retried Pretense?

As far as I remember, yes always happend on Pretense. I've just flight for 2 hours this evening on an empty mission with 3 friends and everything's OK.

We're attempting a free flight mission without any units (with SRS only), and so far, there have been no crashes. Nevertheless, in my opinion, conducting a test without AI units, explosions, or missile/bomb shots doesn't seem representative of how we typically use DCS. I understand that DCS is a complex environment and I am not trying to discredit ED. I know you want to rule out all possible variables (I work in IT, I will do the same) Maybe Pretense is the problem but if we don't have crashes outside of Pretense, it would be too simple to say that the issue comes from there. I'd like to mention that there are approximately ten pilots flying on Pretense, and two of us have experienced recurring random crashes (possibly a third—I'm currently recovering the log). The randomness of this crash makes debugging difficult. It can occur in the first minutes after selecting a slot or after 30 minutes - an hour of flight and sometimes even a day without meeting it. Could enabling the full log tell us more?

And here the log from my friend. I see that we have pretty much the same pattern. First this line: 2024-04-27 14:49:47.605 WARNING EFFECTS2 (Main): OParticleSystem: preset 'smoke' not found in 'speedSmoke.lua', using default And few minutes later crash with these lines: 2024-04-27 14:51:20.582 INFO EDCORE (14832): 0x00000000000272a6 (edCore): b2DynamicTree::RemoveLeaf + 0xC6 2024-04-27 14:51:20.583 INFO EDCORE (14832): 0x0000000000026c19 (edCore): b2DynamicTree::MoveProxy + 0xC9 2024-04-27 14:51:20.585 INFO EDCORE (14832): 0x000000000003e2aa (Effects): Effects::PipeSmokeProviderProxy::setSmokeDensity + 0x650A 2024-04-27 14:51:20.585 INFO EDCORE (14832): 0x000000000003edee (Effects): Effects::PipeSmokeProviderProxy::setSmokeDensity + 0x704E 2024-04-27 14:51:20.585 INFO EDCORE (14832): 0x0000000000161dcf (Visualizer): smSceneManager::DestroySceneManager + 0x1147F 2024-04-27 14:51:20.585 INFO EDCORE (14832): 0x00000000001671b8 (Visualizer): smSceneManager::regLua + 0x4FC8 2024-04-27 14:51:20.586 INFO EDCORE (14832): 0x000000000014e96c (Visualizer): smCamera_Implement::getClipRegion + 0x19CAC 2024-04-27 14:51:20.586 INFO EDCORE (14832): 0x000000000013a08c (Visualizer): smCamera_Implement::getClipRegion + 0x53CC 2024-04-27 14:51:20.586 INFO EDCORE (14832): 0x0000000000151b72 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 2024-04-27 14:51:20.586 INFO EDCORE (14832): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 2024-04-27 14:51:20.586 INFO EDCORE (14832): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2024-04-27 14:51:20.586 INFO EDCORE (14832): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D dcs.log

No I don't have any T.A.R.G.E.T. scripts. I run a memory test from Windows 11 app and everything seems OK.

Repair done but just had a new CTD. Seems the same error. dcs.log

I think we disable all mods and same error yesterday. This time I was in an F-14. CTD 10 seconds after I select slot. dcs.20240425-193638.log

Thanks for your answer. Worth a try to disable some mods on the server. Is it also necessary to remove them from the Saved Games folder (client side)?

Hi! A friend and I had a CTD in our server when we flight the Mi-24. If it could be useful: dedicated server runs a Pretense dynamic mission + Splash Damage script, SRS. Zip files are from my side. dcs.log from my friend. I see that the dump information are pretty similar but I'm not experienced enough to find the issue. My friend believe that the issus come from SRS and uninstalled it. The problem hasn't reappeared but I don't think it's related. I have the impression that it is linked to an effect that is launched by the mission. Thanks in advance. dcs.log-20240418-190556.zip dcs.log-20240418-145812.zip dcs.log