Nvidia Frame Generation PC setting also applied to VR - cause lower performance

Bug Reporting Hub Virtual Reality (VR)
, , ,
1

Hi, I just noticed the Frame Generation setting (PC settings tab) is also applied to VR, causing a 30fps limit in VR with my RTX4080. Usually I’ve got 40-45fps with high settings and active foveated rendering (openXR toolkit).

While Frame Generation is amazing for 3D, the setting results in a laggy experience in VR due to higher latency (30ms vs. 19ms in my case). It’s much smoother without FG enabled, with solid and more responsive 45fps.
I know, 30fps with FG should be 60fps, but It didn’t work like that in VR.

Please implement different Frame Generation settings for 3D and VR to fix the issue, or exclude Frame Generation from VR settings at all.

Frame Generation disabled:

IMG_3108
IMG_31081920×2560 248 KB

IMG_3105
IMG_31051920×2560 320 KB

Frame Generation enabled:

IMG_3109
IMG_31091920×2560 236 KB

IMG_3106
IMG_31061920×2560 336 KB

1 Like
2

this is very interesting because FG doesn’t work in VR. So something else is going on here. You have piqued my interest though and I’m going to test this here shortly when I’m done working in my Network Rack.

3

As far as I know, the MSFS developer tool doesn’t count the FG generated frames.