FR4GGL3

It's a Sarlacc Pit. Did anyone notice a floating Boba?

Thx for the test. Sorry that it was a road to nowhere...

We have a lot of nVidia Users here. So would anybody so kind to try the following: Go into the nVidia Control Panel. Go to "Sourround, PhysX" Menue. Switch the PhysX-Setting from "Auto" (which adresses the nVidia Card) to "CPU". As long as I have PhysX bound to CPU, I haven't had a 2nd Load crash like before. As soon as I switch back to "Auto" oder "GPU", the crashes start all over again. I could switch the crashes on and off via this setting on my machine. That must not be true for anybody else. But I think it would be worth a few Tests. Oh, and of course don't use the Compat. Mode while testing this as that wouldn't be the same. If the new Clouds use some kind of PhysX, that would make sense. At least for nVidia Users. Sorry that I can't test on AMD Hardware as I sold my Vega 64 a few months ago...

Update: it crashed. I'm back to comp mode...

It must not mean anything, but I am trying something at the moment. 1.) the compatibility modes (Win 7 / Win 8 ) worked for me for the last days. No crashes, but a bit slow on loading and exiting. 2.) now I stumbled across a message here in the forums that someone had crashes and he could solve this by uninstalling and reinstalling his official F-14 Module. So I tried that also. So far no compatibility mode and for now no crashes. But it might be that they come back after a few hours or days. So has anybody else tried this and had success or could he/she tell me that this isn't worth the testing(?)

As it seems you changed quite some things at the Engine (e.g. dx11background.dll is now only 1/3 to the stable Version), could it be that you did something that gets into issues with Windows MPO (multiplane overlay)? Because this is something that is supported by the nVidia drivers since 461.09 (I think it was that number). I remember that there have been people that had issues with this even on Desktop and especially on chrome. And there was a registry setting to disable this. And nVidia told people to set VSync on at the global Settings. This is just a stab in the dark. But it is something that has changed not so long ago... But there might people who know better and could prove that this guess leads to nowhere...

I have had a CTD just a few Moments ago. Even with turned off fullscreen mode (I tried your hint). It is the same old d3d11 AppCrash as before. Sorry to say, but that doesn't work for me. I also blacklisted the DCS Folder as well as the DCS.exe in Windows Defender (so it should ignore it) so that the crashes shouldn't be related to the Windows Defender. I don't think it has anything to do with the Security SPP events because I can see them a lot in my Events (even on times when I don't run or crash DCS). And the only thing this events do is to set a restart date for the year 2121 (btw. I guess it won't bother me in 2121 anymore...). But I gave it a try by excluding the whole DCS Folder. That also didn't help. I did also deleted the OOB DCS nVidia Profile as it had Excludings for SSAO which eventually wasn't a thing in Black Shark 1 but is a thing in DCS now. But that also didn't help. /edit: I have 0 mods. But I do have the Nevada Map and the Syria Map. The one and only Plane I fool around with is the F-14. But I can trigger this CTD very often by simply start a Quickstart Mission in Caucasus, end it and then start a Quickstart Freeflight in Nevada. When it crashes, it mostly crashes instantly on loading screen as if the Memory or Cache couldn't get flushed and it tries to load, but it can't (but that is a guess for shure - I have no evidence for that). dcs.log-20210507-061249.zip

This cutting it in half was the reason for me to try the adaptive VSync Option in nVidias DCS Settings. Here is a Windows Event Log of a typical CTD on second Mission (including the dcs.log) dcs.log-20210505-174412.zip

I also have this SPP-Events. But I can also force "App Crash" Events for DCS.EXE simply by fooling around with VSync Settings. I get them if I set the preferred Refresh Rate to "Highest" instead of "Application Controlled" and set the VSync Option "on" in DCS. The Result is a hard locked DCS without a crash report. It is simply frozen. The settings from the uploaded screenshots seem to work for my machine (no guarantee that it could help others). I tried several quickstart Missions and stopped them, got to the next quickstart Mission - till now without a CTD or AppCrash (Driver Version is 466.27 and I have rBAR enabled) I have to admit, that I use a 144Hz Refresh Rate and usually use my Monitors FreeSync Capabilities with FPS Cap to and never use VSync because of the Input Lag. But that doesn't work well in DCS. At the Stable Version (2.5.6.xx), I don't need to set anything else then fixed refresh rate and a FPS Cap - no VSync. But if I use the same Settings at 2.7 I get CTDs mostly on the second Quickstart Mission or the second run of the same Mission. As I wrote, these Settings seem to Work for me at the moment - but I have to test them a few more days:

Hello all, I used to use a FPS Limiter (60 FPS) via the nVidia Control Panel. So i switched it off. But that didn't help. I still have the crash on 2nd Quickstart Mission. Yesterday I used the F-14 against the Flanker on Caucasus. As soon as it was down, I hit End Mission and tried the free flight on Caucasus in the F-14 => crash. And that without FPS Limiter and resetted nVidia DCS Profile. So I went back using the FPS Limiter. It helps me to safe energy and heat. You know, I've heared that fast GFX Cards are rare these days. 9900K @ stock with nVidia Gigabyte 3080 Gaming OC @ stock on 32 GB RAM @ XMP. This System has been stabel at any torture Test I have thrown at it - even LinX with every Residual matched. Except DCS Beta 2.7