Jump to content

Immediate Crash on start up in VR

outlaw04

By outlaw04
in Game Crash

 Share

Recommended Posts

MoleUK

MoleUK

Posted
Posted
2 minutes ago, Flappie said:

@outlaw04 @MoleUK According to this page, your issue with OpenXR is slightly different: 

2023-03-10 16:27:03.153 ERROR   VISUALIZER (8436): OpenXR exception: XrResult failure [XR_ERROR_RUNTIME_UNAVAILABLE]
    Origin: xrEnumerateInstanceExtensionProperties(nullptr, 0, &instanceExtensionCount, nullptr)
    Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:163
2023-03-10 16:27:03.183 INFO    VISUALIZER (8436): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S
2023-03-10 16:50:51.546 ERROR   VISUALIZER (6004): OpenXR exception: XrResult failure [XR_ERROR_RUNTIME_UNAVAILABLE]
    Origin: xrEnumerateInstanceExtensionProperties(nullptr, 0, &instanceExtensionCount, nullptr)
    Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:163
2023-03-10 16:50:51.580 INFO    VISUALIZER (6004): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S

 

 

"XR_ERROR_RUNTIME_UNAVAILABLE" means "the loader was unable to find or load a runtime". Chek your OpenXR installation, and see if @Igrok_kun's solution works for you.

 

Will do. To be clear i'm not trying to launch it in OpenXR. I'm specifically trying to NOT do that.

outlaw04

outlaw04

Posted
  • Author
Posted
On 3/10/2023 at 1:29 PM, MoleUK said:

Deleted mission editor folder, ran the repair. No joy, instant crash when trying to start in oculus api. Didn't even get an error that time, just closed itself. As I said I can launch in VD > OpenVR > SteamVR > DCS, but that's much less efficient overall. Single-threaded .exe still launches in Oculus API on VD just fine.

 

dcs.20230310-212717.crash 1.38 kB · 0 downloads dcs.20230310-212717.dmp 867.26 kB · 0 downloads dcs.log 22.37 kB · 4 downloads

 

So i did this and no Change

 

zulubravo

zulubravo

Posted
Posted

My problem dissapeared after I disabled "OpenXR Toolkit Companion app". I did not know I had that app, I probably instaled it long time ago.

I was going to try page file solution but it was already set to 50GB, my ram is 32GB.

MT seems to work fine,

(off topic)--->1.my warthog throttle went crazy( all buttons turn on and off randomy) 90% sure unrelated to DCS but it never happened before.

2. and somethig is weird with external shadows in the distance.

Seem like large portion of the map is in the shadow and it moves away as you approach it and it extends across the map in the F2 view zoomed out, it was following a line about east to west. It is weird I don't know how to describe it correctly. Tried different shadow settings, it is always there, on shadows low and ground shadows off seems like 90% of the time you are in the shadow regardles of cloud position. I need to investigate this more.

Other than that it is good for now.

  • Like 1
Flappie

Flappie

Posted
Posted

I found this: https://github.com/cmbruns/pyopenxr/issues/79

Quote

Analytics shows this error message "The loader was unable to find or load a runtime" is used as a search term by multiple folks in this repo. We should probably add a wiki page about this message so these folks can find some guidance. They probably don't have an active installed OpenXR runtime, such as SteamVR, Oculus, Monado, or Windows mixed whatever.

So it would seem your DCS "wants" to run OpenXR anyway.

Maybe you'll find a soluion in mbucchia's big post here:

 

@zulubravo Thanks for your feedback. 👍

@MoleUK@outlaw04 Please ensure "OpenXR Toolkit Companion app" is uninstalled.

---

MoleUK

MoleUK

Posted
Posted
57 minutes ago, Flappie said:

I found this: https://github.com/cmbruns/pyopenxr/issues/79

So it would seem your DCS "wants" to run OpenXR anyway.

Maybe you'll find a soluion in mbucchia's big post here:

 

@zulubravo Thanks for your feedback. 👍

@MoleUK@outlaw04 Please ensure "OpenXR Toolkit Companion app" is uninstalled.

Removed it, still no joy. Crash on launch when trying to open in Oculus API.

 

dcs.log dcs.log-20230312-103556.zip

Flappie

Flappie

Posted
Posted

I've just read this in your dxdiag log:

Quote

Display Tab 2: There is a problem with Virtual Desktop Monitor device. For more information, search for 'graphics device driver error code 22'

Is that normal?

Code 22 means your Virtual Desltop Monitor is disabled.

---

MoleUK

MoleUK

Posted
Posted (edited)
4 minutes ago, Flappie said:

I've just read this in your dxdiag log:

Is that normal?

Code 22 means your Virtual Desltop Monitor is disabled.

No idea not seen it before. Exact same process launches the non-MT exe without issue though.

Only way I can get the MT exe to launch on VD is via SteamVR on OpenVR still.

Edited by MoleUK
Flappie

Flappie

Posted
Posted

OK. I'm reaching my limits because VR is an unknown territory for me.

Please open a support ticket: log into DCS website, click "Support", then "Create a new ticket".

---

MoleUK

MoleUK

Posted
Posted
Just now, Flappie said:

OK. I'm reaching my limits because VR is an unknown territory for me.

Please open a support ticket: log into DCS website, click "Support", then "Create a new ticket".

No worries, VR is it's own can of worms. Cheers.

[MA] BigSwede

[MA] BigSwede

Posted
Posted (edited)

Been trying to start MT in VR, "E:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_steam_VR, but DCS crashes every time after it has loaded around 13-15%. Have done clean and repair several times, no joy, changed swap size, deleted MissionEditor, uninstall Norton........

No problem starting MT witout VR

Using HTC Cosmos Elite VR.

 

Edit: Suddenly it works, I don't know what was wrong. But I can start MT with bin-mt\DCS.exe, no --force.

 

dxdiag.txt dcs.log

Edited by [MA] BigSwede

Master Arms a Swedish combat flight sim community

https://www.youtube.com/@bigswedeA10

  • 9 months later...
  • 7 months later...
 Share
Go to topic listing

  • Recently Browsing   0 members

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