Specter

I spoke too soon! Started DCS today and had the very same CTD twice within 5 mins. Restarted DCS both times and on the third restart managed to get into the mission! Getting very tedious now!

I might be talking too soon but either item 1 or item 4 seems to have fixed my crashing. It has gone from several times an evening to none in the last 2 days of regular playing. If it raises it's head again I'll report back.

Ok, solved that issue, I have moved all my Win Temp files to another drive. found it there and emptied it. Will try again tomorrow to see if crashes are still an issue.

2 + 3 I always do every update. I will try 1 and 4. PS. I don't have a "C:\Users\username\AppData\Local\Temp\DCS.openbeta" do you mean "C:\Users\username\Saved Games\DCS.openbeta"? PPS. I've been looking back as I have crash logs all the way back to Sep 2018 and this particular crash happened for the first time on 15 Apr 21. The day after 2.7 released so it has only been happening for me since 2.7. The last hardware change to this machine was in early March 2021 so I don't think that is the cause.

I can report after updating to the latest BIOS I am still getting these random CTD apparently linked to the Nvidia drivers!

Just checked and excluding beta bios there are 2 updates between mine and latest so I will give it a go later. I'll report back.

Thanks Flappie but that is how I always update my Nvidia drivers included recently. I'm afraid that is not the fix.

Can anyone tell me the most likely cause of these random crashes I am experiencing from the attached Crash logs. It is getting really frustrating, I get have been getting these crashes for several versions on OB regardless of Nvidia driver version and in either 2D or VR and whether vanilla install or with mods applied. Thanks in advance dcs.20210626-200710.crash dcs.log

That is not the only problem with Golf Dispersal. Hate to think how many months I have worked at that location in my youth so I know there are several buildings missing from that and Echo dispersal and probably others if I cared to look. I also find it highly amusing to find the U2 hangar with Union Flags hanging on the back wall!

These danger areas was where the RAF carried out air to air gunnery exercises but since Akrotiri has been the centre of the RAF operations in Syria for a few years now those exercises are long gone. I checked the Cyprus AIP and there are no on land bombing ranges.

Looking at the picture you have posted you are already too low, too slow (AOA too high) and looking at the IAS too heavy. If you travel from where this picture was taken to the carrier deck without correcting all of those parameters you will struggle with catching any cable let alone the desired 3 wire. Not sure what you actually mean by "hopeless hook angles" but if you are trimmed "on speed", lined up and follow the appropriate glideslope to the TD area of the deck you will pick up a cable. I'm no expert but I can catch a cable on the majority of my approaches. Search Youtube for "dcs case 1 carrier landing " and you will find plenty of tutorials.

Fully understand. Don't get me wrong, after nearly 40 years of watching INS alignment status countdowns simulating that aspect in a game is taking simulation too far IMHO. I'm all for instant align options.

I was commenting on the Typhoon as I have RL experience of it. DCS is a game and they can program whatever unrealistic wizardry they like but I'm betting IRL every fighter you listed will work the same way as the Typhoon. Every RL fighter I have ever worked on needs a full align before a memhdg align.

It does indeed but it only works if the INS has had a full align and then shut down ready for the next align to be a mem align. You can't just do a mem heading align from cold.

I am still getting CTD some times without a crash log and when a crash log is written invariably it is the nvwgf2umx.dll file mentioned above. I have tried the all of these Nvidia drivers; 466.11, 465.89, 461.92 and 461.72. The crashes are random, irregular and so far seem to be unrepeatable. I never had this problem throughout all of 2.5. I've removed all MODs and run repairs but to no avail. Sometimes I'll get a full session flying and next time CTD within minutes. They are happening SP and MP. It is also interesting to notice that as this thread has slowly grown to 3 pages the one guy that had a positive experience got a response from ED within 10 mins but the rest of us, who are having issues, seem to be talking to the wall. Just an observation.

Bad intel! The driver update did not stop this issue. More investigation required.

On 2.5 I had very very few CTD events and the last one was caused by C:\Eagle Dynamics\DCS World OpenBeta\bin\lua.dll Since updating to 2.7 I have had 8 CTD events and looking in the *.crash files for each event showed: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3784df9edffd3314\nvwgf2umx.dll C:\Eagle Dynamics\DCS World OpenBeta\bin\GraphicsVista.dll C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5364881c934f6ce8\nvwgf2umx.dll C:\Eagle Dynamics\DCS World OpenBeta\bin\GraphicsVista.dll C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3784df9edffd3314\nvwgf2umx.dll C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3784df9edffd3314\nvwgf2umx.dll C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3784df9edffd3314\nvwgf2umx.dll C:\Eagle Dynamics\DCS World OpenBeta\bin\GraphicsVista.dll Sensing a bit of a pattern here I updated my Nvidia driver to the latest 466.11 (it was 465.89) and although it is early days so far so good. If my CTD events return I will report back. Hope the above info helps someone if early testing proves to be an indication. As a side issue I mainly fly on busy PVP MP servers and I still find 2.7 takes a heavier toll on my system than 2.5 ever did but I'm sure further optimizations will follow as there are enough people now reporting poor performance in other threads for it to not be a thing.

You can if you only play single player. Most MP servers will upgrade and you won't be able to join them unless running the same version.

To be fair BN I have seen and tried your VR settings and you are accepting significant reduction in visual quality to achieve your "Super smooth" 90 FPS. As you can see from my signature I have a fairly powerful system and using the settings I settled upon in 2.5 has caused a significant drop in performance in 2.7. No disrespect intended but with your settings I think the game looks and feels awful. However, just in case I have an issue lurking that I have added my DCS log for you to have a look at. dcs.log

It doesn't matter if you are. I am and I've gone from, on MP servers, 50-60 fps in a Reverb G2 pre 2.7 to 30-40 fps post 2.7 and I have made no changes to any settings. So, something is eating the performance.

It had done that for ages! Was hoping for a fix but guess that was not realistic!

Specter - F-5

Not unless Win10 Ver 20H2 does it automatically at it certainly made a massive difference for me running Ver 20H1 (AKA 2004) and I'm running 32Gb RAM and 24GB VRAM (3090).

If you want to alternately switch between VR and Non-VR use Skatezilla's utility. It won't however switch between the 2 with DCS running.

I also have this same bug using Reverb G2 and RTX 3090 and it only happens near the SC superstructure and I've had it happen in the F-18 and UH-1. It doesn't happen anywhere else including on the standard DCS carrier. On a Nvidia DCH driver turning MSAA off did not remove the issue however on the latest standard Nvidia driver it does but then the sim looks shit. I think turning MSAA of just masks the real defect. Hopefully it will be rectified sometime soon. This video shows the issue at around the 0:32 mark. Very distracting. Video