Jump to content

Recommended Posts

Posted (edited)

See the post in here:

 TL;DR 

OpenComposite used to translate everything from DCS to OpenXR.  OpenComposite is not OpenXR. *Since last update* - no more translators needed.

So, add "--force_enable_VR --force_OpenXR" commands to the game's startup shorcut like this: "C:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR

And everything should work fine (at least for myself all works perfect with my G2).

Edited by nickos86
  • Like 1
Posted
11 minutes ago, nickos86 said:

 TL;DR 

OpenComposite used to translate everything from DCS to OpenXR.  OpenComposite is not OpenXR. *Since last update* - no more translators needed.

So, add "--force_enable_VR --force_OpenXR" commands to the game's startup shorcut like this: "C:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR

And everything should work fine (at least for myself all works perfect with my G2).

 

It doesn't work (for most) with motion reprojection. That is why some are going back to the old method.

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Posted (edited)

Sorry but i'm feeling abit overwhelmed  with information and am unsure what I need to do?

I have a G2 and uninstalled Steam ages ago to use the other thing that was better.

For some reason I have to have motion reprojection on to make the game playable (auto isnt good enough).

What do I need to do/install to get me flying again please?

Thx in advance

Edited by parxuk
  • Like 2

Intel i7 8700K @ 5Ghz, Aorus Z370 Gaming5, 32GB Corsair Vengeance RGB Pro 3000MHz, Nvidia 3080Ti FE, Samsung 970 NVME, Samsung 512GB EVO SSD x 2, Thrustmaster Warthog HOTAS, Saitek Rudder Pedals, HP Reverb G2, Windows 11 x64, DCS Modules = FC3, A10c Warthog, F14 Tomcat, F18 Hornet, F16 Viper, Persian Gulf, Syria.

Posted
9 minutes ago, parxuk said:

Sorry but if feeling abit overwhelmed  with information and am unsure what I need to do?

I have a G2 and uninstalled Steam ages ago to use the other thing that was better.

For some reason I have to have motion reprojection on to make the game playable (auto isnt good enough).

What do I need to do/install to get me flying again please?

Thx in advance

Download the dll from here https://znix.xyz/OpenComposite/download.php?arch=x64&branch=openxr

Backup your openvr_api.dll in your DCS World installation folder\bin folder

Copy the downloaded dll into the bin folder

That should be all you need assuming you had OpenXR running previously.

When it gets fixed just let DCS update and it will overwrite the DLL.

  • Like 4

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Posted

Update: Quest2 works, quite brilliantly. Not as great as Pico4 and there are still ghosting at times. I am happier now.

2023-01-29 14:11:14.855 INFO    VISUALIZER (Main): LAUNCH IN VR OpenXR: Oculus Quest2

Side note: no "above and beyond" problem I have with Pico4. The main menu sits where it should be

I would wait for some time and revisit Quest 2 just to make sure. And I shall test XRNeckSafer also but I guess it should work.

It makes me suspect that there may be an issue with SteamVR, which, I would not be surprised.

I Fly, Therefore I Am.

One cannot go around not saying "Thank you" every time these days, can't you?

YouTube: https://www.youtube.com/channel/UCc9BDi-STaqgWsjNiHbW0fA

Posted
9 minutes ago, Baldrick33 said:

Download the dll from here https://znix.xyz/OpenComposite/download.php?arch=x64&branch=openxr

Backup your openvr_api.dll in your DCS World installation folder\bin folder

Copy the downloaded dll into the bin folder

That should be all you need assuming you had OpenXR running previously.

When it gets fixed just let DCS update and it will overwrite the DLL.

Thanks Baldrick

Intel i7 8700K @ 5Ghz, Aorus Z370 Gaming5, 32GB Corsair Vengeance RGB Pro 3000MHz, Nvidia 3080Ti FE, Samsung 970 NVME, Samsung 512GB EVO SSD x 2, Thrustmaster Warthog HOTAS, Saitek Rudder Pedals, HP Reverb G2, Windows 11 x64, DCS Modules = FC3, A10c Warthog, F14 Tomcat, F18 Hornet, F16 Viper, Persian Gulf, Syria.

Posted (edited)
36 minutes ago, VR Flight Guy in PJ Pants said:

I am not sure if OpenComposite is still needed due to the fact that DCS World can now "speak" OpenXR natively. But fingers crossed.

Difference is huge, with OpenComposite you can use OpenXR Motion Reprojection = always on, without this stock DCS OB crashes if you turn it on. So right, DCS speaks or wants to speak but it doesnt recive right answare :D. Question have to be fixed ;).

Edited by YoYo
  • Like 1

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
41 minutes ago, VR Flight Guy in PJ Pants said:

I am not sure if OpenComposite is still needed due to the fact that DCS World can now "speak" OpenXR natively. But fingers crossed.

It is needed if you want to run motion reprojection (with WMR at least).

  • Like 2

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Posted (edited)

Has anyone figured out what is causing the freezing when using Turbo mode on OpenXR with Quest 2? I have spent few hours changing every possible setting and nothing seems to help. 

The performance increase turbo mode offers is pretty incredible. I would love to get it to work. 

Edited by ssg
Posted
On 1/28/2023 at 6:28 AM, Hotdognz said:

To me it seems ED haven't achieved anything yet with this OpenXR rollout except to cause confusion amongst its user base and some angst with users who were not tech savvy which wasn't helpful at all, it took a few of us quite some time trying to help others out and getting information from here to our Discord on what was working and what wasn't and getting them sorted out with a broken DCS install.

I do hope ED can learn from this and any future updates to OpenXR in a future patch make it easier for the lest tech savvy to use and understand, include instructions on what to do and what it means to them and also properly test it first before rolling out a massive change like this as it obviously it wasn't tested by many beta testers with VR as the MR issue would have been picked up very quickly.

OpenXR is a great change and very welcome, but we need a solid release with release notes and documentation of the changes from ED going forward.

 

Exactly. If starting the game without freezes becomes more complicated than flying the Tomcat - both seats - a proper documentation, guide and tutorial video should be ready when the patch goes live. Also, ED long time ago should have made a deal with Skate Zilla and incorporate his launcher as a official DCS tool, upgrade it with options like openxr ON or OFF or at least do the Apple way and bake a new launcher. 

Posted
48 minutes ago, dmatt76 said:

Exactly. If starting the game without freezes becomes more complicated than flying the Tomcat - both seats - a proper documentation, guide and tutorial video should be ready when the patch goes live. Also, ED long time ago should have made a deal with Skate Zilla and incorporate his launcher as a official DCS tool, upgrade it with options like openxr ON or OFF or at least do the Apple way and bake a new launcher. 

Whilst I have been vocal about the implementation and lack of prior communication, I do believe we need to be careful not to stifle innovation, it is what many of us strive for in a continual development environment. I tend to take the opposite view, if users are expected to handle incredibly complicated aircraft systems that top pilots take years to learn, then a bit of IT learning shouldn’t be too much to ask in the field of VR which is still something of a niche (and a bit nerdy!) tech.

if we want it super polished then expect to wait a bit more than two weeks…

  • Like 6

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Posted
Whilst I have been vocal about the implementation and lack of prior communication, I do believe we need to be careful not to stifle innovation, it is what many of us strive for in a continual development environment. I tend to take the opposite view, if users are expected to handle incredibly complicated aircraft systems that top pilots take years to learn, then a bit of IT learning shouldn’t be too much to ask in the field of VR which is still something of a niche (and a bit nerdy!) tech.
if we want it super polished then expect to wait a bit more than two weeks…
Agreed, and well put

14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero

Posted

DCS never seems to start in openXR mode for me. Please advice.

What i get:

Launching via SteamVR with  openXR runtime configured (it says in the developer options: "windows mixed reality")

DCS log file: VISUALIZER (Main): LAUNCH IN VR OpenVR: OpenVR : Oculus Quest2


Launching via Oculus Home with OpenXR set as the active runtime (not Oculus runtime)

VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S

 

I've tried using the command line options both through a shortcut and configured in steam. --force_openXR is never respected.

Obviously the Companion app overlay is never shown.

Please help.

Posted (edited)
vor 23 Minuten schrieb dutchili:

DCS never seems to start in openXR mode for me. Please advice.

What i get:

Launching via SteamVR with  openXR runtime configured (it says in the developer options: "windows mixed reality")

DCS log file: VISUALIZER (Main): LAUNCH IN VR OpenVR: OpenVR : Oculus Quest2


Launching via Oculus Home with OpenXR set as the active runtime (not Oculus runtime)

VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S

 

I've tried using the command line options both through a shortcut and configured in steam. --force_openXR is never respected.

Obviously the Companion app overlay is never shown.

Please help.

This is the same behaviour I'm getting, the option "--force_openXR" does not seem to be respected for Oculus headsets at least.

I've also noticed that any option of Asynchronous Spacewarp except forcing it to off does decrease performance and comes with heavy stutters. This is the first thing I noticed when it switched to OpenXR during the patch before the hotfix. So now the weird thing is the ASW performance seems to be like it was with OpenXR (not usable), while according to the log OpenXR isn't even used, even when forced as stated before.

Would be nice if more Oculus users (I'm using CV1, dutchiili Quest 2) could report their findings about all this so far.

Edited by T-Pickle
Posted

I am actually using a quest 2. So the log is definitely wrong.

If i set the picked software to use Oculus runtime performance is slightly worse. This also makes me think that they log entry is wrong or... All is wrong

Posted (edited)

I think I just screwed something up because I deleted this OpenComposite folder on my Desktop now when I start DCS my VR does not start. I have the command line in my short  "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OPENXR   and its been work fine all day. But after deleting that folder DCS only boots in 2D. I see nothing in the bin folder that says openxr.dll but do see an openvr_api.dll  Deleting that OpenComposite folder corrupted something as my G2 and OXR is not recognize. This stuff is waaaay over my head. I did a slow repair twice with no luck. Would my log.file help to pin point my cause?  

Can anyone look at this log file to see why I'm having this issue. This was after a DCS slow repair. Thanks

dcs.log

Edited by Burt

ALIENWARE R11 - I9 10900KF @ 5.1 GHz - M.2 NVMe 2TB - RTX3090  - XFURY 64GB -3400 MHz RAM

Monitor AW3420DW @ 120Hz - Virpil CM3 Throttle - TM TPR Rudder pedals - Virpil CM2 w/TM Hornet Stick Center - Monstertech Deck Mounts 

RealSimulator FSSB-R3 Lightning Base w/ F16SRGRH SideStick - VR user / Varjo Aero - Big Thx to mbucchia

Start Date April 2020 

 

Posted

I have been using open composite for a while and has been working perfect. And it still is with my G2 reverb on Win 10. But my brother is trying to use OpenXR with opencomposite with his HTC vive cosmos, he gets really good fps, then stutter fest, then good again, so it is un-flyable.

But we then tried to use the "force dcs to openXR" by adding that line in the dcs.exe shortcut. And then it do work and does not stutter at all, and the Toolkit works as intended as well. 

But the problem by forcing the new native OpenXR his VR headset is out of center. So when he use the VR Re-center in DCS he is really high up and the center is off to the right. So in the AH64 the HUD you have in front of your eye(s) is not centered. We have followed the instructions for HTC Vive. When switching back to Steam the center is correct.

Is there any other place you can adjust the center besides in game via numpad 5 command(the one in UI Layer)?

And It does not help by moving the Cockpit camera since you can't move them far enough + that the AH64 hud is offset to the right. 

Ryzen 7 7800x3D, 32GB, Nvidia RTX 4090, Nvme SSD's, HP Reverb G2, Oculus Q3, Open XR

Posted
21 hours ago, Nealius said:

The "switch" being "Oculus set as active OpenXR runtime" setting? I tried appending the forced OpenXR command to DCS.exe and got "unrecognized command" error.

Oculus has to be set as active OpenXR runtime in oculus app to work properly with native OpenXR  DCS.

The switch I mentioned is this

"C:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR. Note the space after .exe"

MAIN SYSTEM SPECS: MSI PRO Z690-A WIFI DDR4, Intel Corei7-12700K @ 5.0, 64Gb RAM Kingston KF3600C18D4/16GX, EVGA RTX 3080 FTW3 ULTRA GAMING 12GB, Samsung SSD 970 EVO Plus 1TB, Virpil T50CM3 Throttle, VKB Gunfighter MkIV Ultimate with 20cm extension, VKB T-Rudder MKIV, Quest Pro

Laptop SPECS: Alienware X16 R2, Intel Core Ultra 9 185H, RTX 4090 mobile 16GB, 32GB LPDDR5X, 2TB Micron NVMe
 

SOFTWARE: Microsoft Windows 11

Posted
Just now, dutchili said:

Thanks.

I need a solution for steam. These command do not work in steam.

@BIGNEWY

It works, show screenshot how did you set it.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
6 hours ago, ismaeljorda said:

 

Thx, looks looks like native solution works a little better. So my fingers are crossed harder for ED to solve MR Always on bug soon ;). With OC no this issue.

  • Thanks 1

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

  • Recently Browsing   0 members

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