hornblower793

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

From other posts there was a Meta upgrade this morning to v64 and that means that DCS will not start in VR for Meta users

I think so - open Oculus and uncheck PTC (I think, but I no longer run an Oculus headset)

Please could you attach the log for trying to run with standard launch

I still think this is the Oculus PTC issue. The old log stops at exactly the point where the VR should load in. The newer log just stops with a message that Steam requested a restart. Does it run if you start in screen rather than VR mode?

It looks like it is erroring in your graphics card drivers (or the MS driver) 2024-03-08 02:27:57.366 INFO EDCORE (9280): try to write dump information 2024-03-08 02:27:57.374 INFO EDCORE (9280): # -------------- 20240308-022757 -------------- 2024-03-08 02:27:57.375 INFO EDCORE (9280): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.19045) 2024-03-08 02:27:57.376 INFO EDCORE (9280): C:\Windows\System32\DriverStore\FileRepository\u0400566.inf_amd64_5e4d397bddb6fe15\B400392\amdxx64.dll 2024-03-08 02:27:57.376 INFO EDCORE (9280): # C0000005 ACCESS_VIOLATION at 00007ffb8b8e44e2 00:00000000 Might be worth checking https://www.exefiles.com/en/dll/atidxx64-dll/

The easy solution is to take a back-up of your configs once you have got them set to your liking (found in C:\Users\<username>\Saved Games\<DCS instance>\Config\Input and then just copy them back if your files get corrupted. I also use Joypro as a mapping tool so that changing a controller takes a matter of seconds to reapply all mappings.

I think you have the PTC option enabled in Oculus - this has been stopping all Meta headsets at the same point in the log. Disable PTC and you should be good to go

Just checking the obvious because I have forgotten to do this before - have you set the airfield to be part of the same coalition as your plane?

Next time it crashes please could you attach the DCS log file to your post. It will help to see whether the error is caused by the same issue

There are lots of users with the install prompt appearing

Great

Have you tried without loading LotATC, SRS, Tacview and any other addons?

Flappie beat me to it

Glad it is working - enjoy the flight

This issue sounds like you might have PTC selected in the Oculus app as this is known to currently stop DCS working. Unselect PTC and you should be good to go The versions are united now (everyone got the download) but it currently remains showing as OB or stable depending on what you updated. The error implies that GraphicsCore.dll is corrupted, but it could also be something to do with a Windows file. Have you tried running sfc to check for errors https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Also, have you tried to run a repair of the Steam installation. Right click on DCS in your library and then select properties>installed files>verify integrity of files

A couple of thoughts: 1. Are either of you running Oculus VR as the PTC option in the Oculus software is known to be incompatible at the moment. 2. Please could you post your DCS log file from C:\Users\<your username>\Saved Games\<your DCS install>\Logs (assuming it gets this far). I run standalone version so cannot really help debug Steam, although I do use Steam for other games. Have you tried going to the Steamapps folder for DCS and running the exe directly from the bin (for ST) or bin-mt (for MT) exe folder?

This - imgui.dll should be in the bin and bin-mt folders for the install

I think your log shows you are running ST D:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe --force_enable_VR MT should be in the bin-MT folder

How much space is available on the drive? IIt might be worth clearing out temp / backup files

Single / multi threaded for your CPU. It affects how DCS uses the cores available in your processor (rather than your graphics card).

Are you using VR, in particular an Oculus device (you have an Oculus device listed in audio)? Your log stops at the point where VR loads in. If you are then there is a known issue with the latest PTC Oculus driver and you need to roll it back

Having looked at your log file it looks like it is at the point where it tries to initialise your VR headset so I think you probably need to roll back to the last version of the Oculus software. ['civTraffic'] = ''; ['ScreenshotExt'] = 'jpg'; }; 2024-02-16 16:58:20.403 INFO VISUALIZER (Main): VRG skip, ask for support if you own VRG helmet My log file at the same point is: ['civTraffic'] = 'low'; ['ScreenshotExt'] = 'jpg'; }; 2024-02-15 20:02:47.272 INFO VISUALIZER (Main): LAUNCH IN VR OpenXR: Pimax Crystal2024-02-15 20:02:47.273 INFO VISUALIZER (Main): render thread initialization... 2024-02-15 20:02:47.278 INFO GRAPHICSVISTA (8392): renderer: 'dx11backend.dll' 2024-02-15 20:02:47.352 INFO DX11BACKEND (8392): DX11Renderer initialization (w:1176 h:1392 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1) 2024-02-15 20:02:47.422 INFO DX11BACKEND (8392): Driver Concurrent Creates - 1 2024-02-15 20:02:47.422 INFO DX11BACKEND (8392): Driver Command Lists - 1 2024-02-15 20:02:47.549 INFO DX11BACKEND (8392): NVIDIA API init OK 2024-02-15 20:02:47.550 INFO DX11BACKEND (8392): NVIDIA Display Driver Version 55152.r551_06 I know my file is from yesterday, but I have just logged in now to check it works