hornblower793

I was replying to the post above mine

Others will have a better chance of helping you work this out if you can also post details like your system specs, whether you are running MT or ST, attaching logfile and / or trackfile with the issue.

In your saved games folder (C:\Users\<your username>\Saved Games\DCS.openbeta (or DCS). You should have both an fxo and a metashader folder in here. Close DCS, either delete both these folders or go into each and clear out all the files. DCS will then recreate the files it needs when it is running

This happened a few years ago to some of the A-10 callsigns and Hollywood had to make a change in Vaicom. Probably worth checking the Vaicom discord to see if this is already a known issue and if not log it

This was fixed in the last update. Are you saying that your installation crashes if you try to launch MT in VR, or just that it runs MT if you click on a shortcut? If the latter then your shortcut is pointing to the wrong exe. Please could you attach the log file from a launch into VR

The logs confirm it is crashing at the exact point in the loading process where the graphics driver is loaded. When I start in 2D I have the following entries: ['ScreenshotExt'] = 'jpg'; }; 2024-04-14 15:21:11.962 INFO VISUALIZER (Main): render thread initialization... 2024-04-14 15:21:11.967 INFO GRAPHICSVISTA (23496): renderer: 'dx11backend.dll' 2024-04-14 15:21:12.046 INFO DX11BACKEND (23496): DX11Renderer initialization (w:2560 h:1440 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1) 2024-04-14 15:21:12.117 INFO DX11BACKEND (23496): Driver Concurrent Creates - 1 2024-04-14 15:21:12.117 INFO DX11BACKEND (23496): Driver Command Lists - 1 2024-04-14 15:21:12.179 INFO DX11BACKEND (23496): NVIDIA API init OK 2024-04-14 15:21:12.180 INFO DX11BACKEND (23496): NVIDIA Display Driver Version 55212.r552_05 where your logs are showing ['ScreenshotExt'] = 'jpg'; }; 2024-04-14 13:07:38.770 INFO EDCORE (Main): try to write dump information 2024-04-14 13:07:38.799 INFO EDCORE (Main): # -------------- 20240414-130739 -------------- 2024-04-14 13:07:38.799 INFO EDCORE (Main): DCS/2.9.4.53627 (x86_64; MT; Windows NT 10.0.22631) 2024-04-14 13:07:38.800 INFO EDCORE (Main): F:\DCS World OpenBeta\bin-mt\Visualizer.dll 2024-04-14 13:07:38.800 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff235dd6be 00:00000000 2024-04-14 13:07:38.801 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'F:\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'MRH' 2024-04-14 13:07:38.801 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x100-0x1 Have you tried doing a repair of your DCS installation? It might also be worth thinking about renaming your DCS Saved games folder (something like Saved Games > DCS.Openbeta.old) and then try to start the game again and see if that lets it load up. If so, then it is something in the config files. You can copy back your input folder from the renamed Saved Games folder

The short answer is no - I also fly VR but regularly start MT without so I can use the Mission Editor more easily. Please could you post the DCS log created on a crash so we can have a look. This will be in your C:\Users\<you username>\Saved Games\<DCS instance>\Logs folder

You are running Tacview as well according to your log. It might be worth turning this off and seeing if the issue resolves itself. It would be useful if you could also post a log from a 'good' start to try and see where there are differences in the time taken to do things.

This is always a difficult topic since AV software needs to learn as well. Their advanced heuristic analysis does sometimes trigger incorrectly because of something it has calculated might be a threat. Sometimes this makes them overly aggressive.

and the screenshots brought a big smile to my face as well, having ended up like most of them at some point

I don't think Voiceattack / Vaicom will have done this as I run them happily with a Crystal. I agree with Hiob that system stress is worth investigating

I am guessing you are running Oculus software - the last Meta update has introduced something that requires a fix from ED. This should come in the next patch.

The last Meta update doesn't work with DCS. The DCS devs have fixed this internally for release in the next patch

Your sound sources in the log file mention an Oculus virtual device as well as Pimax. Do you still need Oculus? Not saying this is causing your issue.

This will be the Meta software update and therefore needs a compatability fix from ED since Meta don't give you a rollback option. The only workaround I am aware of is to use Virtual Desktop