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

[USA_Recon]

On 5/9/2022 at 8:47 AM, streakeagle said:

Great news! I wish the people at nVidia and AMD would recognize DCS as a platform that needs to be properly supported.

I wish the people at ED would make DCS VR a top goal

[Wali763]

I got two questions, since I want to find out if this is related to my AMD-GPU.

When I turn on MR, I get a "waterdrop-effect" in my G2, also quite noticable in the cockpit. But I also have this in SteamVR with turned on MR (WMR4SVR), especially looking at menus, text or the likes and moving my head ever so slightly. Also in SteamVR Home. In cockpit, its not noticable. If I turn MR off in WMR4SVR then there ist no such waterdrop-effect".

So actually my "waterdrop"-problem seem more linked to MR than to OpenXR

Do also Nvidia-Users have the same problem or are there AMD-users, that dont have this problem?

Second question:

When I turn on MR in OpenXR I immediatly get a hefty fps-drop. Where I had 50+fps before, I then have 27-30fps with the same settings as before. Anyone knows the reason for this?

Overall IMO OpenXR is far superior to SteamVR in DCS. With STeamVR I was mostly still using 2D, but with OpenXR I for sure am more time on VR vs 2D.

Thx.

[edmuss]

I've not experienced the water drop effect in SVR but it's quite apparent in openxr, hopefully it will be improved upon.  It's the same for nvidia as well as AMD.  I run without reprojection and sit at 60-80fps, it ghosts a little in certain scenarios but generally it's plenty smooth enough, I'm flying low and slow though so that might make it less obvious.

The hefty drop is to do with the overheads needed to make the reprojection work.  Using the openxr dev tools performance overlay you can see app_GPU and post_GPU, these are the time for the VR render and the time for the overheads respectively.  Basically add the two together and that should dictate which refresh rate fraction bracket you're sitting in.

20ms app_GPU + 5ms post_GPU = 25ms (40fps) which means you've missed the 45Hz bracket (half of refresh rate) and it's dropped down to the next bracket which is third refresh rate (30Hz); this is why you appear to have suddenly lost a whole bunch of FPS.

There also needs to be considered is that the refresh rate brackets get progressively smaller each time (specifically 45/15/7.5 Hz gap between brackets) so the reprojection overhead eats up a much larger proportion of the available bracket.  I see the 30Hz bracket as a bailout and you should ideally tune to keep in the 45Hz bracket for the majority of the time.

[Svsmokey]

As i understand it , Amd 6000 gpu drivers are not yet optimised for motion reprojection . I use motion smoothing in Svr instead , and this is one of the reasons i have not yet installed OpenXR .

I'm also one of the lucky ones who don't see the 60 hz flicker , so the only time motion smoothing kicks in is on airfields/supercarrier .

4 hours ago, Wali763 said:

I got two questions, since I want to find out if this is related to my AMD-GPU.

When I turn on MR, I get a "waterdrop-effect" in my G2, also quite noticable in the cockpit. But I also have this in SteamVR with turned on MR (WMR4SVR), especially looking at menus, text or the likes and moving my head ever so slightly. Also in SteamVR Home. In cockpit, its not noticable. If I turn MR off in WMR4SVR then there ist no such waterdrop-effect".

So actually my "waterdrop"-problem seem more linked to MR than to OpenXR

Do also Nvidia-Users have the same problem or are there AMD-users, that dont have this problem?

Second question:

When I turn on MR in OpenXR I immediatly get a hefty fps-drop. Where I had 50+fps before, I then have 27-30fps with the same settings as before. Anyone knows the reason for this?

Overall IMO OpenXR is far superior to SteamVR in DCS. With STeamVR I was mostly still using 2D, but with OpenXR I for sure am more time on VR vs 2D.

Thx.

 

[Wali763]

6 hours ago, edmuss said:

I've not experienced the water drop effect in SVR but it's quite apparent in openxr, hopefully it will be improved upon.  It's the same for nvidia as well as AMD.  I run without reprojection and sit at 60-80fps, it ghosts a little in certain scenarios but generally it's plenty smooth enough, I'm flying low and slow though so that might make it less obvious.

The hefty drop is to do with the overheads needed to make the reprojection work.  Using the openxr dev tools performance overlay you can see app_GPU and post_GPU, these are the time for the VR render and the time for the overheads respectively.  Basically add the two together and that should dictate which refresh rate fraction bracket you're sitting in.

20ms app_GPU + 5ms post_GPU = 25ms (40fps) which means you've missed the 45Hz bracket (half of refresh rate) and it's dropped down to the next bracket which is third refresh rate (30Hz); this is why you appear to have suddenly lost a whole bunch of FPS.

There also needs to be considered is that the refresh rate brackets get progressively smaller each time (specifically 45/15/7.5 Hz gap between brackets) so the reprojection overhead eats up a much larger proportion of the available bracket.  I see the 30Hz bracket as a bailout and you should ideally tune to keep in the 45Hz bracket for the majority of the time.

Thx for the help with app_ and post_GPU. I read this (your) advices a few pages back already and it helped to optimize my settings, but there is still a big fps-gap between MR on and off. But since I cant/dont use it anyway, thats ok.

And considering Svsmokey`s comment about AMDs drivers not being optimized, I guess this really should be an AMD-thing. From what Ive heard, AMD is working hard to optimize their drivers for the upcoming RDNA3-generation, which also should give the older RDNA2-gen-GPUs a boost, one that I currently have. Maybe this upcoming update also resolves some of my VR-problems...

And maybe, if it holds true, that the upcoming Gen from Nvidia and AMD should have up to 120% perf gain above the 6900XT, this could also mean, that we finally could run DCS with real 90fps. But I guess, in that case we´ll use that gain to increase our videosettings, getting us back, where we are now but just with a better picture-quality....

[GPatricks]

For those using XRNeckSafer, beta 2 is out with motion smoothing Autorotation, works great!

[zildac]

2 hours ago, =LD=Icer said:

For those using XRNeckSafer, beta 2 is out with motion smoothing Autorotation, works great!

Am I right in assuming that this only works with WMR? So no joy with Varjo Aero and OpenXR (OpenComposite)?

[GPatricks]

Just now, zildac said:

Am I right in assuming that this only works with WMR? So no joy with Varjo Aero and OpenXR (OpenComposite)?

I'm told, and have seen on the Varjo Discord, that it does indeed work with the Varjo Aero and OpenXR (OpenComposite)!

[zildac]

Just now, =LD=Icer said:

I'm told, and have seen on the Varjo Discord, that it does indeed work with the Varjo Aero and OpenXR (OpenComposite)!

Thanks, must have missed that (Discord is a fire hose!) I'll go take a look

[Christopho]

Hello

Did anyone else have this issue while launching DCS with OpenComposite "Unknown config option mirrorMode on line 2"? It works fine when i switch to steamvr.

I tried to repair dcs and reinstall opencomposite aswell as the manual install of the ddl. Nothing worked thill now. I hope someone can help me.

Thank you, cheers

Edited June 21, 2022 by Christopho

[firefox121]

hace 39 minutos, Christopho dijo:

Hello

Did anyone else have this issue while launching DCS with OpenComposite "Unknown config option mirrorMode on line 2"? It works fine when i switch to steamvr.

I tried to repair dcs and reinstall opencomposite aswell as the manual install of the ddl. Nothing worked thill now. I hope someone can help me.

Thank you, cheers

 

just put a semicolon first in the second line of opencomposite ini

then if I remember well you'll se a error on line 7, make the same thing, 

I didn't try to delete the file, but think in the latest versions are no longer needed. In fact I have no longer the  file in my dcs bin folder

[Sr.]

1 hour ago, firefox121 said:

just put a semicolon first in the second line of opencomposite ini

then if I remember well you'll se a error on line 7, make the same thing, 

I didn't try to delete the file, but think in the latest versions are no longer needed. In fact I have no longer the  file in my dcs bin folder

same

[mbucchia]

I wrote a page with some explanations about what's going on with OpenComposite and also listing all the common errors I've come across. Could be helpful:

https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html

[coldViPer]

Thanks mbucchia, great stuff as always

[Ready]

9 hours ago, mbucchia said:

I wrote a page with some explanations about what's going on with OpenComposite and also listing all the common errors I've come across. Could be helpful:

https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html

Great work!  @nikoel might be nice to add this to your first posting?

[Antibak]

Late to the party here gang but glad I eventually found this and can finally now skip Steam to play this title. Thanks for the detailed procedure here.  Following it to the letter helped on some issues but for the most part, this was about the same, "FPS wise" since I already optimized my machine with Thud's VR4DCS advice ages ago.  What is improved: 1) No more flickering when loading screens and missions! 2) Faster start of the game and missions too.  3) Using the OpenXR Toolkit to enhance visuals to eliminate the Washed-out look in VR.  Everything "Pops" now! 4) Playing with some other settings PLUS  OpenXR tools can improve frames, "Marginally" if you are trying for every FPS you can get but it is not a game changer like others boast here.  (Their systems were probably messed up in the first place.)  5) So far shimmering effects seem to be drastically reduced too but minimal time thus far; not all maps yet.  What doesn't work: 1) NOT USING Motion reprojection!  I noticed a ton of comments concerning stuttering cockpits and when close to the ground; when you look sideways down at it.  Turning settings to minimums with 70+ FPS did not help.  Motion reprojection was the only option that worked for me.  (Anyone else find an alternate fix?) An internet search came up with nothing.  Thanks!       

[edmuss]

6 hours ago, Antibak said:

Motion reprojection was the only option that worked for me.  (Anyone else find an alternate fix?)

Unfortunately no, reprojection is still a bit flaky with the toolkit. Sometimes it seems to work ok and others it just spirals into a death dive and locks the framerate to 20fps.

[PLUTON]

Since the last update of OB open composite no longer works and when I configure it puts me
this window which tells me that the access path is refused, what is the problem??

Thanks for the help

null

 

[Tattiebogle]

Since the last update of OB open composite no longer works and when I configure it puts me
this window which tells me that the access path is refused, what is the problem??
Thanks for the help
null
 

You probably need to delete D3DCompiler_47.dll inside the Bin folder of your DCS Install

Sent from my SM-G950F using Tapatalk

You probably need to delete D3DCompiler_47.dll inside the Bin folder of your DCS Install

Sent from my SM-G950F using Tapatalk

Sorry I'm wrong

Sent from my SM-G950F using Tapatalk

[PLUTON]

No, I already took it off.
open composite no longer opens the window where DCS is when I press the configure button and then when I fly I run at 6 or 7 fps instead of 30 locked

[PLUTON]

I uninstalled Steamvr from my pc (since it is no longer used) it has nothing to do I think??

[slughead]

3 hours ago, PLUTON said:

Since the last update of OB open composite no longer works and when I configure it puts me
this window which tells me that the access path is refused, what is the problem??

Thanks for the help

null

 

No problems with it for me. As I don't have any mods added I just installed the update and renamed the d3dcompiler_47.dll. If you have installed any mods, I would advise doing a "clean up/repair" and then running the update. Rename the d3dcompiler_47.dll or delete it and then run DCS. If that works then add your mods. As you have already applied the update, remove any mods, run a clean up/repair and go from there.

[PLUTON]

You say delete the d3dcompiler_47.dll.
or rename it.
What is the difference between renaming it or deleting it??
If I rename it what does it bring me as an advantage?

[Tattiebogle]

You say delete the d3dcompiler_47.dll.
or rename it.
What is the difference between renaming it or deleting it??
If I rename it what does it bring me as an advantage?

Nothing. Backup if you think you might try steam vr in the future

Sent from my SM-G950F using Tapatalk

[speed-of-heat]

Just now, PLUTON said:

You say delete the d3dcompiler_47.dll.
or rename it.
What is the difference between renaming it or deleting it??
If I rename it what does it bring me as an advantage?

one or the other there is no disadvantage or advantage to one or the other ... either deleting or renaming will have the effect of the calls going to the system32 dll with the same name.

me i copy a copy of my System32\ d3dcompiler_47.dll into my Mod Manager and then use my mod manager to over right the one in DCS, because that means I just have a single process to mange for this and any other mods...