17 minutes ago, agent00729 said:

Thanks for getting back. I meant to say I was using sensitivity mode  prior, and am now testing non expert fps cap mode. Also, I was seeing 500 TLOD, even though I had 200 in settings, and IFR mode selected. Regardless, what is a good sim setting to set with this mode? For example, is the idea to set it to something I can get good performance in basically any scenario? Because 200 wouldn’t be that, as it is too high of a setting on the ground at a place like EGLL. Let me know if that makes sense.

I just need to clarify first, you say you are testing non expert fps cap mode, which implies you have a system or MSFS set FPS cap set for it to ever get in this mode, but in expert mode you are using FPS sensitivity mode, which is not really suitable when using an FPS cap. Are you using an FPS cap set somewhere and if so where and what is it?

Also, you say 200 won't be a good setting at EGLL on the ground, which I agree with, but unless you have your default MSFS TLOD set to 400+ for non expert mode or you have set TLOD Base Min to 200 in expert settings, which I doubt you have done either, then with AutoFPS you will never see 200 in this specific scenario anyway. What did you mean here?

Edited April 20Apr 20 by Reset XPDR

15 minutes ago, Reset XPDR said:

I just need to clarify first, you say you are testing non expert fps cap mode, which implies you have a system or MSFS set FPS cap set for it to ever get in this mode, but in expert mode you are using FPS sensitivity mode, which is not really suitable when using an FPS cap. Are you using an FPS cap set somewhere and if so where and what is it?

Also, you say 200 won't be a good setting at EGLL on the ground, which I agree with, but unless you have your default MSFS TLOD set to 400+ for non expert mode or you have set TLOD Base Min to 200 in expert settings, which I doubt you have done either, then with AutoFPS you will never see 200 in this specific scenario anyway. What did you mean here?

Essentially, I am trying to calibrate what in sim setting make sense for this mode. It feels like 200 is too high, because it pushes me way up to 400+ over a city like Tokyo (where I was testing), which, although my system can handle, causes massive stuttering and VRAM messages. It seems like the app thinks I have more room to increase settings than I have.
 

I have the cap set at 90 FG (so 30 x3).  

Edited April 20Apr 20 by agent00729

On 4/17/2026 at 12:22 AM, Reset XPDR said:

Re setting an FPS cap in MSFS 2020, the only internal option is to enable Vsync and hope that the full, half or one third setting produces the resultant FPS that you are seeking. If not, which is pretty likely, then you need to set it elsewhere. The simplest way is via nVidia Control panel if you have an nVidia GPU, under Manage 3D Settings, Program Settings, MSFS 2020 and then set Max Frame Rate to what you want. For AMD you can set it under Gaming, Graphics, Frame Rate Target Control. You can also use universal apps like MSI Afterburner, and even though it is a bit trickier to configure, it gives a very consisistent resultant frame rate.

I enabled Vsync and set the frame rate limit to 50% so I can get 30 FPS out of my 60 Hz monitor and I applied the setting but that did not result in a locked 30 FPS. The FPS kept fluctuating above 40-50 FPS as if I did not just enabled Vsync and set the frame limit to 50%. Is there anything wrong with what I did? Any idea why this didn't work? Thank you.

 

55 minutes ago, agent00729 said:

Essentially, I am trying to calibrate what in sim setting make sense for this mode. It feels like 200 is too high, because it pushes me way up to 400+ over a city like Tokyo (where I was testing), which, although my system can handle, causes massive stuttering and VRAM messages. It seems like the app thinks I have more room to increase settings than I have.
 

I have the cap set at 90 FG (so 30 x3).  

I just double-checked non-expert FPS cap mode to confirm what it does and with a default TLOD of 200, while it pushes up to 440 while seeking, it settles on no higher than 400 at altitude.

 

For what you want to achieve, non-expert mode is not really suitable unless you set default TLOD to 100 and use the VFR profile, which gives you 50-100 on the ground and 150-300 in the air, you are probably better off switching to expert FPS cap mode and manually configuring what you want eg. with these settings you will get a fixed 50 on the ground and 200-300 in the air:

Just be aware that FPS Cap mode is being deprecated in 0.4.6.8 about to be released very shortly, because it offers a better Fixed Target FPS mode in Sensitvity mode instead. You will still be able to use FPS Cap in 0.4.6.8, but it will offer to migrate you to the new mode in anticipation of it being phased out in a subseqent release. 

The reason I mention this is that you may want to try out this new mode in the latest test version that you can get here, which is pretty mature now, as it is easier to configure with none of this TLOD Top Extra business to have to worry about. eg. here is the equivalent of above

Edited April 20Apr 20 by Reset XPDR

11 minutes ago, xsever said:

I enabled Vsync and set the frame rate limit to 50% so I can get 30 FPS out of my 60 Hz monitor and I applied the setting but that did not result in a locked 30 FPS. The FPS kept fluctuating above 40-50 FPS as if I did not just enabled Vsync and set the frame limit to 50%. Is there anything wrong with what I did? Any idea why this didn't work? Thank you.

 

Make sure you have your Windows refresh rate set to 60Hz. I just tried setting tha on my system, which normally runs at 120 Hz refresh, and with Vsync enabled and frame rate limit 50% monitor refresh rate set in MSFS, it locks at 30 FPS, which is what you are after.

37 minutes ago, Reset XPDR said:

I just double-checked non-expert FPS cap mode to confirm what it does and with a default TLOD of 200, while it pushes up to 440 while seeking, it settles on no higher than 400 at altitude.

 

For what you want to achieve, non-expert mode is not really suitable unless you set default TLOD to 100 and use the VFR profile, which gives you 50-100 on the ground and 150-300 in the air, you are probably better off switching to expert FPS cap mode and manually configuring what you want eg. with these settings you will get a fixed 50 on the ground and 200-300 in the air:

Just be aware that FPS Cap mode is being deprecated in 0.4.6.8 about to be released very shortly, because it offers a better Fixed Target FPS mode in Sensitvity mode instead. You will still be able to use FPS Cap in 0.4.6.8, but it will offer to migrate you to the new mode in anticipation of it being phased out in a subseqent release. 

The reason I mention this is that you may want to try out this new mode in the latest test version that you can get here, which is pretty mature now, as it is easier to configure with none of this TLOD Top Extra business to have to worry about. eg. here is the equivalent of above

Great, thanks! Any reason the fps cap mode is being phased out?

14 minutes ago, agent00729 said:

Great, thanks! Any reason the fps cap mode is being phased out?

Because with my testing and feedback so far the new mode is easier to configure, provides better results and means I can remove about half of the TLOD automation code, thus improving maintainability for me. Unless I get valid feedback to the contrary that I can't othewise resolve, this will remain the plan.

17 hours ago, Reset XPDR said:

Make sure you have your Windows refresh rate set to 60Hz. I just tried setting tha on my system, which normally runs at 120 Hz refresh, and with Vsync enabled and frame rate limit 50% monitor refresh rate set in MSFS, it locks at 30 FPS, which is what you are after.

Thank you for the detailed instructions. I am ready to pull my hair almost. I made sure my monitor is set to 60 Hz in Windows Graphics settings and then I double checked my settings in the sim and yes V-Sync is set to ON and Frame Rate Limit is set to 50% and for some reason the FPS are not locking to 30 and are going as high as 60 sometimes. Very weird! Is there anything else you could think of? Thanks.

xsever,

I'm locking MSFS 2020 at 30 fps with my older system (i9-9900K, 32 GB and 3080 Ti) and I'm also using Lossless Scaling to get MSFS up to 60 fps.

Are you using nVidia Profile Inspector to lock the fps for MSFS as I'm doing below? That keeps MSFS at 30 fps and never goes above it. Note the Frame Rate Limiter V3 setting set to 30 FPS.

 

 

 

5 minutes ago, WallysWorlds said:

I'm locking MSFS 2020 at 30 fps with my older system (i9-9900K, 32 GB and 3080 Ti) and I'm also using Lossless Scaling to get MSFS up to 60 fps.

Are you using nVidia Profile Inspector to lock the fps for MSFS as I'm doing below? That keeps MSFS at 30 fps and never goes above it. Note the Frame Rate Limiter V3 setting set to 30 FPS.

Winner winner, chicken dinner! This did it. Thank you so much. I will start with 30 and then experiment with 35 and 40 maybe later on and then using adaptive mode in lossless scaling to go to 60.

I noticed in your screenshot that you're not running the latest version of profile inspector so I thought I'd flag that out to you.

Thank you again!

Any idea why the in-sim v-sync and frame limit options don't work for us?

So I’m strictly in VR with a BSB2e.  I’ve got an fps cap of 38 set in the sim, and a target of 37 set in AutoFPS.

What I’ve found, is that I get far smoother and more predictable increases / decreases in TLOD using Manual rather than Fixed, in FPS Sensitivity mode. 

When I use fixed, I notice the TLOD has issues maintaining a steady climb and a lot of times will actually drop itself back down to my min of 50, even when FPS seems to be holding steady.   

2 hours ago, FakeWayne said:

So I’m strictly in VR with a BSB2e.  I’ve got an fps cap of 38 set in the sim, and a target of 37 set in AutoFPS.

What I’ve found, is that I get far smoother and more predictable increases / decreases in TLOD using Manual rather than Fixed, in FPS Sensitivity mode. 

When I use fixed, I notice the TLOD has issues maintaining a steady climb and a lot of times will actually drop itself back down to my min of 50, even when FPS seems to be holding steady.   

Interesting observations.

FYI, Fixed intentionally behaves differently than Manual, with the primary objective of Fixed being to maintain your Fixed Target FPS, which means it reacts rapidly, and sometimes significantly, to FPS spikes that you do not see represented in the smoothed FPS+ value the app displays on its UI but are certainly present in the raw FPS data the app is receiving. On the other hand, Manual mode, aka Soft, requires headroom above and below your target FPS to work and while may seemingly work favourably with TLOD increases, it comes at the cost of larger FPS drops, which in VR can introduce stutters when using motion reprojection. ie. you are essentially chosing between FPS accuracy or TLOD consistency for Fixed and Manual modes respectively.

Your settings imply you are either running your BSB2e with motion projection at 75 Hz, making your half refresh rate lock rate 37.5 Hz, or are you not using motion reprojection and have just decided to cap at 37 FPS. If the former, then you truly are running a Fixed FPS arrangement and, if you are running any any newer version than 0.4.6.8-test9 then I am surprised the app has not auto-detected this and forced you to use a Fixed Target FPS of 37.5Hz, unless your FPS regularly drops below this and thus escapes the Fixed FPS detection logic. If the latter, and going below 37 FPS is acceptable and your Max Frame Rate in MSFS is a not to exceed cap rather than an actual fixed FPS, then sure Manual mode may provide more consistent TLOD results and still be smooth because the FPS fluctuations are not fighting a motion reprojection algorithm.

Could I ask that you PM me the contents of one or more of your app log files, located in %appdata%\MSFS_AutoFPS\log, where you try both Manual and Fixed modes as I would like to see what the app is doing with each of these modes. This is important for me to work out whether enforcing Fixed mode when Fixed FPS is detected, which I have done because many logs I see with Fixed FPS arrangements have Manual-like settings and sub-optimal outcomes, is a good idea or not.

Also, since 0.4.6.8-test11 the app supports fraction target FPS values, so if you are using motion reprojection with a 37.5 FPS base, try setting the target FPS to 37.5 in Fixed mode and see how that goes.

Edit: Based on your observations, I am going to tone down the reactiveness of Fixed mode to FPS drop spikes, as I must admit that below Alt TLOD Top with the Extra option in particular, there is no way for it to recover and it is easy to trigger so it likely is too reactive.

Edited April 21Apr 21 by Reset XPDR

1 hour ago, Reset XPDR said:

Your settings imply you are either running your BSB2e with motion projection at 75 Hz, making your half refresh rate lock rate 37.5 Hz, or are you not using motion reprojection and have just decided to cap at 37 FPS

So I’m not using Motion Smoothing if that’s what you’re referring to.  But yes, Steam VR is auto throttling me to half refresh rate of 38, and subsequently applying a ~50% reprojection ratio. I've also locked to 38 in the sim as well even though it's probably not even completely necessary. 

The reason I set 37 as my target and not 37.5 is to give me just a bit of room for TLOD to hold steady, and not decrease when I drop from 38 to 37….since 37 is still perfectly smooth.  Only at 36 and below do things start to get hairy.

I can definitely PM you a couple of logs later tonight once I get home from work.

34 minutes ago, FakeWayne said:

So I’m not using Motion Smoothing if that’s what you’re referring to.  But yes, Steam VR is auto throttling me to half refresh rate of 38, and subsequently applying a ~50% reprojection ratio. I've also locked to 38 in the sim as well even though it's probably not even completely necessary. 

The reason I set 37 as my target and not 37.5 is to give me just a bit of room for TLOD to hold steady, and not decrease when I drop from 38 to 37….since 37 is still perfectly smooth.  Only at 36 and below do things start to get hairy.

I can definitely PM you a couple of logs later tonight once I get home from work.

The logs would be good thanks. I am experimenting with the TLOD reduction code for Fixed mode right now and it difficult to predict whether a single FPS drop is just a temporary spike from something like a view transition, hence should be ignored, or is the start of a downwards spiral. The longer the app waits to confirm a drop trend before acting means the longer, and possibly deeper, that the FPS drop is experienced, which is undesirable with a Fixed FPS setup, and the shorter it waits, the greater likelihood of it being fooled by something temporary and then potentially over-reacting. It is a difficult balance to achieve, but I am working on it!

 

I've retuned Fixed Target FPS to not reduce TLOD unless it gets two raw consecutive FPS drops, or a longer term average FPS drop but still requiring a current single raw FPS drop, and I think I have tamed the balance beast a bit better. 

Here's a chart of a quick circuit I did at NZQN in the C208B in Fixed mode, firstly with the standard Extra option enabled:

And again with the FreeTLOD option:

You can see it no longer gets sucked in by single sample FPS dips, pausing TLOD increases rather than dropping TLOD as it did before. If a drop is sustained at least two samples it acts on the average of the last two, so it should not overract if it was coming out of a dip but still in it enough to trigger. BTW, don't be concerned about the big TLOd drop 2/3 of the way through the first graph as it is because I had a large TLOD and small altitude range set to expedite testing, so this drop is purely to keep me on altitude schedule for landing ie. nothing to do with Extra reductions.

I hope this alleviates @FakeWayne's rightful concern that Fixed is too aggressive on the down swings and decides to give it another go in 0.4.6.8-Test16 which has now been released. I would also appreciate if others could give Fixed Target FPS a go and provide feedback, either good or bad, as it all helps make it better.

Edited April 21Apr 21 by Reset XPDR