I’ve been away for awhile from flight  and I thought I’d boot up 24 again. Even with Settings down on medium or low, I can’t fly for more than about 30 minutes without a crash very jerky and the sound is chopping all over the place.
so I returned to MSFS and with the same hardware set up it’s a solid 35 frames per second and really really really smooth is 24 just not optimised yet or is it that the quest two is just not up to the job? Any thoughts? 
 

I’ve got 24 for about another six months as it was part of a Broadband package that gave me game pass for a year where I actually own MSFS outright

 

Pico 4 user. I am not a happy MSFS2024 VR user. 😠 I'm pretty sure the main issue is VRAM exhaustion. I'm back onto MSFS2020 for VR. Smooth and steady. I'll revisit 2024 when the beta is released. It sounds promising. 

since su2 I'm happy with performance, provided I lock the meta link ASW at 30hz. The terrain is very sharp using dlss 4 and the K preset.   Locking it at 30 was still jittery in SU1 so they've managed to fix something.

On 4/26/2025 at 1:46 PM, dogmanbird said:

since su2 I'm happy with performance, provided I lock the meta link ASW at 30hz. The terrain is very sharp using dlss 4 and the K preset.   Locking it at 30 was still jittery in SU1 so they've managed to fix something.

Hi what setting is this “I lock ASW at 30hz” ie where is this set.  Thanks

you can do it a few different ways, but one of the more convenient methods is to make a text file and copy the lines below into it. Then rename the file to .bat  You then run it before or during the game

 

 

echo server:asw.clock30 > “TEMP.txt”

echo exit >> “TEMP.txt”

call “C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugToolCLI.exe” -f “%~dp0\TEMP.txt”

del “TEMP.txt”

 

 

 the meta CLI appears to not be able to start up with the server clock command as a function, but it can read / execute it from a text file, so this batch file temporarily creates a file containing the 30hz clock command which the CLI reads, then deletes the temporary file

 

 server:asw.clock30       <--- this is the command that sets the clock and you can type it into the CLI.  

 server:asw.clock18         This also works but makes ASW a bit too wobbly for my liking

 

Just note that using the asw shortcut keys (e.g  numpad cntrl +1), restarting the PC, restarting headset, disconnecting headset, will reset ASW to 45hz

30hz ASW will be smoothest if you set the headset refresh to a multiple of 30, such as 90hz or 120hz

Edited April 29, 20251 yr by dogmanbird

btw - the above assumes you've installed the meta software in the default location 

C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugToolCLI.exe

 

Cheers 🙂

 

Try this FOV and Supper sampling trick described on this video.

I was using the FS2024 on a hardware even weaker that yours.