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

[TylerPL666]

If u have boottleneck (+~xx ms) USE PRERENDER FRAMES 2 in NVidia Panel. probably everyone with RTX20xx/30xx will benefit with this settings.

Edited May 20, 2022 by TylerPL666

[M1Combat]

Can you prove that?  Are you saying you gain some MS frame time by having it render frames BEFORE it will know where your head is at?  I can try later but...  seems not legit based on my understanding of that setting.

[some1]

It's not predictive. It simply increases the delay between your movement and the change on screen, so there is a small buffer which can smooth things out a bit.

It's also nothing new. Increasing the prerendered frames buffer can reduce stutter if the frametimes are fluctuating, and increase system throughput in both 2D and 3D, at the price of increased latency. Also known as input lag. And normally it's something we try to minimize, especially for VR. 

 

Edited May 20, 2022 by some1

[TylerPL666]

8 hours ago, M1Combat said:

headset goes black WMR thinks it's asleep and won't wake it back up for a while even if I close WMR

Set sleep timer to 5h + Manual switching between Desktop/hedset mode by Win+Y

[Hammer1-1]

I wouldnt recommend not using a sleep timer for your headset longer than 15-20 minutes. Some headsets will get burn-in if you let them idle for a long time, and on top of that they will shorten their lifespan.

[M1Combat]

I re-installed the older version of OXR and that seems to work...  I'm thinking that means I need to manually pop the newer d3d file in the bin folder...

9 hours ago, some1 said:

It's not predictive. It simply increases the delay between your movement and the change on screen, so there is a small buffer which can smooth things out a bit.

It's also nothing new. Increasing the prerendered frames buffer can reduce stutter if the frametimes are fluctuating, and increase system throughput in both 2D and 3D, at the price of increased latency. Also known as input lag. And normally it's something we try to minimize, especially for VR. 

 

 

I'll check it out.  You're basically implying that we can live with a touch of input lag and it buys us some smoothness yeah?

 

[speed-of-heat]

Hi I think he was saying you will get input lag, and you really don't want it.

[TylerPL666]

New version 1.1.2:

[KevyKevTPA]

On 5/19/2022 at 6:03 AM, A.F. said:

Try this:

Re-calibrate your headset by clearing the environment and then realigning via Mixed Reality Portal, SEATED, and with the headset in the exact same position and with the exact same posture and direction you intend to fly in

I didn't think that would work as I had just done that a few days before trying the OpenXR toolkit and having the zoom problem, but somehow....

IT DID!!!

Thanks so very much!

Kev

[KevyKevTPA]

On 5/19/2022 at 7:10 AM, nikoel said:

I'm just going to leave this here for anyone who went through the DCS Update

I'm curious what deleting/renaming that file does for us?

[Baldrick33]

2 hours ago, KevyKevTPA said:

I'm curious what deleting/renaming that file does for us?

The file gets replaced with a DCS update to one which is not compatible with the OpenXR mod. Deleting or renaming it forces Windows to use a compatible version which it finds in the Windows\System32 folder or similar.

The alternative is to keep a backup and replace it in the DCS\bin folder. It has the same result.

[horstweihrauch]

Necksafer for openxr when?

[Sr.]

6 hours ago, horstweihrauch said:

Necksafer for openxr when?

I miss it too but, I think that's more of a question for the Neck Safer guy.

[nikoel]

The good news is that it's a matter of 'when' rather than 'if' - the developer has said that he is happy with where the Steam version is at and is actively looking at an OpenXR version 

[kaltokri]

Can someone tell me the details of their D3DCompiler_47.dll in the Windows\system32 folder, please?

Maybe the reason why OpenXR doesn't work is, that this file was changed by something.

My D3DCompiler_47.dll has a change date of 09.04.2021 and the version is 10.0.19041.868.
I've got Windows 10 (21H2) with all available updates.

There are some more files (d3dcompiler_47_32.dll & d3dcompiler_47_64.dll) in C:\Windows\system32\DriverStore\FileRepository\...\NvCamera with different dates.

[diamond26]

2 hours ago, kaltokri said:

Can someone tell me the details of their D3DCompiler_47.dll in the Windows\system32 folder, please?

Maybe the reason why OpenXR doesn't work is, that this file was changed by something.

My D3DCompiler_47.dll has a change date of 09.04.2021 and the version is 10.0.19041.868.
I've got Windows 10 (21H2) with all available updates.

There are some more files (d3dcompiler_47_32.dll & d3dcompiler_47_64.dll) in C:\Windows\system32\DriverStore\FileRepository\...\NvCamera with different dates.

null

2 hours ago, kaltokri said:

Can someone tell me the details of their D3DCompiler_47.dll in the Windows\system32 folder, please?

Maybe the reason why OpenXR doesn't work is, that this file was changed by something.

My D3DCompiler_47.dll has a change date of 09.04.2021 and the version is 10.0.19041.868.
I've got Windows 10 (21H2) with all available updates.

There are some more files (d3dcompiler_47_32.dll & d3dcompiler_47_64.dll) in C:\Windows\system32\DriverStore\FileRepository\...\NvCamera with different dates.

and I use this for OpenComposite

[M1Combat]

I was able to fix my issue by doing the manual open composite style install.

[easy_ci]

I cant get it to run in VR-mode with OpenXR since the update too. Anyone found a solution yet?

[M1Combat]

Try the post just above yours

[Harlikwin]

On 5/22/2022 at 6:23 AM, nikoel said:

The good news is that it's a matter of 'when' rather than 'if' - the developer has said that he is happy with where the Steam version is at and is actively looking at an OpenXR version 

Did ED actually say that somewhere?

IDK, I tried it and didn't get any/much FR boost it was +/- 5-10 fps for me depending on the scenario... And the sharpening was in some ways better and in other ways worse than reshade that I'm using. So its kinda of a "ease of use" thing for me. 

 

[nikoel]

On 5/24/2022 at 8:30 AM, Harlikwin said:

Did ED actually say that somewhere?

IDK, I tried it and didn't get any/much FR boost it was +/- 5-10 fps for me depending on the scenario... And the sharpening was in some ways better and in other ways worse than reshade that I'm using. So its kinda of a "ease of use" thing for me. 

 

ED do not develop the necksaver app. Its made by a dev on the Il2 Forums who was kind enough in the way he coded it that it worked with DCS as well. And yes he has actually said that

At the moment it doesn't. I see it as a feature as I am now a much better pilot for it - physical pain of having to 180' like an owl is a great motivator not to suck. However some people have physical constraints and see it as a must have app. Each to their own

[krazyj]

Im getting this error and I cant for the love of me get it to work despite following the guide, any aid would be appreciated

 

Thanks

[Baldrick33]

1 minute ago, krazyj said:

Im getting this error and I cant for the love of me get it to work despite following the guide, any aid would be appreciated

I believe you may have an incompatible opencomposite.ini file in your dcs\bin folder.

If you delete or rename it then it will use defaults

[krazyj]

6 minutes ago, Baldrick33 said:

I believe you may have an incompatible opencomposite.ini file in your dcs\bin folder.

If you delete or rename it then it will use defaults

Then I got this error 

[fastf1nger]

Anybody else is unable to start DCS in VR since the last open beta update?

It woked perfectly until yesterday, after todays update.... nothing