OpenXR Guide - Deprecated - This time for real (▀̿Ĺ̯▀̿ ̿)

[RvL]

8 hours ago, Hammer1-1 said:

 

 

Think I get it...

edit: ok yeah that worked!  Thanks!

you're supposed to delete that beforehand.

 

I did delete it beforehand. I did exactly like the instructions.

[scorch71]

Super new to VR, Followed the install instructions, I cleaned and rebuilt DCS, but I got this at start up and a Crash? Can anyone please point me in the right direction? Thanks

[TED]

2 hours ago, scorch71 said:

Super new to VR, Followed the install instructions, I cleaned and rebuilt DCS, but I got this at start up and a Crash? Can anyone please point me in the right direction? Thanks

Error 2 is a runtime error. I was getting this when I installed again for a while and not 100% sure how I fixed it.

Try uninstalling and reinstalling the toolkit and make sure your openxr for Windows is latest version from the ms store. 

The other possibility is one of the 3 files is corrupt. Check the bin folder see if the compiler is duplicated. Failing that remove the 3 files from bin and download them from new. I think someone provided a Dropbox link earlier. Then drop them in your bin folder again. 

[DeltaMike]

Is there a "best practices" approach to troubleshooting those runtime errors?  I spent a little quality time in the discords this morning looking at this.  I'm not sure there's anything new under the sun.  Here's what I came up with -- for G2, Quest has its own issues -- recognizing I'm simply restating what's already in the first post in this thread.  Which is worth reading, folks...

1.  Update windows, turn off HAGS (if there's no option for that, don't worry about it), turn off background programs (RGB, voice attack, winsimapp, etc etc)
2. Un-f*** DCS.  Uninstall all mods, especially shader mods, especially ReShade.  (Mod manager is your friend.) Set pixel density to 1.0 and leave it there.    Clean DCS using Skatezilla.  Tell Skatezilla to use the SteamVR interface (under "rendering driver"), but make sure you have WMR set NOT to start SVR, and make sure you aren't starting DCS with the --force_steam_vr argument.  By starting it from Skatezilla.  
3. Clear shaders files (metashaders and fxo folders)
4. Rename D3DCompiler_47.dll and delete opencomposite.ini (if it's still there, which it shouldn't be if DCS was cleaned properly)
5. See if OXR is working.  Do this without the OXR Toolkit.  If you've already installed the OXR toolkit, you don't have to uninstall it, but definitely de-activate it for this test.
   1. Open the OXR Developer Tools (the one you download from the Microsoft store)
   2. Check version
   3. Check settings.   Check resolution at 100% or less, and check motion reprojection off.
   4. Pull up the "demo scene."  
   5. If OXR isn't working, or is out of date, follow procedures for re-install (ie unintstall the three programs and then re-install using procedures in the first post)
6. Once we are sure OXR is working, activate the OXR Toolkit (the one you download from Github)
   1. Check version
   2. Check scaling off (if scaling -- FSR or NIS -- is causing the error, there's a registry edit for that)
   3. ?  It seems some systems just don't like the OXR toolkit

Does that sound about right?  What am I missing?

I found one case where pushing resolution >150% caused issues, several instances where OXR was out of date, one where old ReShade files seemed to be causing issues, and generally a lot of not following procedure / skipping steps / making things more complicated than it needs to be.  And I get the feeling a lot of that comes from not using Skatezilla, which I think is a key to success here

Edited May 2, 2022 by DeltaMike

[Ghostman]

Hey DeltaMike in step 3. Rename D3DCompiler_47.dll  what do you rename it too?

Thanks

[Lange_666]

Whatever, D3DCompiler_47.org or something.

[Hive]

59 minutes ago, DeltaMike said:

2. Un-f*** DCS.  Uninstall all mods, especially shader mods, especially ReShade.  (Mod manager is your friend.) Set pixel density to 1.0 and leave it there.    Clean DCS using Skatezilla.  While Skatezilla should specify the SteamVR API (it says "runtime" but it means "API"), make sure you have WMR set NOT to start SVR, and make sure you aren't starting DCS with the --force_steam_vr argument.  By starting it from Skatezilla.

 

Thank you very much for this guide. One question as I never used Skatezilla before: Will it keep all settings and bindings after that procedure? Just to be sure.

[DeltaMike]

In my experience with Skatezilla it has never messed with my settings and bindings.  I don't think it does anything inside your saved games folder, far as I know

That said, it's never a bad idea to have a copy of your saved games folder on an external drive, that'll be a lifesaver someday

Speaking of the saved games folder, let's see what @nikoel says about all this, I think clearing that folder is part of his troubleshooting regime...  so yeah, make a backup now while you're thinking about it

[sze5003]

In my experience with Skatezilla it has never messed with my settings and bindings.  I don't think it does anything inside your saved games folder, far as I know
That said, it's never a bad idea to have a copy of your saved games folder on an external drive, that'll be a lifesaver someday
Speaking of the saved games folder, let's see what @nikoel says about all this, I think clearing that folder is part of his troubleshooting regime...  so yeah, make a backup now while you're thinking about it

I think it is recommended to delete the saved games folder for dcs prior to doing any of the open xr updates/install. But actually you just back it up somewhere and then delete it. Run through the open xr configuration and installation, then once everything launches without issues, you can put your saved games folder back.

[TylerPL666]

1 hour ago, DeltaMike said:

While Skatezilla should specify the SteamVR API (it says "runtime" but it means "API"), make sure you have WMR set NOT to start SVR, and make sure you aren't starting DCS with the --force_steam_vr argument.  By starting it from Skatezilla.  

mine is:

 

keep steam close. I dont run it for weeks. Run WMR first, clean enviorement, use seat mode.

Edited May 2, 2022 by TylerPL666

[nikoel]

28 minutes ago, DeltaMike said:

In my experience with Skatezilla it has never messed with my settings and bindings.  I don't think it does anything inside your saved games folder, far as I know

That said, it's never a bad idea to have a copy of your saved games folder on an external drive, that'll be a lifesaver someday

Speaking of the saved games folder, let's see what @nikoel says about all this, I think clearing that folder is part of his troubleshooting regime...  so yeah, make a backup now while you're thinking about it

Not much to add. This is 100% correct. And I also have a backup because I have trust issues with SimAppPro (but that’s neither here nor there) 

I always clear metashaders and fxo when I make big changes 

Also I Launched OpenComposite.exe today and update notification came up. Clicked on the update button. It fetched everything automagically, double clicked DCS and it launched. Looks like that’s all she wrote and all we gotta do is open the app every now and then to update

[DeltaMike]

2 minutes ago, nikoel said:

Not much to add. This is 100% correct. And I also have a backup because I have trust issues with SimAppPro (but that’s neither here nor there) 

I always clear metashaders and fxo when I make big changes 

Also I Launched OpenComposite.exe today and update notification came up. Clicked on the update button. It fetched everything automagically, double clicked DCS and it launched. Looks like that’s all she wrote and all we gotta do is open the app every now and then to update

Edited

I've been timing my trips perfectly lately -- sounds like I was out of town just long enough to get that merge sorted out.  Thanks for all you do.  Gonna try life in the fast lane (60fps/60hz) today. Wish me luck

[markturner1960]

On 5/1/2022 at 10:54 AM, speed-of-heat said:

The OXRTK stores its settings in the registry, which means you can use a *.reg file to make them portable.

These are my current settings for DCS, which is for my HP Reverb G2, and my FOV is slightly wider than normal I am using motion reprojection, if you have a different headset these may not be the right choices for you.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\OpenXR_Toolkit\OpenComposite_DCS]
"module"="E:\\Games\\Eagle Dynamics\\DCS World Openbeta\\bin\\DCS.exe"
"first_run"=dword:0000000b
"scaling_type"=dword:00000002
"vrs"=dword:00000002
"saturation_mode"=dword:00000000
"saturation_red"=dword:00000258
"saturation_green"=dword:00000258
"saturation_blue"=dword:00000258
"expert_menu"=dword:00000001
"vrs_pattern"=dword:00000000
"mipmap_bias"=dword:00000001
"motion_reprojection_rate"=dword:00000001
"vrs_quality"=dword:00000001
"vrs_x_scale"=dword:0000008c
"sharpness"=dword:0000000a
"overlay"=dword:00000000
"scaling"=dword:0000005f
"vrs_inner_radius"=dword:00000046
"vrs_outer"=dword:00000003
"vrs_prefer_horizontal"=dword:00000001
"vrs_x_offset"=dword:00000000
"vrs_middle"=dword:00000001
"prediction_dampen"=dword:00000064
"saturation"=dword:00000258
"post_process"=dword:00000001
"post_vibrance"=dword:00000000
"post_saturation"=dword:00000208
"post_sunglasses"=dword:00000000
"post_shadows"=dword:00000000
"post_gain_b"=dword:000001f4
"bypass"=dword:00000000
"menu_timeout"=dword:00000001
"vrs_inner"=dword:00000000
"vrs_y_offset"=dword:00000000
"post_contrast"=dword:000001f8
"post_brightness"=dword:000001c2
"world_scale"=dword:000003e8
"vrs_outer_radius"=dword:0000005a
"vrs_lr_bias"=dword:00000000

1) note the line module, will need to be changed to reflect your DCS exe path

2) then save it as OpenComposite_DCS.reg,

3) double click on the saved file and select YES and then YES again to apply these changes.

as with any change to the registry, it's your fault, understand what they are going to do.

 

 

 

when I try that, I get an error saying its not a registry script?

[TylerPL666]

After every instalation/deinstalation of any shader mod (like 3DMigoto) I use DCS-Update-Witching-Utility to Clear Terrain Metacache, and FXO + Metashaders2.

Prefiously I was using DCS Updater Utility option to Clear Metashaders2 and FXO every time I instal something new. It have to be a habit for people that mess up with files.

Those programs have very similar function, Wiching have +1 option for that Terrain Metacache - to be honest have no idea what it is, but if its clearing more than GUI I stick to this

[speed-of-heat]

it was a straight cut and paste from my reg file

 

Edited May 2, 2022 by speed-of-heat

[zildac]

1 hour ago, markturner1960 said:

when I try that, I get an error saying its not a registry script?

Make sure you have this line at the top (as per @speed-of-heatpost)

Windows Registry Editor Version 5.00

[horstweihrauch]

On 3/17/2022 at 10:33 AM, nikoel said:

 

Thank you so much for this foolproof guide. I hesitated for a long time to try it because I was annoyed with all the VR related stuff and swtiched back to TrackIR...
The comparison to SteamVR is really huge. Suddenly the fonts and textures are almost as sharp as on a screen and it feels definitely much smoother and I haven't even played with the toolkit settings THANK YOU

(System: AMD Ryzen 5 5600x, Radeon 6800XT; DCS Steam Edition)

One question: is it possible to run the VR necksafer with openxr? It won't start now.Necksaver not possible, as mentioned it starting post.

Edited May 2, 2022 by horstweihrauch

[johnbowzer]

7 hours ago, TED said:

Error 2 is a runtime error. I was getting this when I installed again for a while and not 100% sure how I fixed it.

Try uninstalling and reinstalling the toolkit and make sure your openxr for Windows is latest version from the ms store. 

The other possibility is one of the 3 files is corrupt. Check the bin folder see if the compiler is duplicated. Failing that remove the 3 files from bin and download them from new. I think someone provided a Dropbox link earlier. Then drop them in your bin folder again. 

@TED, what are "the 3 files" that you are referring to?

[scorch71]

28 minutes ago, johnbowzer said:

@TED, what are "the 3 files" that you are referring to?

Thanks Ted got it sorted 

John, not sure if these are the files that Ted is referring too, but It makes since that they are because this is what fix my problem.

I did not install the 3 files (two dll and one ini file) 

from OCXR_WMR_ACC into the DCS bin folder

this fix my problem, FYI I believe the OBS pugin folder in the zip for MS2020

Edited May 2, 2022 by scorch71

[johnbowzer]

I thought I was/am missing something, posts were getting confusing, but now I think that for the last several days there have been install and troubleshooting suggestions that are mixing the old and new ways to get OPENXR working with DCS. 

Unless I got it wrong, this is the evolution?

The initial "per-application" method as per @nikoel was  - short version - clean DCS, then replacing DCS's <openvr_api.dll> and <D3DCompiler_47.dll> and adding the <opencomposite.ini>. And this may still work.

The new "system-wide" method as per updated post 1 using the opencomposite.exe. And this method requires no files to be put in DCS's bin folder, other than an <opencomposite.ini> should you want/need to use one. So the DCS version of </bin/openvr_api.dll> is not touched, and the DCS </bin/D3DCompiler_47.dll> is deleted or renamed so the windows version gets used (which is basically what was being used for the per-application method).

I did everything as per new post 1 for system-wide install, and DCS ran in VR with G2, so it must be using OpenXR. Re-enabled OpenXR Toolkit 1.1 and it is OK.

Just wanting to ensure that I got it right and am not leaving features off the table.

[speed-of-heat]

23 minutes ago, johnbowzer said:

I thought I was/am missing something, posts were getting confusing, but now I think that for the last several days there have been install and troubleshooting suggestions that are mixing the old and new ways to get OPENXR working with DCS. 

Unless I got it wrong, this is the evolution?

The initial "per-application" method as per @nikoel was  - short version - clean DCS, then replacing DCS's <openvr_api.dll> and <D3DCompiler_47.dll> and adding the <opencomposite.ini>. And this may still work.

The new "system-wide" method as per updated post 1 using the opencomposite.exe. And this method requires no files to be put in DCS's bin folder, other than an <opencomposite.ini> should you want/need to use one. So the DCS version of </bin/openvr_api.dll> is not touched, and the DCS </bin/D3DCompiler_47.dll> is deleted or renamed so the windows version gets used (which is basically what was being used for the per-application method).

I did everything as per new post 1 for system-wide install, and DCS ran in VR with G2, so it must be using OpenXR. Re-enabled OpenXR Toolkit 1.1 and it is OK.

Just wanting to ensure that I got it right and am not leaving features off the table.

Yep, you can also copy the new d3dcompiler_47.dll into the directory with the 2nd approach, which I do mostly so I can manage it with a mod manager.

[Gravy Jones]

Man, I must be missing something.   Got this to work, but the performance sucks.   I had much smoother performance using Steam VR with Kegetys VR shaders, 100% resolution and no reprojection.  This is a stuttery mess.  And I’m running a stout pc (3090, 5900x, etc).  What am i missing.  Unless there is something obvious, I’m going back to Steam VR.  
 

Edit:    Never mind.  Switched the G2 to 60hz, now it’s all good.   Now I see what all the hype is about.   Colors are definitely better. As is frame smoothness.  Was able to turn a few things up.   Definitely more performant than Steam VR. 

Edited May 3, 2022 by Gravy Jones

[nikoel]

4 hours ago, johnbowzer said:

I thought I was/am missing something, posts were getting confusing, but now I think that for the last several days there have been install and troubleshooting suggestions that are mixing the old and new ways to get OPENXR working with DCS. 

Unless I got it wrong, this is the evolution?

The initial "per-application" method as per @nikoel was  - short version - clean DCS, then replacing DCS's <openvr_api.dll> and <D3DCompiler_47.dll> and adding the <opencomposite.ini>. And this may still work.

The new "system-wide" method as per updated post 1 using the opencomposite.exe. And this method requires no files to be put in DCS's bin folder, other than an <opencomposite.ini> should you want/need to use one. So the DCS version of </bin/openvr_api.dll> is not touched, and the DCS </bin/D3DCompiler_47.dll> is deleted or renamed so the windows version gets used (which is basically what was being used for the per-application method).

I did everything as per new post 1 for system-wide install, and DCS ran in VR with G2, so it must be using OpenXR. Re-enabled OpenXR Toolkit 1.1 and it is OK.

Just wanting to ensure that I got it right and am not leaving features off the table.

This is the way

i don’t try to correct the ‘drag and drop’ per app install because it’s fully legitimate and works. I also don’t provide any commentary on it as I have not tried it - 

i chose my way because I believe it’s superior  for three reasons. It will auto update and is easier for newcomers to install and finally it’s easier to go between SteamVR and OpenXR

However both are 100% fine and should resolve in exactly the same outcome [if done correctly]

[A.F.]

vor 6 Stunden schrieb Gravy Jones:

Man, I must be missing something.   Got this to work, but the performance sucks.   I had much smoother performance using Steam VR with Kegetys VR shaders, 100% resolution and no reprojection.  This is a stuttery mess.  And I’m running a stout pc (3090, 5900x, etc).  What am i missing.  Unless there is something obvious, I’m going back to Steam VR.  
 

Edit:    Never mind.  Switched the G2 to 60hz, now it’s all good.   Now I see what all the hype is about.   Colors are definitely better. As is frame smoothness.  Was able to turn a few things up.   Definitely more performant than Steam VR. 

 

Have you ever tried to set the G2 to 60Hz when playing with Steamvr?
No wonder you have a higher performance now.
I'm not sure if setting your G2 to 60Hz is the solution to your problem.

[DeltaMike]

^It's one solution.

He probably had microstutter.  If your headset is set at 90hz, microstutter only ever goes away at 90fps and 45fps.  For people like me who are usually loping along at 50fps, most of the time each frame is displayed twice, with an occasional early frame.  If you're closer to 70hz, most frames are displayed once with frequent dropped frames. 

If the dropped frames are driving you bonkers, setting your refresh rate to 60hz solves that problem.  Another strategy could be dialing up your settings to get yourself below 60fps, or locking your frames at 45 using MR or something. 

Nothing wrong with SVR of course.  Pimax users seem to be getting great results with it.  The problem I think is with WMR4SVR, and I believe the mischief might be happening after the frame has already been rendered.  Which is why nikoel keeps banging his spoon on the table about how FPS doesn't tell the whole story here. 

About the only way to deal with WMR4SVR is frame rate locking.  Which works great in SVR but not quite as well in OXR.  For people like me, it's a close call.  SVR with MR is definitely smoother.  I just think OXR looks better and I can live with a little microstutter, long as it's down at the low end of the refresh rate range where you're getting frames early, instead of late. 

@Gravy Jones -- if you keep dialing up your settings, there's a risk of dropping below 60fps, at which point you'll start dropping frames again.  If that happens, you could go back to 90hz if you want, only downside to that is, when you snap-roll the horizon will judder.  Curious to know what the horizon looks like at 60.  Whether it does anything for cloud shimmering and stuff.  Are you doing helicopters?  Jets?  

Edited May 3, 2022 by DeltaMike