After getting a tip somewhere on this forum, that I can’t find now, I’ve been getting great performance with the quest.
In brief, the basic idea is to throttle the GPU main frame rate to an even fraction of the headset framerate.
So for my setup, I set Oculus framerate to 80Hz:
And limit max frame rate in the NVIDIA control panel to 40:
Other combinations probably work depending on your hardware. ( My specs are: 3080, i7 10700K)
I tried every tip I could find, and this was the only one that really worked. My GPU went from maxed out to around 50% utilization, which allowed me to put most in game setting to ultra with smooth performance and no stutters at all.
I think what’s going on is that the GPU is not busy generating frames that can’t be rendered to the headset anyway because they are out of sync with the refresh. Also measuring the FPS shows it sits at 40Hz consistently - which gives a very smooth sensation visually.
Don’t know your hardware arrangement, but if you have a usb3.1 Gen2 powered hub (pricey $40 and using 12v plug), I would try it between motherboard and Quest 2. They help high frequency data signal on USB3.x where some motherboards seem to unable supplying enough power and signal fidelity.
In the transfer of data, high frequencies require higher power consumption, in the Whole chain of transfer.
Dear, there is something I don’t understand, you have a better CPU and GPU than what I have, i9-9900K and RTX3070, and I have set it to 90Hz and maximum rendering 1.5 in msfs2020 the general render to 90 and with the FOV at 0. I don’t know what other settings you have, but I think with that card you should run 90Hz without problems. Regarding the data speed, I use usbA 3.1 and the speed is 2.7Gb/s.
On the other hand, I only use the Oculus Debug Tool and I don’t use OTT since it complicated me more than it helped me.
What is meant by this? 1/1, 1/2, 1/4 (et cetera) of the headset frame rate? Or is 1/3 of the headset frame rate okay as well?
Also, I don’t understand the logic behind why this should work. When throttling the frame rate, is the extra performance that is saved used to compute frames ahead (or doing some other task)?
The idea is that the GPU is not generating frames that do not end up in the headset because they are out of sync with the headset. For example if the headset is running at 90 frames per second and the GPU is producing 46 frames per second, then every second a frame will be dropped. In reality the GPU framerate is variable - so the framerate could bounce around all over the place, resulting in random frames being dropped.
By limiting the framerate to a bit below what you are getting on average, it frees up GPU resources to turn up the settings in the sim. Before I did this I had most things on medium. After making this change I can put everything to ultra and it’s still smooth.
Yes 1/3 should work, it means there will be a new frame drawn to the headset every 3rd refresh that the headset does. Any fraction that is 1 over a whole number should in theory work.
I was getting around 44 to 46 fps, so I set the headset to 80 and max framerate in nvidia control panel to 40. If you are getting at least 37, you could set the headset at 72 and nvidia to 36, or headset at 90 and nvidia at 30.
Thanks for the explanation! So, just to be clear, if I for example set my headset to 90 Hz, every rendered frame above 45 fps will be a waste (unless it goes up to 90 fps, which basically never will happen)? Meaning there’s no reason why I never would want to throttle the frame rate to 45 fps, meaning that even if I get 50-60 fps in some cases, this will look like 45 fps to me anyway?
In my experience I didn’t see any difference in quality from 72Hz vs above freq. So I take mine on 72hz and blocked the fps to 36 fps (1/2 of 72hz). But in busy scene I prefere add ASW=30, and this option block my fps to 24 (1/3 of 72Hz). I can do this change while flying thanks to my tool bar, without leave my VR.
My spec= 3070 Ti, I7-10700
I’m on the latest version. I find I have to turn ASW to auto as well to stop the stutters. I tried all other possibilities with ASW, but everything gives me stutters except auto.
My problem might be Windows 11 related. I tried toggling the Oculus console window to give that focus as suggested on a reddit thread, but that did not appear to have any effect. Forcing ASW on (45 fps) gave the best results, but still left a lot of hiccupping. I also tested out Virtual Desktop (which defaults to 90Hz) but saw similar results.
Yes, the inability to get a “locked in” framerate and smooth ASW even with the console window trick seems to be a Windows 11 problem for Oculus Quest 2. Hope the Devs hurry up! Even if I try to help with RivaTuner or NVCPL frme capping, it just won’t stay fixed.
