VR Discussions, Questions & Feedback

Could you possibly check something for me and report back? Can you setup a race with 15+ AI in GT3 AMG, at Nurburgring Veedol, midnight, starting front or mid pack (not last, you need headlights behind you) and report your frame rate into turn 1? This kills my frame rate at night , clear weather with a 11900K/3080. I mean murders it. I'm hitting 13ms here. I only have MSAA on Medium btw.

I don't have any issues running 90fps during the day with light rain. Its night time that kills me with lots of headlights directly behind me.

Personally, I don't understand how people don't notice the severe visual degradation of FSR even at 0.77 render scale. I have to ramp up my SS so much to compensate for the poor result that I end up back at square 1 in terms of frame rate. I pretty much gave up on it.

 

Maybe I'm old and my eyes are failing me, but I wouldn't call the degradation severe. The stuttering and low frame rates I get without FSR is far more immersion killing in my opinion. I only started testing FSR yesterday, so haven't played all that much with it yet, but so far it looks promising.

But I guess image quality varies a lot between the different headsets. My Reverb G2 renders around 3000x3000 pixels @ 100% SS, which I think is quite a bit more than the Vie Pro?

 

I've downloaded the OpenVR-FSR_1.1 file but, being a technoidiot, am not sure where I need to put the openvr_api.dll.

AMS2 is on my steam account and looking in Steam/SteamApps/Common/Automobilsta2 I see a steam_api.dll file - should the openvr_api.dll go in there?

 

find a folder called x64

 

As said in the post above there is an 'x64' subfolder under the 'Automobilista 2' folder.
There is already an 'openvr_api.dll' file there, rename that so you can go back if you don't like FSR.
Copy the new 'openvr_api.dll' and the 'openvr_mod-cfg' files into the 'x64' folder.

 

At the end of the day, I find just reducing SteamVR SS basically gets me the same results and image quality as cocking around with this FSR.

 

That was my initial experience too. Two things to try - reduce radius to 0.4, you can try turning on debugging to make this radius temporarily visible - on the Index at least 0.4 covers more than enough for me. And check how much sharpening you have applied in the AMS2 graphics config. None is not good. Too much is not good. I settled on 0.4. Will try your test later and report back.

 

Yup - this knackered my frame rate too. Even reduced Steam SS to 170 and framerate was still over 13ms at the start - fluctuated between 10 and 13 ms for the first lap . Not ideal but was driveable - I have motion smoothing off and the frame rate variation was noticeable but not too jarring. I appreciate others might find this more annoying than I do - I think I've learned to live with settings that are the best compromise for the moment. I do believe FSR helps though and is worth some experimenting with

 

I just tested fsr. I played with steam SS untill I found a setting where I have similar performance and then I switched back between settings. I notice a significant increase in sharpness using fsr with increased super sampling. I use 0.77 / 0.4 settings as suggested

Without fsr I have a resolution of 2500*2500 (I really wish everyone stops telling how much SS they apply and simply state resolution per eye!)

With fsr I bumped the resolution to 3000*3000 giving similar performance. It's very noticeably sharper. Much less aliasing and shimmer.

I use MSAA MED. This gives me 90fps at daytime against 29 AI

I was quite sceptical, but fsr really helps improve image quality

 

Does what you are all talking about regarding fsr etc apply to oculus rift s? Don’t laugh cos I’m not tech savvy

Thanks

 

It's irregardless of VR headset or GPU. It's basically a fancy upscaling tool that renders below the set resolution and upscales it back to the set resolution.

 

Non tech savvy answer - Yes!

 

Wow!!! Although I am super happy for you, I am simultaneously jealous: With my RTX 3080 I can't get anywhere close to this. I realize that 190 SS on the Index is different than the Reverb G2, but even if I reduced SS to 150% and kept the 0.77 render scale, and even dropped radius to .3, I would be no where near 90 FPS even in clear/dry with those same graphics settings. Maybe this is solely a Time Trial problem thing, so I will see how performance is impacted across different game modes. I've solely been testing within Time Trial, but I'll have to test other game modes as well.

Anyone have tips for getting rid of the shimmer using FSR? I have my non-FSR settings @ 45FPS nailed down perfectly, but using FSR in hopes of achieving 90 FPS, I can't seem to find something that runs smoothly and doesn't shimmer a lot in the middle of the picture, especially in the mid to far distance.

 

People should really stop mentioning steam SS value and instead report resolution per eye. This only causes confusion when people have different headsets.

 

@Chip I think the shimmering your talking about is coming from the sharpness.. Try turning it down a little

 

I was playing AMS2 on my Quest 2 with a Ryzen 2600 and 1060 GPU, and it had acceptable framerate and was playable.
Today I upgraded my CPU to a Ryzen 5600x, and all of a sudden in VR AMS2 is very very choppy and unplayable. I tried other games, and their performance is much better than when I was on a Ryzen 2600, so I'm puzzled as to why AMS2's VR performance dropped. I'm using a wired connection and not air link.

I also noticed that when I recenter the VR view, I am slightly behind the driver, so I can see the hole where his neck is supposed to be.

Has anyone experienced this?

EDIT: I just realized this choppiness is only in Oculus VR model I tried it on SteamVR and it runs smooth. I thought Oculus VR should have less overhead.

 

Have you tried adjusting your seat position forward or up a bit?

Ive had this problem a few times and thought it was a bug, until I mapped some buttons to adjust my seat position.

 

@Shodan0000
Without fsr I have a resolution of 2500*2500 (I really wish everyone stops telling how much SS they apply and simply state resolution per eye!)

With fsr I bumped the resolution to 3000*3000 giving similar performance. It's very noticeably sharper. Much less aliasing and shimmer.

What are your Hardware specs?

 

I have exactly the same experience! 5800x 6900xt

Thanks for stating the resolution, but sorry for sounding pushy.

 

We all have our own little bugbears. Makes more sense to me to refer to the SS% though - as long as we know the HMD we can work out the size of the image being rendered if that interested us. When I think about SS I think in percentages - not resolutions.