FSR 2.1 in elite
- Thread starter Benji85
- Start date
07Oops, I accidently replied on reddit. copy, alt-tab, paste:
VRPerfkit and OpenVR_FSR are indeed old -- they predate Frontier's adding FSR to the game -- do you have any credible sources to confirm this is indeed FSR 2.1 and not FSR 1?
(Anything above FSR 1 requires motion vector data from the game.)
VRPerfkit and OpenVR_FSR are indeed old -- they predate Frontier's adding FSR to the game -- do you have any credible sources to confirm this is indeed FSR 2.1 and not FSR 1?
(Anything above FSR 1 requires motion vector data from the game.)
Depends on what headset you are using.
The game itself does not support OpenXR, but there are wrappers that redirect OpenVR (SteamVR) calls to OpenXR instead, which can bypass SteamVR as a middle man, if your headset is more "native" to a different OpenXR compliant VR runtime than Valve's.
I use a Valve Index, so I'm already "close to the metal" so to speak. :7
I have not kept up, but latest I knew of, what you are looking for is: https://github.com/aashishvasu/OpenComposite
That will do the redirecting I mentioned. From that point, you can choose whichever OpenXR compliant runtime you want to use; And additionally maybe stick OpenXRToolkit (EDIT: https://mbucchia.github.io/OpenXR-Toolkit/ ) between the game and the runtime, in order to try to force some degree of foveated rendering, or other manipulation.
If you stay with OpenVR, have a VariableRateShading-capable graphics card (RTX20x0 and up), and wish to try foveation, check back at fholgers github page where you got openvr_fsr, and give VRPerfkit a try, as an option -- it will allow you to render less detail in the periphery (radius of full detail configurable), for a percent or two of workload relief...
The game itself does not support OpenXR, but there are wrappers that redirect OpenVR (SteamVR) calls to OpenXR instead, which can bypass SteamVR as a middle man, if your headset is more "native" to a different OpenXR compliant VR runtime than Valve's.
I use a Valve Index, so I'm already "close to the metal" so to speak. :7
I have not kept up, but latest I knew of, what you are looking for is: https://github.com/aashishvasu/OpenComposite
That will do the redirecting I mentioned. From that point, you can choose whichever OpenXR compliant runtime you want to use; And additionally maybe stick OpenXRToolkit (EDIT: https://mbucchia.github.io/OpenXR-Toolkit/ ) between the game and the runtime, in order to try to force some degree of foveated rendering, or other manipulation.
If you stay with OpenVR, have a VariableRateShading-capable graphics card (RTX20x0 and up), and wish to try foveation, check back at fholgers github page where you got openvr_fsr, and give VRPerfkit a try, as an option -- it will allow you to render less detail in the periphery (radius of full detail configurable), for a percent or two of workload relief...
Keep your eyes open for another Pimax Crystal user on this forum (can't recall their nick, unfortunately), who has a number of times made claims about a level of quality and performance (without reprojection or other tricks), on his current setup, which I am seriously doubtful about to be frank -- maybe if he really has some magic spinning, he could share it with you, and maybe then you could be his corroborator. :7
Mbuccia who wrote OpenXR-Toolkit (which I linked to above) also made a Pimax-native implementation of the OpenXR API, which you could use with OpenComposite -- it may even since have become included in Pimax's newer software, but do not know - I'm a bit out of touch. :7
Mbuccia who wrote OpenXR-Toolkit (which I linked to above) also made a Pimax-native implementation of the OpenXR API, which you could use with OpenComposite -- it may even since have become included in Pimax's newer software, but do not know - I'm a bit out of touch. :7