I hope I am doing something in the wrong order or that my understanding of the outcome is incorrect. I have tried using the OculusDebugToolCLI.exe, the OculusDebugTool.exe and the OTT to force my system to have a maximum frame rate of 40FPS/Hz with no ASW.
I set it, then I launch Oculus Desktop, then I get the Quest 2 on and start Microsoft FS2020. I then “Alt-Tab” to the OculusDebugTool.exe and set the HUD to Performance and straight away it is running at 80.
Now when I switch to VR mode it stays at 80hz until the plane is on the tarmac when as expected the Framerate drops. Then as I take off the Framerate fluctuates slightly below 40FPS then on take off it rises up above 50FPS. As it fluctuates above 40 I get microstutters but at 40 its nice and smooth.
My set up is using the Oculus OpenXR runtime and is launched from the Oculus desktop. The MSFS2020 itself was purchased via Steam.
Is my understanding wrong of how this should work or is there a route to getting the FPS fixed?
Did you try to hit CTRL+Numpad 2 as a test, when you are inside a VR session?
For me it’s 45FPS ASW OFF obviously (Rift CV1), and those shortcut work fine, I can see it immediately when monitoring fps. It should be 40fps ASW OFF for you AFAIK.
For the record (for my CV1):
CTRL+KP1 - Disable ASW and USE ATW
CTRL+KP2 - Force apps to 45hz, DISABLE ASW
CTRL+KP3 - Force apps to 45hz, ENABLE ASW
CTRL+KP4 - Enable ASW to operate automatically
I see… And what’s the problem with OculusDebugToolCli or OculusDebutTool? If you run the sim in windowed mode (it’s what I do when I want to fly in VR), you’ll be able to ALT-TAB to the pre-opened oculusDebugTool.exe, right before switching the Sim in VR, and force the ASW setting to “40 fps ASW OFF”?
I usually use a batch file with oculusDebugToolCli but when I want to fine tune my VR session (like 90% of the time at its current state, 10% remaining for testing/flying, then it’s time to sleep) I use OculusDebugTool instead like I described…
Edit : I knew I red something about your keyboard issue and lack of numpad, here a workaround from a reddit post:
Go to start menu and open the onscreen keyboard
Click the ‘options’ key on the lower right
Check the box for ‘Enable numeric keypad’
Hold Lctrl on your physical keyboard and click the numberpad key
I have managed to control it using Oculus tray tool. The important part for me was don’t start the tray tool until your sat in the cockpit of plane, then it works. I guess this makes sense when thinking about the numpad keys as these are active while your playing.
I was not so lucky when trying with the debug tool, tried the same order but it did not like it.
I have had about all I can take for now testing happy with the result but will come back and try this in a bit more detail later but for now it works and is doing what I hoped it would which is prevent half of the judders in VR. By fixing to 40hz it only judders when my graphics card can’t reach 40. Before it would also judder as it fluctuates from 40 up to 80, so now it’s only the few times when I can’t reach 40 - happy days.
Great! Now you have to experiment with renderscale and Pixel Density to find a good balance between fps and crisp image. Lowering renderscale keeping TAA ON will give you more fps and lower stutter, and then raising Pixel Density will restore and even enhance the crisp. With my machine (i7 10700K RTX3070 Oculus CV1) I have (I had post last World Update, didn’t really try after that) 45fps locked ASW OFF, and crisp image with TAA ON Renderscale 70% and Pixel Density in OculusDebugTool at 1.7, and I still have even some GPU headroom.
happy with the result but will come back and try this in a bit more detail later but for now it works and is doing what I hoped it would which is prevent half of the judders in VR. By fixing to 40hz it only judders when my graphics card can’t reach 40. Before it would also judder as it fluctuates from 40 up to 80, so now it’s only the few times when I can’t reach 40 - happy days.