Just to let you know you can automate this process using simply a batch file to launch before turning the sim in VR.
The OculusDebugToolCLI.exe program in the same directory than the OculusDebugTool.exe allow you to send command through a txt file as parameters.
E.g. I have a batch file called “MSFS 45fps 170SS.bat”, but the name don’t matter, for locking ASW at 45 and Pixel Density to 1.7.
So I have first a txt file called “MSFS45.txt” with this inside:
server:asw.Clock45
service set-pixels-per-display-pixel-override 1.70
service set-client-fov-tan-angle-multiplier 1.0 1.0
exit
And the batch file in the same directory than the parameters file above with this inside:
“D:\Oculus\Support\oculus-diagnostics\OculusDebugToolCLI.exe” -f MSFS45.txt
pause
The pause is just their as I will see what happen, you can remove it safely so the batch will close immediately. To be sure it worked, just launch your oculusDebugTool and you’ll see the applied parameters. With this method no need to keep oculusDebugTool opened.
You can also run directly OculusDebugToolCLI and type help to see all available commands (a bunch).