On 12/1/2025 at 9:56 AM, outermarker said:

Sorry, native in this case means pre frame gen? So if I’m using 2x DLSS FG and have AutoFPS Target FG FPS set to 60, should I set the dynamic settings target to 20?

silly question @Reset XPDR  if using x2 FG and target it 60 fps,  why set dynamic settings target to 20 and not 30 

 20 x 2 (fg) = 40  

 30 x 2 (fg)  = 60  etc etc

again sorry if its a silly question

equally if I was trying to target FG FPS TO 72 ,  what would I set dynamic settings target to ??

 

thanks again for the help.  i hope this su4 really does do something to the frames as people keep saying

Edited December 5, 2025Dec 5 by fluffyflops

2 hours ago, fluffyflops said:

silly question @Reset XPDR  if using x2 FG and target it 60 fps,  why set dynamic settings target to 20 and not 30 

 20 x 2 (fg) = 40  

 30 x 2 (fg)  = 60  etc etc

again sorry if its a silly question

equally if I was trying to target FG FPS TO 72 ,  what would I set dynamic settings target to ??

 

thanks again for the help.  i hope this su4 really does do something to the frames as people keep saying

"If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results."

60 FPS with FG (2×) corresponds to 30 FPS native, -10 for the dynamic settings target you end up with 20.

For your example, 72 FPS with FG = 36 FPS native, -10 gives 26. I think you can only set increments of 5, so 25.

52 minutes ago, outermarker said:

"If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results."

60 FPS with FG (2×) corresponds to 30 FPS native, -10 for the dynamic settings target you end up with 20.

For your example, 72 FPS with FG = 36 FPS native, -10 gives 26. I think you can only set increments of 5, so 25.

thanks alot. 

 

So im running a 120 hertz Monitor with adative half vsync, so 60 fps.  with FG x2 to get it to 60.

so this above is correct I need to lock at dynamic at 20 right ?

 

 

8 hours ago, rjack1282 said:

I love the auto update but would still like to get the notepad popup with the release notes.

Auto update, which is the option where you have to confirm you wish to install the update, does still show the notepad popup after the auto install. Silent update currently does not show the notepad popup.

6 hours ago, fluffyflops said:

silly question @Reset XPDR  if using x2 FG and target it 60 fps,  why set dynamic settings target to 20 and not 30 

 20 x 2 (fg) = 40  

 30 x 2 (fg)  = 60  etc etc

again sorry if its a silly question

equally if I was trying to target FG FPS TO 72 ,  what would I set dynamic settings target to ??

 

thanks again for the help.  i hope this su4 really does do something to the frames as people keep saying

It is not a silly question as dynamic settings is a bit of a tricky one to get working with AutoFPS if you are not using an FPS cap.

The reason it is so tricky is that in my limited testing without a frame rate limit, if you set dynamic setting the same as your target FPS then dynamic tends to activate at a frame rate even higher than what you have set it to for some strange reason. This is why I suggest you set dynamic setting at least 10 FPS lower than your target FPS (and it does need to be the native equivalent of your target FPS because that's how MSFS is configured).

For example, here I have my FPS uncapped, with FSR3 getting around 110 FPS, so 55 FPS native, and dynamic setting set to 55 to line up with native FPS. As you can see, even though I am achieving the required 55 FPS native, dynamic setting feels the need to start activating, which IMO is too pessimistic:

 

If I change to using an FPS cap by setting max frame rate in MSFS to 60, then set dynamic settings to 60 and target FSR3 FPS to 120, ie everything to 60 FPS native, dynamic settings now behaves itself.

 

For your particular configuration, I would try using an FPS cap setup and set max frame rate in MSFS to 30, dynamic settings to 30 and target FSR3 FPS to 60 and, very importantly, use FPS cap mode in AutoFPS (which has been designed to work with an FPS cap).

On 12/5/2025 at 9:57 PM, Reset XPDR said:

It is not a silly question as dynamic settings is a bit of a tricky one to get working with AutoFPS if you are not using an FPS cap.

The reason it is so tricky is that in my limited testing without a frame rate limit, if you set dynamic setting the same as your target FPS then dynamic tends to activate at a frame rate even higher than what you have set it to for some strange reason. This is why I suggest you set dynamic setting at least 10 FPS lower than your target FPS (and it does need to be the native equivalent of your target FPS because that's how MSFS is configured).

For example, here I have my FPS uncapped, with FSR3 getting around 110 FPS, so 55 FPS native, and dynamic setting set to 55 to line up with native FPS. As you can see, even though I am achieving the required 55 FPS native, dynamic setting feels the need to start activating, which IMO is too pessimistic:

 

If I change to using an FPS cap by setting max frame rate in MSFS to 60, then set dynamic settings to 60 and target FSR3 FPS to 120, ie everything to 60 FPS native, dynamic settings now behaves itself.

 

For your particular configuration, I would try using an FPS cap setup and set max frame rate in MSFS to 30, dynamic settings to 30 and target FSR3 FPS to 60 and, very importantly, use FPS cap mode in AutoFPS (which has been designed to work with an FPS cap).

thanks so much for this,  they should offer you at a job at ms/asobo.  your a hero

Is 400 TLOD the highest possible? I'm hitting that easily enough in VR now so just wondering if there's a way to get more whilst using this app.

2 hours ago, MarcG said:

Is 400 TLOD the highest possible? I'm hitting that easily enough in VR now so just wondering if there's a way to get more whilst using this app.

Yes. You can go up as high as 1000, which is the default highest possible TLOD in the app, if you really want to. Just be aware that at very high TLOD levels, MSFS might be fine looking in the same direction, but panning can easily induce stutters, not because of AutoFPS but simply because of how much data MSFS must redraw for the changing scene.

On 12/5/2025 at 11:46 PM, rjack1282 said:

I love the auto update but would still like to get the notepad popup with the release notes.

Your comment has sat with me a few days and I think you are right in implying that currently silent updates is perhaps too silent, and an update can go completely unnoticed.

I have just released the next test build 0.4.5.12 (nothing major, just small fixes and tweaks I find as I use the app myself) and with silent updates it is still non-interactive but now auto-shows the release notes in notepad after if has completed so at the very least you know an update has occurred.

7 minutes ago, Reset XPDR said:

Yes. You can go up as high as 1000, which is the default highest possible TLOD in the app, if you really want to. Just be aware that at very high TLOD levels, MSFS might be fine looking in the same direction, but panning can easily induce stutters, not because of AutoFPS but simply because of how much data MSFS must redraw for the changing scene.

Ok cool thanks, I'll have a look one day just good to know for now 🙂

19 hours ago, Reset XPDR said:

Your comment has sat with me a few days and I think you are right in implying that currently silent updates is perhaps too silent, and an update can go completely unnoticed.

I have just released the next test build 0.4.5.12 (nothing major, just small fixes and tweaks I find as I use the app myself) and with silent updates it is still non-interactive but now auto-shows the release notes in notepad after if has completed so at the very least you know an update has occurred.

I messed up the nomenclature but this was exactly was I meant. Thanks. 

I've noticed that when I'm not meeting my "Target FPS" over demanding areas (LA or NYC for example), that my TLOD is not lowering to compensate.

For instance:  I have my FPS cap set to 38 in sim.  I've got my Target Fps set to 38 in Auto FPS.  I'll take off from a field with not much around me and climb to 5,000 ft while my TLOD slowly rises to 200+ and my fps stays pinned at 38.  However, once I start passing over demanding photogrammetry, I'll see my FPS creep lower and lower, down into the low 30's or high 20's.  Yet, my TLOD is still sitting at 200.  Shouldn't it be decreasing to compensate for the loss of framerate, and to get me back to my Target of 38? 

Is the app able to sense wide open rate, then lock it xFPS or x% below that, dynamically?

17 minutes ago, FakeWayne said:

I've noticed that when I'm not meeting my "Target FPS" over demanding areas (LA or NYC for example), that my TLOD is not lowering to compensate.

For instance:  I have my FPS cap set to 38 in sim.  I've got my Target Fps set to 38 in Auto FPS.  I'll take off from a field with not much around me and climb to 5,000 ft while my TLOD slowly rises to 200+ and my fps stays pinned at 38.  However, once I start passing over demanding photogrammetry, I'll see my FPS creep lower and lower, down into the low 30's or high 20's.  Yet, my TLOD is still sitting at 200.  Shouldn't it be decreasing to compensate for the loss of framerate, and to get me back to my Target of 38? 

What auto method, TLOD Base and Top Mins and Auto Setting Reduction settings are you using? If you are using FPS Cap mode (implied by your mention of an FPS cap) and your TLOD Top Min is 200 and you are not using Auto Settings Reduction, then yes TLOD will not go below TLOD Top Min, as the settings name implies. If your setting are something else, please let me know in more detail so I can try and reproduce.

16 minutes ago, Noel said:

Is the app able to sense wide open rate, then lock it xFPS or x% below that, dynamically?

I am not sure what you mean by this. Please elaborate.