Jump to content

DCS-MT VR Crashes On Loading Screen

AndyB

By AndyB
in Game Crash

 Share
Go to solution Solved by Scendore,

Recommended Posts

AndyB

AndyB

Posted
Posted

DCS-MT crashes on the loading screen only in VR. It will load in 2D just fine. DCS-ST works just fine in both 2d and VR. I've repaired DCS, removed all user mods, cleared fxo and metashaders folders, uninstalled and reinstalled oculus app for Quest 3. I don't know what to do. I get 2 different crash logs. Somebody please help. 

 

# -------------- 20240730-163802 --------------
DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631)
C:\WINDOWS\SYSTEM32\VCRUNTIME140_1.dll
# C0000005 ACCESS_VIOLATION at 00007ff8c57911d1 00:00000000
SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew'
OS-Version: 10.0.22631 () 0x300-0x1
0x00000000000011d1 (VCRUNTIME140_1): __NLG_Return2 + 0x81
0x0000000000004957 (VCRUNTIME140_1): __CxxFrameHandler4 + 0x877
0x000000000000f886 (VCRUNTIME140): __C_specific_handler + 0x1E6
0x00000000000a50cf (ntdll): __chkstk + 0x1AF
0x0000000000020154 (ntdll): RtlUnwindEx + 0x274
0x000000000008f6ae (ntdll): __C_specific_handler + 0xDE
0x00000000000a504f (ntdll): __chkstk + 0x12F
0x000000000001e866 (ntdll): RtlFindCharInUnicodeString + 0xA96
0x00000000000a403e (ntdll): KiUserExceptionDispatcher + 0x2E
0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE
0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0
0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5
0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6
0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C
0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77
0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87
0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6
0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461
0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B
0x000000000090bdd8 (DCS): SW + 0x422578
0x000000000090a886 (DCS): SW + 0x421026
0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9
0x0000000000cb85de (DCS): SW + 0x7CED7E
0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D

 

# -------------- 20240730-163741 --------------
DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631)
X:\DCS World OpenBeta\bin-mt\Visualizer.dll
# C0000005 ACCESS_VIOLATION at 00007ff873d8360e 00:00000000
SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew'
OS-Version: 10.0.22631 () 0x300-0x1
0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE
0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0
0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5
0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6
0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C
0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77
0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87
0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6
0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461
0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B
0x000000000090bdd8 (DCS): SW + 0x422578
0x000000000090a886 (DCS): SW + 0x421026
0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9
0x0000000000cb85de (DCS): SW + 0x7CED7E
0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D
 

dcs.log-20240730-163802.zip dcs.log-20240730-163741.zip

rob10

rob10

Posted
Posted

Those logs are still showing a whole bunch of errors/warnings due to mods.  Check that you have actually removed them all from your saved games folder.

The other thing you can try would be RENAME your DCS saved games file (so you don't lose anything if that doesn't work).  DCS will create a "clean" new one and see if it launches at that point.

AndyB

AndyB

Posted
  • Author
Posted
18 minutes ago, rob10 said:

Those logs are still showing a whole bunch of errors/warnings due to mods.  Check that you have actually removed them all from your saved games folder.

The other thing you can try would be RENAME your DCS saved games file (so you don't lose anything if that doesn't work).  DCS will create a "clean" new one and see if it launches at that point.

Unfortunately that didn't work either. Still getting the same issue. I removed all mods from saved games. 

# -------------- 20240730-171130 --------------
DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631)
C:\WINDOWS\SYSTEM32\VCRUNTIME140_1.dll
# C0000005 ACCESS_VIOLATION at 00007ffd433811d1 00:00000000
SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew'
OS-Version: 10.0.22631 () 0x300-0x1
0x00000000000011d1 (VCRUNTIME140_1): __NLG_Return2 + 0x81
0x0000000000004957 (VCRUNTIME140_1): __CxxFrameHandler4 + 0x877
0x000000000000f886 (VCRUNTIME140): __C_specific_handler + 0x1E6
0x00000000000a50cf (ntdll): __chkstk + 0x1AF
0x0000000000020154 (ntdll): RtlUnwindEx + 0x274
0x000000000008f6ae (ntdll): __C_specific_handler + 0xDE
0x00000000000a504f (ntdll): __chkstk + 0x12F
0x000000000001e866 (ntdll): RtlFindCharInUnicodeString + 0xA96
0x00000000000a403e (ntdll): KiUserExceptionDispatcher + 0x2E
0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE
0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0
0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5
0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6
0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C
0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77
0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87
0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6
0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461
0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B
0x000000000090bdd8 (DCS): SW + 0x422578
0x000000000090a886 (DCS): SW + 0x421026
0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9
0x0000000000cb85de (DCS): SW + 0x7CED7E
0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D

 

# -------------- 20240730-171119 --------------
DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631)
X:\DCS World OpenBeta\bin-mt\Visualizer.dll
# C0000005 ACCESS_VIOLATION at 00007ffcea13360e 00:00000000
SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew'
OS-Version: 10.0.22631 () 0x300-0x1
0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE
0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0
0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5
0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6
0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C
0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77
0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87
0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6
0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461
0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B
0x000000000090bdd8 (DCS): SW + 0x422578
0x000000000090a886 (DCS): SW + 0x421026
0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9
0x0000000000cb85de (DCS): SW + 0x7CED7E
0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D
 

 

  • Solution
Scendore

Scendore

Posted
  • Solution
Posted (edited)
  1. The Recent Meta Update Breaks VR for DCS. Here is the fix. Meta has started to use OpenXR within the Meta App after this update which affects the Link Cable. So you go to the Open XR Tool Kit which I'm assuming you're using and check the disable checkbox. It will default to Meta. There is a catch in that the OpenXR Menu will not pop up and your headset settings will be defaulted to Auto. So go back to the headset settings with the Meta App and reset your preferences like Refresh and Scaling. IL2 and DCS are running fine.
     
Edited by Scendore
  • Like 5
AndyB

AndyB

Posted
  • Author
Posted
1 hour ago, Scendore said:
  1. The Recent Meta Update Breaks VR for DCS. Here is the fix. Meta has started to use OpenXR within the Meta App after this update which affects the Link Cable. So you go to the Open XR Tool Kit which I'm assuming you're using and check the disable checkbox. It will default to Meta. There is a catch in that the OpenXR Menu will not pop up and your headset settings will be defaulted to Auto. So go back to the headset settings with the Meta App and reset your preferences like Refresh and Scaling. IL2 and DCS are running fine.
     

 

That did it, Thank You!

Ratcatcher

Ratcatcher

Posted
Posted

Glad that worked for you. Unfortunately doesn't for myself.

Had no issue with this until today after Oculus decided to update itself after the META/FB bull<profanity>try DOB requirement kicked in and like a fool I allowed it to go ahead and update my QP software, even though it had been working fine...stupid stupid boy!!!

  • Like 1

Techlabs Chameleon Watercooled Gaming PC - Intel Core i7 6700K @ 4.7GHz : Samsung 950 Pro 256GB SSD, Samsung 500 gig SSD, Seagate 1TB 7200RPM Drive : MSI GeForce GTX 1080 "Founders Edition" 8192MB : 800W '80 Plus Gold' Modular Power Supply : 32GB (2x16GB) DDR4 PC4-25600C16 3200MHz : Occulus Rift S : TM Warthog : MFG Crosswind V2 : Win 10 64. PointCTRL.

Mailman76

Mailman76

Posted
Posted
On 7/30/2024 at 3:53 PM, Scendore said:
  1. The Recent Meta Update Breaks VR for DCS. Here is the fix. Meta has started to use OpenXR within the Meta App after this update which affects the Link Cable. So you go to the Open XR Tool Kit which I'm assuming you're using and check the disable checkbox. It will default to Meta. There is a catch in that the OpenXR Menu will not pop up and your headset settings will be defaulted to Auto. So go back to the headset settings with the Meta App and reset your preferences like Refresh and Scaling. IL2 and DCS are running fine.
     

 

This also worked for me.  Thanks!

Running in VR can be such a pain, I went to the extreme after trying several times to get it to work and ended up deleting all of DCS and reinstalling.

CH4Pz

CH4Pz

Posted
Posted
On 7/31/2024 at 7:23 AM, Scendore said:
  1. The Recent Meta Update Breaks VR for DCS. Here is the fix. Meta has started to use OpenXR within the Meta App after this update which affects the Link Cable. So you go to the Open XR Tool Kit which I'm assuming you're using and check the disable checkbox. It will default to Meta. There is a catch in that the OpenXR Menu will not pop up and your headset settings will be defaulted to Auto. So go back to the headset settings with the Meta App and reset your preferences like Refresh and Scaling. IL2 and DCS are running fine.
     

 

Here i am thinking its the mods/missions i just added, spending 30 minutes removing and testing one by one... i shouldve known, damn zuckerberg!!

Ratcatcher

Ratcatcher

Posted
Posted

Small update from my experience...After trying everything mentioned and a few other things found in other threads to no avail, I noticed my GFX driver was out of date. Updated and what do you know!!! Working again!

  • Like 1

Techlabs Chameleon Watercooled Gaming PC - Intel Core i7 6700K @ 4.7GHz : Samsung 950 Pro 256GB SSD, Samsung 500 gig SSD, Seagate 1TB 7200RPM Drive : MSI GeForce GTX 1080 "Founders Edition" 8192MB : 800W '80 Plus Gold' Modular Power Supply : 32GB (2x16GB) DDR4 PC4-25600C16 3200MHz : Occulus Rift S : TM Warthog : MFG Crosswind V2 : Win 10 64. PointCTRL.

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...