52 minutes ago, abennett said:

I am not seeing FG Active in 2024 with SU2 beta, so have had to half the target frames in the app to just what would be the native frames.

Which actually I prefer, when using FG it seems smoother when you set native target rather than a target including FG frames because the native frames are more stable.

This was sent to me in another thread:

"Had the same problem with FrameGenMod after SU2. Went beck to live version and noticed, that there was no difference with Frame Gen on or off. I was getting about 40 fps. 

I've found the solution by deactivation Smart Docking System in the option menu from the Dev Mode. 

This system was preventing the Frame Gen Mode to work as it should be."

38 minutes ago, kevinfirth said:

This was sent to me in another thread:

"Had the same problem with FrameGenMod after SU2. Went beck to live version and noticed, that there was no difference with Frame Gen on or off. I was getting about 40 fps. 

I've found the solution by deactivation Smart Docking System in the option menu from the Dev Mode. 

This system was preventing the Frame Gen Mode to work as it should be."

Thanks, I don't use the FG mod.

FG itself is definitely working for me in the beta, just not showing in the AutoFPS app.

Still happy with MSFS after changing my 3080 for a 5070ti... and Beta testing MSFS2024 SU2 #2 (v1.4.9.0).

Tested with MSFS_AutoFPS (0.4.4.7). I set my "Target MFG FPS Cap" to 60 as my screen is 60Hz max.

With MSFS2024 SU2, I set the Framerate Multiplier to 2x (it seems it's the only value which is recorded whatever 3x or 4x). Run steady 60 fps with my PC and FSLTL.

Thank you again!

@Reset XPDR Everything was working fine, at least with AutoFPS 4.4.8 Test-16.

But after updating AutoFPS to Test-20 it no longer detects that FG is active on my MSFS2024 SU1 install.

I have reveret to the 4.4.7 Release version for now.

Deleted

Edited March 29, 20251 yr by Reset XPDR

It's crazy. I've been searching for the error all day.
Just reverted to 0.4.4.7 with MSFS 2020 SU1 and everything is working again.
I can't understand it.

FG was gone. No it is back

Edited March 29, 20251 yr by f.skywalker

For those experiencing FG detection issues recently, please be advised the following:

• MSFS_AutoFPS v0.4.4.7 (current formal release version available here) detects FG correctly with MSFS 2020 and MSFS 2024 SU1 only. You need to press the app's Reset button if you change your FG setting when in a flight session for the change to be detected.
• MSFS_AutoFPS v0.4.4.8-test24 (latest test version available here) detects FG correctly with MSFS 2020, MSFS 2024 SU1 and MSFS 2024 SU2 Beta. It will also automatically detect when you change your FG setting at any time.
• Neither AutoFPS version automatically detects MFG for 5000 series cards, but it should be configurable manually on either of them.

If this does not match your experience, please tell me what specific AutoFPS and MSFS versions, including whether MS Store or Steam for the latter, are experiencing the issue. Thanks.

Edited March 29, 20251 yr by Reset XPDR

Usually I don't have any issues with AutoFPS but I seem to now have two

1) since test 48.23 when I start AutoFPS and then start MSFS2024 SU2b I get a popup error aboutnot identifying msfs. If I close and restart AutoFPS it connects and stays connected.

2) RTX3090 using FSR3 -  dev m ode shows 54fps - AutoFPS shows 27 - always exactly half what dev mode shows. Old versions did exactly opposite - AutoFPS always double dev mode when MSFS has focus.  Now makes no difference what process has focus - AutoFPS is always half dev mode on my system.

33 minutes ago, vgbaron said:

1) since test 48.23 when I start AutoFPS and then start MSFS2024 SU2b I get a popup error aboutnot identifying msfs. If I close and restart AutoFPS it connects and stays connected.

If you start AutoFPS at exactly the same time as MSFS this can sometimes happen, but it gives it 5 goes over 5 seconds to try and connect correctly. Either start AutoFPS at least a few seconds before MSFS, have it auto-start with MSFS or FSUIPC, or start it when you are in the main MSFS menu and you shouldn't have an issue.

 

33 minutes ago, vgbaron said:

2) RTX3090 using FSR3 -  dev m ode shows 54fps - AutoFPS shows 27 - always exactly half what dev mode shows. Old versions did exactly opposite - AutoFPS always double dev mode when MSFS has focus.  Now makes no difference what process has focus - AutoFPS is always half dev mode on my system.

Per the release notes for 0.4.4.8-test19: 

• FSR3 FG is now detected, however a base target FPS must be used as the FG multiplier is variable for this type of FG.

Edited March 29, 20251 yr by Reset XPDR

4 hours ago, Reset XPDR said:

Either start AutoFPS at least a few seconds before MSFS, have it auto-start with MSFS or FSUIPC, or start it when you are in the main MSFS menu and you shouldn't have an issue.

It and other MSFS supporting apps (that has a nice ring to it), can not only be started from settings within Addons Linker, the delay to start time for apps can also be spec'd.

FYI, a progress update on where we are at with the 0.4.4.8 test program, which is close to finalising once MSFS SU2 becomes more stable and activates native MFG support for 5000 series GPUs. 

In a nutshell, MSFS 2020 functionality and its UI have been largely left alone, with a few improvements  here and there found when developing MSFS 2024 changes. MSFS 2024 functionality and its UI get a fairly major work over, with Cloud Quality Reduction and Auto OLOD removed as standalone options and subsumed into the new Auto Settings Reduction feature.

Please take a look at these changes and try the latest test version here if you want to see any of them in action and join in the test discuss here too if you like. If you don't like anything you see, speak now before the changes get locked in for the next release version.

Summary of 0.4.4.8 Changes to Date:

This release brings significant improvements in automated performance optimization, FG detection, and memory management for MSFS 2024, along with refined user configuration options and overall responsiveness to performance fluctuations.

• Automatic Settings Reduction (MSFS 2024 Only):

  • Introduced an auto reduction feature that saves default settings at flight start and restores them on completion.
  • Activated only during a flight session with a passed secondary compatibility test.
  • Dynamically reduces settings (especially TLOD and OLOD) if FPS falls below the target, and restores them when performance improves.
  • Provides configurable options for reduction steps, floor, altitude-based recovery, and selection of settings suites to be reduced.

• FG Detection Enhancements:

  • Now reads FG (DLSS/FSR3) directly from the UsferCfg.opt file for greater reliability.
  • Supports real-time updates during flight and works with the latest MSFS 2024 SU2 Beta.
  • Detects and handles FSR3 FG and, for 5000 series GPUs, allows setting MFG with future auto-detection planned.

• TLOD Adjustments:

  • TLOD Min+: Updated logic for faster decreases under heavy performance drops, aligning with TLOD Base+ logic and using a settle timer.
  • TLOD Base+: Removed unnecessary full resets when climbing through Alt TLOD Top, and adjusted reduction scaling to ensure rapid response during FPS cap breaches.

• VRAM Protection:

  • Enhanced to trigger auto settings reduction when VRAM thresholds are exceeded.
  • Implements a recovery threshold (about 5% below the reduction threshold) to ensure recovery only under safe VRAM usage.
  • Applies maximum possible reduction during VRAM overflow and adjusts TLOD reduction/recovery rates accordingly.

• Cloud Quality Reduction:

  • Integrated into the overall auto settings reduction for MSFS 2024, and for MSFS 2020 with revised activation based on performance margins.

• Memory Management:

  • The memory offset search for MSFS 2024 now starts from the last known good offset and expands outward, speeding up detection after updates.
  • Connection status now visually indicates when a memory offset search is running.
  • Added a secondary compatibility test to disable settings reduction if needed.

• General Improvements:

  • Added sim rate detection displayed on the status line (except at normal 1X).
  • Incorporated command-line options to force IFR or VFR flight profiles.
  • Disabled AutoOLOD for MSFS 2024 to avoid conflicts with new auto reduction features.
  • Updated FSUIPC7 support with dedicated registry keys for both MSFS 2020 and 2024 versions.
  • Enhanced logging to reflect new features and the current MSFS version.
  • Upgraded the app to .NET 8.0.14.

 

Example of auto reduction settings inactive with proposed default settings:

Example of auto reduction settings fully activated with proposed default settings :

 

Hello

How do I get this setting? MFG 2x

 

Best Regards

Ramon

 

40 minutes ago, Metall4You said:

Hello

How do I get this setting? MFG 2x

 

Best Regards

Ramon

 

It will automatically show if you have a 5000 series GPU and not show otherwise.

Edited March 30, 20251 yr by Reset XPDR

Hello

Unfortunately not. I have an RTX 3090 with triple 4K screen. What settings should I use?

Thanks for the tip.

 

Ramon

31 minutes ago, Metall4You said:

Hello

Unfortunately not. I have an RTX 3090 with triple 4K screen. What settings should I use?

Thanks for the tip.

 

Ramon

Settings and expectations vary greatly among users. I suggest you read the readme here, start with non-expert mode and go from there.