mbucchia

This is already what it does, as I described in my message. If you are locked at 45 FPS, it means you don't have enough headroom to achieve 90 FPS. Motion reprojection needs to run at a fraction of the headsets refresh rate. There is no slot between 90 FPS and 45 FPS (half).

Automatic in OpenXR Tools for WMR means "Always on in Flight Simulator 2020". It has no other meaning, and that explains why it means Disabled in DCS. Motion reprojection when set to Always on or Enabled in OpenXR Toolkit will automatically lock to the best frame rate you can achieve. Unless you can reach 90 FPS with headroom (meaning Motion Reprojection is not needed), it will select 45 FPS as long as you can do 45 FPS with headroom. If you can't do that, it will do 30. If you can't do that, it will do 22.5. If you can't do that, it will be disabled.

There seems to be some issues on certain versions of Oculus software. You can use the "legacy menu" mode that shouldn't be affected by these issues: 1) turn on OpenXR Toolkit Safe mode from the Companion app 2) start the game. Menu should work. 3) go to Menu tab and set Legacy menu to On 4) turn off Safe mode and try the game again. This seems to solve the problem for every reported case.

[deleted]

[deleted]

Horizontal offset cannot be supported without the game providing additional information about left/right view rendering. The effort required on my end to support it without this information is phenomenal. This isn't an OpenXR thing: the way FFR is implemented is 100% unrelated to OpenXR. The issue you have here is exactly the same issue that vrperfkit has. There is a thread here where all that's needed from DCS is outlined (and yes it would take them literally MINUTES to do it, while without this information it would take me WEEKS or MONTHS), however the developer has ignored this request since April: https://forum.dcs.world/topic/299598-trying-to-connect-the-individuals-that-made-the-performance-enhancement-in-vr-to-the-dcs-devs/

[deleted]

"At 22fps" I assume you mean motion reprojection. Neither OpenComposite nor the WMR Portal affect that, the motion reprojection is built into the OpenXR runtime, and the latest 112 updates did bring some improvements. That's assuming that you have OpenXR Tools for WMR and you selected Enable latest Preview.

[deleted]

[deleted]

For Pimax, which does not have native OpenXR support from the vendor itself, you need to install the unofficial OpenXR wrapper from here: https://github.com/mbucchia/Pimax-OpenXR/wiki Assuming you have OpenComposite already set up properly for DCS, this is all you should need. Edit: if you use both the G2 and 8KX on the same PC, you will need to change your active OpenXR runtime every time you switch headset. For G2, open the Mixed Reality Portal and click the "Fix it" button that will appear at the top of the window. For 8KX, open the PimaxXR Control Center app and select PimaxXR as your runtime (you will likely get some sort of error at first telling you that "MixedReality.json is not recognized", that's OK, just ignore it).

Hey! Can you follow these steps to capture a trace of the problem (start capturing, reproduce the issue in-game - I only need like a minute of data showing the problem - then save the trace and ZIP it up). https://github.com/microsoft/OpenXR-MixedReality/wiki/Troubleshooting-for-developers#capture-a-diagnostics-trace-from-the-command-line The file will be big, we can organize you sharing it with me through DM. Thanks.

Not having it at 0 will indeed make things worse.

I've been looking at improving the quality of motion reprojection with AMD cards, but it's a dead end it looks like. The video encoder block (needed to compute motion vectors, an essential component of motion reprojection) on AMD cards is just far inferior to the competition. On 5000 series, it does not support 16x16 optimal block sizes (which requires us to downsample the input), creating a big loss of quality leading to "warping effects". On 6000 series, I have measured it to be 3 times slower than on Nvidia RTX cards, barely able to drive 90 Hz reprojection, causing added latency contributing to the "water effect". I've been looking for alternatives to accelerate and improve the motion estimation and even asked AMD developers on the AMF project (their video SDK). They told me what I need is just not supported. I've mostly run out of things to try for AMD. Nvidia on the other end, has delivered great innovation through their NVENC and NVOF...

Check out the top post here: https://forums.flightsimulator.com/t/reminder-this-is-how-wmr-openxr-updates-work/539112 This should help a bit.

There is a bug in OpenXR Toolkit that makes anti-shake interfere with motion reprojection. Hoping to fix that eventually.

**The ZIP file contains samples for developers and nothing else.** You do not need to download anything from that website. You get updates from the Microsoft Store. Good to hear that yesterday's update resolved your problems.

The latest OpenComposite build broke a few things on the controllers side. Revert to that older version instead: https://ci.appveyor.com/project/ZNix/openovr/builds/44353680/job/ab9sh3fntl2pn57v/artifacts

Hmm interesting. My bad I should've asked you to write down all your settings before returning to default...

This option was removed a few versions ago, it wasn't doing anything since Feb 2022

Thanks. I know you said you tried disabling FFR and FSR, but there must be another setting interfering then. Safe mode disables reading all settings, which means no features are enabled. Most features don't need a restart (except for upscaling, which you have already tested with and without). I would suggest next to try resetting all to default (via restore defaults menu option or ctrl+f1+f2+f3), then re-enable all settings while looking for the issue to appear.

Thanks. Any chance you could try enabling OpenXR Toolkit Safe Mode?

Take a look at your registry at "HKLM\Software\Khronos\OpenXR\1\ApiLayers\Implicit". Make sure there is no stale (uninstalled) API layer referenced there. Also, it is important that all your API layers are installed somewhere in a system folder like "C:\Program Files". Otherwise you will get this error.

A couple of hours is ridiculous. Are you sure they weren't developers using Unity or Unreal Engine? In which case it's a fairly simple migration clicking a couple of buttons. For a custom engine, it's work quantified in weeks at least, and will highly depend on how experienced the developers are.

AFAIK there is just no support for OBS with OpenComposite.