40 minutes ago, mikeymike said:

Now that i have a 5080 how would i set it up with using frame gen?

Don't know if it's the way but this is my way (5070ti, max 60hz display) (check this post as well : 

• MSFS_AutoFPS:
  • Target: FG (fps) it should be automatic since 0.4.4.10-RC3
  • Auto Target FPS: check
  • MFG Off
• MSFS Graphics :
  • Anti-aliasing: NVIDIA DLSS Super Resolution
  • NVIDIA DLSS super resolution: DLAA
  • Frame Generation: NVIDIA DLSS
  • (new in SU3) Max Frame rate : 30. If you're SU2 do it via the config file UserCfg.opt.
  •  
• nvidia App
  • Vertcial Sync: ON
  • Max Frame Rate: 60
  • DLSS Override Model Presets: latest

More info: https://20-100-video.blogspot.com/2025/05/my-pc-settings-for-msfs2024-may-2025.html

Edited May 26, 20251 yr by vbazillio

1 hour ago, mikeymike said:

I am very Happy with autofps.

Now that i have a 5080 how would i set it up with using frame gen?

60hz tv here.4k

Do i just select mfsg x 2?in autofps?

Vsync off? Or on?

Will it help with vram as it has only 16gb? And dx12

 

Thanks

Mike

 

 

I know you didn't ask this of me directly but as this type of question is coming up much more often I have added the following to the FAQ section of the readme after the latest update, which I hope you find helpful:

You developed this app and must therefore know how to best configure it, so surely you can tell me the best settings for me to use?

• The best settings for you to use are highly dependent on your system's capabilities, what other addons and supporting apps you use, and what your expectation of "best" actually is - higher FPS, improved visuals, smoother experience - some of which are mutually exclusive (i.e you can have one but only at the expense of another).
• Additionally, there are now thousands of users of this app and I simply don't have the time to provide individual settings advice to everyone that asks.
• As such, your best course of action is to start off with non-expert mode to see what the app actually does and when.
• Once you are comfortable with how the app operates, enable expert settings and start reading the tooltip and readme on what each setting does.
• When making changes, it is best to make small changes to only a few settings so that you can see the effect of them and adjust as desired.

Also, as you see by the above post by @vbazillio (thank you!), other users with similar systems and setups are willing to share their experience here too.

 

Edited May 26, 20251 yr by Reset XPDR

1 hour ago, iborg1979 said:

Works brillantly with MSFS 2024 SU2. Flying the 777F, in 4K with FSR3/TAA I'm getting 70+ FPS with TLOD at 400, most settings on high/ultra.

"It just works".

 

1 hour ago, Adamski_NZ said:

Though it's already a 204pp topic, I still think there's enough space to voice some appreciation for an addon that we may have once thought to be destined for the boneyard - but has become as indispensible as Addons Linker. It's been an interesting journey, watching it get tweaked and improved.

Kiwis are fond of their Pavlovas, so here's a Kiwi Oscar for you!

 

Thanks guys. And that Kiwi Oscar is gold! 😆

2 hours ago, vbazillio said:

Don't know if it's the way but this is my way (5070ti, max 60hz display) (check this post as well : 

• MSFS_AutoFPS:
  • Target: FG (fps) it should be automatic since 0.4.4.10-RC3
  • Auto Target FPS: check
  • MFG Off
• MSFS Graphics :
  • Anti-aliasing: NVIDIA DLSS Super Resolution
  • NVIDIA DLSS super resolution: DLAA
  • Frame Generation: NVIDIA DLSS
  • (new in SU3) Max Frame rate : 30. If you're SU2 do it via the config file UserCfg.opt.
  •  
• nvidia App
  • Vertcial Sync: ON
  • Max Frame Rate: 60
  • DLSS Override Model Presets: latest

More info: https://20-100-video.blogspot.com/2025/05/my-pc-settings-for-msfs2024-may-2025.html

Thank you

 

In MSFS 2020 the program never autostarts anymore

Unistalled and reinstalled with the autostart with fsuipc option but it never autostart when fsuip opens  😞

1 hour ago, motishow said:

In MSFS 2020 the program never autostarts anymore

Unistalled and reinstalled with the autostart with fsuipc option but it never autostart when fsuip opens  😞

Make sure you are using the latest app and FSUIPC version, namely 0.4.4.10 and 7.5.3 respectively.

Also, with the newer versions of FSUIPC, MSFS has to be running before any FSUIPC autostart apps will run. Running FSUIPC alone will not autostart AutoFPS until you start MSFS.

If all that is correct and you still have an issue, can you personal message me the contents of your FSUIPC7.ini file, located in the directory whereever you installed FSUIPC7 to, and I will take a look.

 

 

On 5/26/2025 at 6:55 AM, vbazillio said:

 

• MSFS_AutoFPS:
  • Target: FG (fps) it should be automatic since 0.4.4.10-RC3
  • Auto Target FPS: check
  • MFG Off
• MSFS Graphics :
  • Anti-aliasing: NVIDIA DLSS Super Resolution
  • NVIDIA DLSS super resolution: DLAA
  • Frame Generation: NVIDIA DLSS
  • (new in SU3) Max Frame rate : 30. If you're SU2 do it via the config file UserCfg.opt.
  •  
• nvidia App
  • Vertcial Sync: ON
  • Max Frame Rate: 60
  • DLSS Override Model Presets: latest

Pretty much what I have setup.

Only under (General/Target) I had (PC) for some reason. Dont even know what is means. Did not find the instructions very clear on what the different settings means either. I suspect FG is for frame generation, but who knows.

 

15 hours ago, Ron Lefebvre said:

Only under (General/Target) I had (PC) for some reason. Dont even know what is means. Did not find the instructions very clear on what the different settings means either. I suspect FG is for frame generation, but who knows.

 

PC is the term MS/Asobo used in MSFS 2020, the only version around when AutoFPS was first created, for your normal graphics settings.

I do note that MSFS 2024 no longer uses this terminology, so I will define it in the readme for those not familiar with the term.

As for FG, or frame generation as you correctly assume, is a very common term for MSFS graphics and this acronymn, along with all other flavours of FG, are already defined in the readme FAQ section as follows:

How does this app work for Frame Generation (FG) users?

• The app does detect correct FG FPS when FG (native nVidia or FG mod) is enabled in MSFS, however FG is only active when MSFS is the focused window and becomes inactive when not, through your graphics driver not this app.
• To see correct MSFS FG FPS, use the app's "On Top" option to overlay this app over MSFS and give MSFS the focus.
• If MSFS FG is being incorrectly reported as enabled by the app, the likely reason is that either the FG mod had been installed and removed or you have disabled Hardware Accelerated Graphics Scheduling under Windows settings and the now the now greyed out MSFS FG setting may show that it is off but it is still set to on internally to MSFS. To fix, change the DLSSG line in your UserCfg.opt file to be DLSSG 0.
• Lossless Scaling (LS) FG, including the scaling multiplier used, is also detected and the correct LSFG multiplied FPS is displayed.
  • Make sure your LSFG app is updated to the latest version that supports LSFG 3.0 (2.13.2 or later).
  • The app will first try to use an LS profile with the specific name MSFS2020 or MSFS2024, depending on which MSFS version is currently in use, to obtain these settings.
  • If such an MSFS2020 or MSFS2024 profile does not exist then the settings in the first profile found in the config file, usually named Default, will be used.
  • When adaptive frame generation is detected, a base FPS will be used for the target FPS because the frame generation multiplier is variable and is not currently detectable.
  • If you make changes to your LS settings after starting a flight, press AutoFPS's Reset button so that AutoFPS can redetect them correctly.
• FSR3 FG is now supported for MSFS 2024 as of SU2.
  • Although FSR3 FG can be implemented with an adaptive multiplier, MSFS currently implements it with a fixed 2X multiplier that is active regardless of whether MSFS has the focus or not.
• Multi Frame Generation, available only for users with 5000 series nVidia GPUs, is unable to be auto detected by the app at this time due to the privileged access need to read this setting.
  • In the interim, a manual MFG multiplier and target MFG FPS selection will be presented on the UI when a 5000 series nVidia GPU is detected.
  • Match the app's MFG multiplier with what you have set for MFG with MSFS in nVidia settings.
  • Set to MFG Off if not using MFG or using an alternative FG method.
  • Feature can be removed by the user setting MfgModeMultEnabled to false in MSFS_AutoFPS.config in the app root directory.
• Detection of all FG types other than LSFG is automatic within 5 seconds of making the change. Detection of LSFG is normally only performed upon starting a flight. If LSFG is started after this detection is normally performed, press the Reset button for it to be detected.
• Only one type of FG can be active at a time for the app to show FPS correctly. In particular, using native nVidia or the FG mod AND LSFG will cause incorrect FPS calculations in the app because they function differently when MSFS loses focus. Choose one or the other if you want to use them with this app.

There is also this section in the Usage/Configuration section, which describes what the target FPS, and associated drop down, do in great detail:

Target FPS - The most important setting in this app. (10 - 200 allowable)

• Set it to what FPS you want the app to target while running, noting that this value should be at the mid to lower end of what your system is capable of otherwise the app will be unlikely to achieve it.
• There is a setting for each graphics mode (PC, FG, LSFG, MFG, FSR3 and VR) and each flight type (VFR, IFR and, if Expert mode, 4 user profiles). Automatically defaults to the currently detected graphics mode, however the user can change the target FPS for graphics modes other than what is currently active.
  • Selectable by using the drop down list of target FPS types in the app window.
  • Target FPS type drop down list background will change to orange when the target FPS type is different to the current graphics mode to clearly indicate this difference to the user.
  • Changes to target FPS for a type different to the current graphics mode will be saved to the config file without reloading the UI as it does not affect any other displayed settings.
  • Changes to any other setting on the UI will reload the target FPS type for the current graphics mode.
  • Particularly useful for VR users who have previously had to be in VR and remove their headset to change this setting.
• If using MSFS FG, the target FPS you set is your desired FG Active FPS, not the FG Inactive FPS you see when this app has the focus instead of MSFS.
• If using an FPS cap, or Vsync for the same purpose, it is strongly recommended you use the FPS Cap automation method, available in Expert mode, with an FPS target matching your FPS cap and works well in such instances.
• If using such an FPS cap with either FPS Sensitivity or Tolerance automation methods you will need to set your target FPS to be at least 5% lower than that cap to allow the automation logic to function correctly. This potentially introduces screen tearing, or breaks motion reprojection in VR, hence why Auto TLOD is preferred.

Please tell me what you don't find clear and I will update it.

1 hour ago, Reset XPDR said:

PC is the term MS/Asobo used in MSFS 2020, the only version around when AutoFPS was first created, for your normal graphics settings.

1 hour ago, Reset XPDR said:

I do note that MSFS 2024 no longer uses this terminology, so I will define it in the readme for those not familiar with the term.

Further to this, I need to update the release app version shortly to fix an auto update issue with future test versions, so I could change the term PC to something else more meaningful for when using MSFS 2024, but the question is to what?

I could call it GEN or GFX as it is under general and graphics settings respectively, but some of the FG flavours sit under these titles as well, which would be inconsistent. I could therefore call it NonFG, or more likely NFG as 5 letters is too much for other UI item spacing, or even STD, with its disease-like connotations 😄, for standard but I think this could create more confusion than just leaving as PC the way it has always been.

So unless anyone else has a better suggestion palatable to the masses, I think I'll leave it as it is.

 

Understand the 5 letters UI limitation but STANDARD is the one that works better. What about DEFAULT (DEF?) even if there isn't really any default settings 😉

Talking about UI, the confusion exists as well as the selected item (PC, VR, FG...) seems to be part of the sentence "Target ___ FPS". What is (for example) a "Target VR fps" or "Target MFG fps" ? I'm not sure because you know better your UI than I, but splitting this line in two with first, Profil: (PC, VR, FG, MFG...) and second "Target FPS : ___" (followed by the two check boxes)... Just my 2 cents as a basic user.

58 minutes ago, vbazillio said:

Understand the 5 letters UI limitation but STANDARD is the one that works better. What about DEFAULT (DEF?) even if there isn't really any default settings 😉

Talking about UI, the confusion exists as well as the selected item (PC, VR, FG...) seems to be part of the sentence "Target ___ FPS". What is (for example) a "Target VR fps" or "Target MFG fps" ? I'm not sure because you know better your UI than I, but splitting this line in two with first, Profil: (PC, VR, FG, MFG...) and second "Target FPS : ___" (followed by the two check boxes)... Just my 2 cents as a basic user.

DEF could work. Copilot is also suggesting RAW or BASE, the latter of which I have used myself when referring to non-FG FPS.

Re "Target ___ FPS", that is intended to be shorthand for saying "Your target FPS when in __ graphics mode" without overrunning that area of the UI. While I could split the line as you suggest, there is no room to do it where it lives and I want to keep the user focused on what they are changing in one phrase. 

This setting short hand is reasonably consistent across the UI, but one thing I have noticed with this particular control is that there is no tool tip for the graphics mode drop down and that will be rectified in the next release.

Edited May 28, 20251 yr by Reset XPDR

I've decided to change the term PC to BASE for the selected target FPS graphics mode for both MSFS 2020 and 2024 as it is the most accurate term to describe FPS without any form of frame generation applied ie. it is the BASE FPS without any frame generation multiplication.

I have also added a tooltip for this drop down list, which I have made very descriptive as it refers to a potentially confusing setting that lives in the non-expert section of the UI.

I am planning on releasing 0.4.4.11 in the next half day, as mentioned previously primarily to fix an auto update issue with future test versions, so let me know ASAP if you have any serious objection to what I have proposed and what you propose as alternative.

 

Sounds good to me - though I think a tiny punctuation edit on the tooltip may help 😉

"Graphics mode for Target FPS selection:
BASE: default, with no frame generation. AUTO: detects when graphics mode is changed. MANUAL: select to change non-active graphics mode settings (background changes to orange)"

Not a criticism ... just trying to make things a little clearer! One question though ... is the 2nd mention of "graphics mode" (in red, above) the AutoFPS graphics mode or the MSFS graphics mode?

2 minutes ago, Adamski_NZ said:

Sounds good to me - though I think a tiny punctuation edit on the tooltip may help 😉

"Graphics mode for Target FPS selection:
BASE: default, with no frame generation. AUTO: detects when graphics mode is changed. MANUAL: select to change non-active graphics mode settings (background changes to orange)"

Capitalising AUTO and MANUAL like BASE implies that those are drop down selections too, which they are not. Better to leave it as is IMO.

3 minutes ago, Adamski_NZ said:

Not a criticism ... just trying to make things a little clearer! One question though ... is the 2nd mention of "graphics mode" (in red, above) the AutoFPS graphics mode or the MSFS graphics mode?

The graphics mode can be changed in multiple places: MSFS itself, but also the Lossless Scaling or nVidia app can change it too, hence the non-specificity of the term.

 

38 minutes ago, Reset XPDR said:

Capitalising AUTO and MANUAL like BASE implies that those are drop down selections too, which they are not. Better to leave it as is IMO.

The graphics mode can be changed in multiple places: MSFS itself, but also the Lossless Scaling or nVidia app can change it too, hence the non-specificity of the term.

 

Aaaah ... I see ... OK 🙂