Howcome I cant set Vsync (the setting in the game) to work properly (that is: at all). I can click Vsync on and set 30 or 60, but the fps are not locked at all. Its like having Vsync off. Right now Im using a max fps in Nvidia control panel instead (no Vsync selected). I do get more CTD this way, though…
My apologies if you already know this, but are you aware the V-sync settings in the sim are really 60=100% of your monitor refresh rate, 30=50%?
So if you’re running that LG monitor at 144 Hz refresh rate, and set V-sync in the sim to 30, it’s going to cap your fps at 72. Depending on your settings, you may or may not be able to get anything that high.
I have a 1440p monitor, refresh rate set at 75Hz. I set V-sync at 30fps (so really 50%). The sim cruises along at 37 fps happily! In my case, I let the Nvidia GeForce app optimize the sim settings, which results in something somewhere between “High” and “Ultra”. (This on an RTX3080). Can’t remember the last time I had a CTD.
Can you show a screenshot of your nvidia control panel settings for MSFS? If I recall if vsync is set in the NV control panel then this will override the application setting.
The ingame vsync works fine (as the above post describes) when there is no NVCP override.
Max framerate is set to OFF in the Nvidia Control Panel. I have tried to use it to cap framerate, but always come back to my current method… it just works.
Thank you! I have been thinking about this for so long time now. It was starting driving me nuts. Should I change the over all refresh rate of the monitor? Can I set the refresh rate for each app and game or should i keep it at 144 as a general setting?
…and the refreshrate setting, can I change that individuallay for each app / game in some way? The last (at the bottom) setting did not do the trick so its back to standard.
Should Vsync be “controlled by 3d program” or be “off” ?
I’m no expert, so maybe someone else has a better idea.
I would try setting the MSFS V-Sync to 20fps (which is really 1/3rd of your monitor refresh rate, 144/3= 48).
If your hardware + the graphics settings you’re using in the sim can support 48 fps, fantastic. If that doesn’t work, try changing the refresh rate of your monitor. For example, set monitor to 120 Hz refresh, then 1/3 would be 40 fps. Just play with it until you find the combination that is smooth and stable.
But again, I don’t claim to know much about this. I just know doing it this way works for me, and I get to spend my time flying in the sim instead of fiddling with graphics settings.
Ok. thanks for the info about the percentage of refresh rate that each setting gives in Max FPS. Whoever decided to display it this way at MS/Asobo needs a different job. Frame rate limit of 30 FPS does not equate to 50% of your current monitor refresh rate (unless in the one specific circumstance that your refresh rate is 60!). In my case I was setting it to 60FPS which meant 165FPS on my system - no wonder I was confused.
If it wasn’t for the drawbacks of TrackIR then Gsync would be the way to go - super smooth when no tracking needed and Vsync off.
How could you understand if you do not experience the problem that I do? Head movement is stuttery with TrackIR unless I can lock refresh rate and FPS to 60 or 120. Same problem I have in DCS. TrackIR has an update rate of 120 and apparently multiples of that should be smooth (30, 60, 120, 240) but only 60 and 120 work for me.
From what I have read it is a problem with TrackIR and has been for a number of years.
Turn TrackIR off and everything is super smooth .
Well well… Seems I get stutter when landing, even on small runways on the US countryside. Might do some experimenting, lowering to 30 and turn on Vsync (not sure if that will help, Im having a hard time thinking I’ll go below 45fps on the countryside even at landing). Must be something else.
Maybe I don’t experience any stuttering because I don’t use VSync and lock my FPS in NVCP? I have flown for some time now with it set to 39. This is with G-Sync On, of course.
My Samsung G7 monitor’s native refresh rate is 240 Hz, which is what I run it with in Windows.
I can see with PresentMon that the FPS limit in MSFS is just changing the V-sync present interval from 1, 2, 3. That is not how a real CPU wait based FPS limiter works. A CPU wait based limiter isn’t necessarily tied to refresh rate, and it helps avoid stale frames in the rendering pipeline. The developers of the game either used the present interval because it was faster to implement, or it helped alleviate stuttering having extra frames in the pipeline, or both.
I’m not very educated about technical things such as this but I have noticed that I get less stutters when using VSync on in game at 20 with a refresh rate of 120hz. This locks the FPS to 40.
As opposed to using Nvidia Control Panel to lock 36 FPS at 144hz.
Is that because of the reasons that you mentioned?