Jump to content

Recommended Posts

Posted

I don't get it:

Shouldn't MT DCS (not Steam version, actual stable version) start in SteamVR if not forced by "-- force_openxr" argument? I tried "--force_vr --force_openxr" and either it stalls while in loading screen (sometimes 11%, sometimes 87%) or it enters the game but the image in my Pimax8KX headset is frozen (still headtracking the scene, not in the scene, but like a movie screen) and no mouse input possible. Starting with --force_disable_vr works, but puts me into 2D, of course. Starting with "--force_openxr" either set or not set doesn't change anything, not even SteamVR comes up.

 

ST works in both VR and 2D.

  • ED Team
Posted

Hi, 

please have a read here it should help 

you are creating a shortcut from the bin-mt folder and the DCS.exe and for VR adding the VR parameters

How can I launch VR in MT? 
Same way you do now but using the bin-mt/ dcs.exe with the added launch parameters. ( example "C:\DCS\bin-mt\DCS.exe" --force_enable_VR )
Steam users will have a MT VR option in the launch pop up. Or try starting in 2D and enabling VR in the DCS VR tab, then restarting DCS.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted (edited)

No change. I corrected the start parameters to "\...\DCS.exe" --force_enable_VR, program stalls in loading screen at 38%. With --force_enable_VR --force_openxr it at least finishes the loading screen but mouse cursor (that dot) isn't responding and program seems to have frozen (kill process in task manager).

Loading DCS MT in (prior to this I had to --force_disable_vr) 2D, then tagging "VR headset" in VR, hitting ok -> restart gets me to 2D but with VR headset tagged. Shutdown and launch DCS.exe without any parameters stalls at 82%.

"Hot plug" is disabled.

 

dcs.log throws this out "VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE"

 

edit: I disabled OpenXR Toolkit, too. No change, program just freezes after loading to main screen.

Edited by void68
Posted

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

  • 2 weeks later...
Posted

Thanks, but I don't understand how that thread may be of any help.

Last entry by user Yoyo says "Only ST version works with OXR or OVR (SteamVR), MT only OXR. ". The post you relate to says "With OpenXR supported in the game, you do not need OpenComposite anymore, regardless of what headset you use.". I use OpenXR standalone, no OpenComposite anymore.

 

What I did (after I flushed MT out of my PC): installed the new PimaxRuntime 0.3.4 and the Toolkit 1.3.2 and it seems to work now. I was very cautious and hesitating to "just update it" as the previous updates on the previous stable release of DCS broke VR. Had to go back to older XR releases.

Thanks for giving me the kick to dig into it again!

Posted
5 hours ago, void68 said:

Thanks, but I don't understand how that thread may be of any help.

I wanted you to take note of what is adviced there specifically for Pimax users.

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

  • Recently Browsing   0 members

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