Open XR - no Fixed foveated

[7Coolhand]

I discovered that the settings for enabling Fixed foveated rendering is gone in my open XR toolkit, v1.24.

How do I get it back?

[Brzi_Joe]

Which headset? Mbucchia put it out for DCS from last XR Toolkit until DCS developer settle his multithreading update, and add some "small" changes (info which eye is currently rendered). Booth DCS developer and mbucchia (xr toolkit developer) want that foveated working in this game, so we need to wait a bit.

Ps: with older xr toolkit foveated works, but it is implemented in wrong spots. Maybe for headset with small fov is okey-ish..

[7Coolhand]

It’s a Reverb G2, rtx 3090.

The problem is that there’s no setting in the toolkit anymore to enable the foveated rendering.

[speed-of-heat]

are you looking at the in game menu, or that of the companion app, it appears in the in game menu. 

[edmuss]

It's there on mine, perhaps check all of the options for advanced options?

[Sile]

It should be there even without activating "Show Expert Settings" in "Menu" tab, but i'm not sure. Maye try activating that.

[7Coolhand]

In the game menu, I have activated Expert settings with no joy.

I will try to make a screen shot.

[mbucchia]

1 hour ago, 7Coolhand said:

In the game menu, I have activated Expert settings with no joy.

I will try to make a screen shot.

There's typically two reasons for this:

- you might have accidentally turned on "Foveated Rendering killswitch" while in safe mode. Use the "Restore defaults" option in the Menu tab and restart the game.

- some Nvidia users experienced that issue after updating Nvidia drivers. The driver stopped advertising the capability. They had to do a full driver reinstall to get it back

[7Coolhand]

Startup in safe mode and reset all settings made the trick!

[D3fact0]

On 3/14/2023 at 4:41 PM, mbucchia said:

There's typically two reasons for this:

- you might have accidentally turned on "Foveated Rendering killswitch" while in safe mode. Use the "Restore defaults" option in the Menu tab and restart the game.

- some Nvidia users experienced that issue after updating Nvidia drivers. The driver stopped advertising the capability. They had to do a full driver reinstall to get it back

Hi,

I have the same problem after a I installed quadview. But I dont like a effect of visible rectangle inside headset so I uninstalled it. After that I dont see an option for Foveated rendering in openXR Toolkit. I tried reset all setting and reinstalling the Toolkit, but without succses. Other games like MSFS has FFR option visible.

Please is there any way how to make it visible again?

Thanks.

[Phantom711]

@D3fact0

Do you still have the QuadViews box ticked in the DCS options by any chance? I‘m just guessing here, that this might interfere with the FFR options in the OXRTK.

[Qcumber]

1 hour ago, D3fact0 said:

Hi,

I have the same problem after a I installed quadview. But I dont like a effect of visible rectangle inside headset so I uninstalled it. After that I dont see an option for Foveated rendering in openXR Toolkit. I tried reset all setting and reinstalling the Toolkit, but without succses. Other games like MSFS has FFR option visible.

Please is there any way how to make it visible again?

Thanks.

DId it OXRTK FFR work for your current system before you tried QVFR?

QVFR shouldn't have a visible rectangle if it's working properly. Do you mean that there is a harsh transition between low and high Res areas? If so you could try increasing the border size. This gives a graduated transition. Also make the centre high Res area larger then you don't really notice the periphery. 

[D3fact0]

@Phantom711 I have uninstalled Quadviews so the box is inactive and unticked now. But I am sure that it was ticked when i close DCS and then uninstall Quadviews.

@Qcumber Yes, there was a visible transition no matter how large area was set. I have a HP G2 headset with custom thin pad and FOV gasket so my eyes are very close to displays. It could be the reason? OXRTK FFR worked perfectly before.

[mbucchia]

On 12/1/2024 at 8:14 AM, D3fact0 said:

I tried reset all setting and reinstalling the Toolkit, but without succses

Many people don't do this step correctly, like forget to confirm the restore to defaults, or forget to leave safe mode. So I'd recommend to try that again.

Alternative is to delete registry entries by hand, both HKEY_LOCAL_MACHINE\Software\OpenXR_Toolkit and HKEY_CURRENT_USER\Software\OpenXR_Toolkit.

[D3fact0]

I deleted both registry entries and the OpenXR companion app shows me no VR applications. So i started DCS and still don´t see option for Foveated rendering (I tried MSFS and option is there). All settings are in default state so they were surely reseted.

This leads me to conclusion that the problem must be in DCS itself, not in OpenXR Toolkit.

Do you have any idea where in DCS files I can search for VR setting?

[mbucchia]

There are 2 conditional steps to OpenXR Toolkit showing the FR option:

- absence of the "foveated  rendering killswitch setting" which would have been reset by clearing the registry

- failure to initialize NvAPI (part of Nvidia driver) or NvAPI returning that VRS isn't supported on your card.

For the latter, I don't really know what can cause that. You said it still works in another game which is ever more confusing.

The only other time someone had this problem, this was caused by their Nvidia driver. I think they did DDU etc to cleanly reinstall it. But I think they were seeing this problem with all games, not just one.

Perhaps you replaced some DLLS in the sim and that interferes with NvAPI, so maybe a clean reinstall of the sim (making sure to delete the game folder!).

[D3fact0]

All right,

What I did:

1) uninstall DCS + hard delete all DCS related files.

2) delete OpenXR registry

3) reinstall GPU driver with DDU (I have AMD 6900XT)

4) install fresh copy of DCS

and the result is the SAME!!! I´m totaly confused.

MSFS has FR option and DCS not.

I was using DCS with FR for months till I installed QuadView  

[gonvise]

After yesterday's update, has anyone experienced that the halo generated by XR Toolkit Foveated Rendering (Fixed or eye tracking) in the percentages where the resolution changes is much more visible than before?

[mbucchia]

3 hours ago, D3fact0 said:

reinstall GPU driver with DDU (I have AMD 6900XT)

I was using DCS with FR for months till I installed QuadView

.........

No, you were not [using DCS with FR for months with your AMD 6900XT].

AMD doesn't support VRS (OpenXR Toolkit foveated rendering) with D3D11, which is what DCS uses. It never has and never will, this is a limitation of AMD drivers.

You must be confused out of your mind if you think it ever worked. Maybe you switched from Nvidia to AMD at some point?

You are seeing foveated rendering option in MSFS because you are using D3D12 in MSFS.

https://mbucchia.github.io/OpenXR-Toolkit/#supported-graphics-cards

Edited December 5, 2024 by mbucchia

[D3fact0]

2 hours ago, mbucchia said:

.........

No, you were not [using DCS with FR for months with your AMD 6900XT].

AMD doesn't support VRS (OpenXR Toolkit foveated rendering) with D3D11, which is what DCS uses. It never has and never will, this is a limitation of AMD drivers.

You must be confused out of your mind if you think it ever worked. Maybe you switched from Nvidia to AMD at some point?

You are seeing foveated rendering option in MSFS because you are using D3D12 in MSFS.

https://mbucchia.github.io/OpenXR-Toolkit/#supported-graphics-cards

Ok, this explains a lot  I could swear, that I had FR option in DCS and even better performance then now. But its true that I did not change the OXRT settings for long time and jump often between sims.
Anyway Thank you for your patient and help mbucchia.

BTW: I thought DCS use Vulcan

[speed-of-heat]

1 hour ago, D3fact0 said:

 

BTW: I thought DCS use Vulcan

Nope, not yet

[mmike87]

Along the same lines of FR with the OXRTK ... anyone have any idea why, despite having the option available sometimes FFR seems to work and sometimes it just doesn't seem to do anything? I (like many of us) am continually trying to find the magic combo of settings that work best with my 4090 and Varjo Aero. I actually prefer the three-rung, FFR of the OXRTK - especially now that the foveated rendering "box" is clearly visible since the last update (as others have reported as well).

Edit: I just figured it out. If I have a pixel density of anything other than 1.0, the OXRTK FFR shows as available, but doesn't seem to actually do anything.

 

Edited December 8, 2024 by mmike87
More info

[najafsen]

On 12/5/2024 at 5:39 PM, mbucchia said:

.........

No, you were not [using DCS with FR for months with your AMD 6900XT].

AMD doesn't support VRS (OpenXR Toolkit foveated rendering) with D3D11, which is what DCS uses. It never has and never will, this is a limitation of AMD drivers.

You must be confused out of your mind if you think it ever worked. Maybe you switched from Nvidia to AMD at some point?

You are seeing foveated rendering option in MSFS because you are using D3D12 in MSFS.

https://mbucchia.github.io/OpenXR-Toolkit/#supported-graphics-cards

I have RX7900 GRE and I had it working. I never had any other graphics card. I set open xr foveated setting so drastic that only small portion of the screen was high quality (very high quality) and the rest was very low quality. This way I got high frame rate and very high quality center of view. But downside was sudden transition from very high quality view to very blurry view. This transition was so visible that no one can tell me I had never had it working. Now all are gone and I can't bring it back. I don't know if DCS update, Steam VR update or AMD graphic card update caused this. My headset is Pico 3.

[mbucchia]

2 hours ago, najafsen said:

I have RX7900 GRE and I had it working. I never had any other graphics card. I set open xr foveated setting so drastic that only small portion of the screen was high quality (very high quality) and the rest was very low quality. This way I got high frame rate and very high quality center of view. But downside was sudden transition from very high quality view to very blurry view. This transition was so visible that no one can tell me I had never had it working. Now all are gone and I can't bring it back. I don't know if DCS update, Steam VR update or AMD graphic card update caused this. My headset is Pico 3.

There is no support for OpenXR Toolkit foveated rendering on DX11 with AMD GPUs. It simply does not exist.

I literally wrote the OpenXR Toolkit program and I know how it works.

To use VRS on D3D11, you must use the NVAPI library (also known as NVidia VRWorks), here is the code in OpenXR Toolkit doing that:

https://github.com/mbucchia/OpenXR-Toolkit/blob/6b9ecb69a4b2dc714b14a86407868af315d02531/XR_APILAYER_MBUCCHIA_toolkit/vrs.cpp#L1171

As the name indicate, NVAPI or NVidia VRWorks is exclusive to NVidia and does not work on AMD.

https://developer.nvidia.com/vrworks

> Variable Rate Shading (VRS) is an easy to implement rendering technique enabled by Turing GPUs.

Turing = NVidia.

I'm not going to have another back and forth on this. Previous user ultimately realized that they were not speaking of DCS, but instead they had used the feature in another game, a DX12 game, with their AMD card. You're probably in the game boat.

Or you are thinking of ",Quad views foveated rendering" which is nothing to do with OpenXR Toolkit, and is a completely different feature (that does work on AMD with DX11).

Edited April 26 by mbucchia

[SN68]

Hi all,

Ive been told that  OpenXR is not longer needed with the Quest Pro. Is that correct ?