OMG FSR for VR! Hands down FPS and AA improvement for me!
- Thread starter DJSlane
- Start date
I am not an Nvidia expert (although I had 3070 before purchasing the AMD card), but did you try to install the utility in the first post of this thread? It comes with a nifty utility that will help you set everything up, including which games you wish to use with this utility...Thanks for posting these, really helpful. Unfortunately I could not get NIS working reliablyEvery time I turned it on the launcher would start up Odyssey (in VR) and when I quit to the launcher and selected Horizons I got a crash. I also had a hard time toggling NIS on and off, it only worked through GeForce Experience. The NVIDIA control panel would not leave the option turned on.
Hopefully others can chime in, it would be great if this could improve VR framerates
And also to answer your other question: I do not how to tell that this is working other than having a significantly higher frame rate...
BTW, if you are wondering why my material quality is set to "Medium": that is the only setting where I do not lose the reticle... When set to high or ultra, I do not see the reticle and therefore it is difficult to fly to anything because you cannot see how close you are (that 6 seconds rule)...
After flailing about with the NVIDIA driver, I installed the mod linked by the OP as well as the mini launcher that lets you go straight into VR with Horizons. Definitely impressive, using your settings I was at 60-70 fps inside of stations which I had never reached previously. Outside often 90, although I was more like 60 during bounty hunting which is in asteroid fields. It looked like the CPU was holding things back, GPU frametimes were 10 ms. At any rate, definitely recommended! The only downside for me is that bounties in Horizons are way smaller than in Odyssey
![[VR] Mad Life Crisis](https://forums-cdn.zaonce.net/data/avatars/m/232/232989.jpg?1592151565){kind=avatar}
What is this?
That is impressive! Unfortunately, I am nowhere close to any station at the moment, nor am I close to any busy bounty hunting area, I'm out in the void, hunting the ELWs... So I have yet to see what impact this utility has on my in-station framerate...After flailing about with the NVIDIA driver, I installed the mod linked by the OP as well as the mini launcher that lets you go straight into VR with Horizons. Definitely impressive, using your settings I was at 60-70 fps inside of stations which I had never reached previously. Outside often 90, although I was more like 60 during bounty hunting which is in asteroid fields. It looked like the CPU was holding things back, GPU frametimes were 10 ms. At any rate, definitely recommended! The only downside for me is that bounties in Horizons are way smaller than in Odyssey
But happy to hear that it worked out for you and kudos to the OP fr bringing this to our attention!
There is an optional app you can download together with the utility that will help you set everything up... It's the second link in the OP...
I tried it with useNIS=true, renderScale=1.70 with Oculus Q2 in Odyssey, replaced the openvr_api.dll. No Steam.
In station sitting still.... and look around.
Without: I get about steady 30fps, up to 37fps.
With: I get occasionally 30 fps, mostly 37fps, and up to 45fps.
No perceived quality difference. With frame rate difference this small, I am not even sure if it actually worked. Too little to matter. I'd rather have steady 30fps instead of 30-37-45 fps.
In station sitting still.... and look around.
Without: I get about steady 30fps, up to 37fps.
With: I get occasionally 30 fps, mostly 37fps, and up to 45fps.
No perceived quality difference. With frame rate difference this small, I am not even sure if it actually worked. Too little to matter. I'd rather have steady 30fps instead of 30-37-45 fps.
My understanding is that if you use a value less than 1.0 for renderScale, then you're making the application render at a lower resolution (by the ratio of the renderScale), then upscaling to the original resolution - this is where the performance benefit comes from.
If you're using a value over 1.0 for renderScale (such as 1.70), then you're effectively just supersampling your original resolution to that scale, which will probably result in lower performance (though higher quality).
The comment in the .cfg file says, "if > 1, the game will render at its "native" resolution and afterwards the image is upscaled to higher resolution as per the given value." Since I set the Oculus device resolution to max... 1.7... so now the render resolution would be the LCD resolution, and upscaled to the max resolution...
Anyway, I changed renderScale=0.59 (1/1.7), and tried it, doesn't make a difference.
Anyway, I changed renderScale=0.59 (1/1.7), and tried it, doesn't make a difference.
It sounds as if yours isn't operating as intended, then. If you've implemented a 1.7 value and a 0.59 value, the differences between those outputs should be immediately visible.
I think this is evidenced by you mentioning that at the 1.7 value, there was no material frame rate change. Supersampling to that degree would generally result in much, much poorer frame rate.
Are you definitely placing the files in the correct location? For Steam, it would be in:
C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-odyssey-64\Openvr\win64
Like I said, not Steam... Oculus directly, so my openvr_api.dll is at c:\Users\<xxx>\AppData\local\Frontier_Development\products\elite-dangerous-odysseey-64\Openvr\win64\openvr_api.dll.
BTW, when I tested the 0.59 value, I get framerate teh same as when I used 1.7. Like you said, scaling this big, the difference should be very prominent. But it's not, so I think it's most likely not working.
BTW, when I tested the 0.59 value, I get framerate teh same as when I used 1.7. Like you said, scaling this big, the difference should be very prominent. But it's not, so I think it's most likely not working.
Ah... that's probably the issue, my apologies - I missed that very important point.
fholger's mod is stated to work only for SteamVR and DirectX11 apps - as mentioned here: https://github.com/fholger/openvr_fsr
... so that's probably why it's not working for you!
Do you know where is your bottleneck? Is it the GPU or CPU?
Well, I figured it's just a modified openvr_api.dll, which may also be loaded by Oculus version of ED... there might be a chance that it will work... if the code written is platform agnostic. Give it a shot... Might win big. Guess not!
If I have to guess, the bottleneck is most likely CPU... I have a 7900X 10-core processor, at turbo 4.2GHz. A bit old, but the MT performance is still stellar (compiles the whole arm32 Linux kernel in 62 seconds). However single core performance is just so so. And I recently got an EVGA RTX3080 Ultra. So, my rig is a bit GPU heavy. Unfortunately, ED and DCS are both MT-poor applications.
If I have to guess, the bottleneck is most likely CPU... I have a 7900X 10-core processor, at turbo 4.2GHz. A bit old, but the MT performance is still stellar (compiles the whole arm32 Linux kernel in 62 seconds). However single core performance is just so so. And I recently got an EVGA RTX3080 Ultra. So, my rig is a bit GPU heavy. Unfortunately, ED and DCS are both MT-poor applications.
Last edited:
Cheers, I shall pay more attention.
There is an app, that shows what is keeping your framerate low (fpsVR for Steam, maybe it exists for other platforms as well)... And ST performance of the CPU, unfortunately, is the culprit in some cases...
A heads-up: after today's update I had to re-install the plugin... I was wondering why my framerate went down after updating and sure enough, the plugin was not installed...
![Benjumanji [VR]](https://forums-cdn.zaonce.net/data/avatars/m/42/42439.jpg?1626566342){kind=avatar}
I gave it a try. Without increasing my settings all graphics were worse (to be expected), but my FPS was the same or maybe slightly lower. Maybe because I'm on a Pimax and the target resolution is very high anyhow?