2 hours ago, Rumpelzuck said:

the current Test Version 4.4.8-test18 (older ones too I guess)  doesn't recognize the usage of FrameGeneration in the new MSFS 2024 SU2 beta 1.4.7 any more.  Neither using the current Nvidia 310.1.0.0  DLSS 4 version nor the AMD FSR3 version which came with the new beta. Always detects that the sim is running without FG. Scannnig the FPS without using FG works fine.

Using the newest Nvidia FG Version 310.2.x per Nvidia Profile Inspector works in the sim, but AutoFPS doesn't detect the FG Mode neither.

I'm using 50% lower target FPS in AutoFPS as a workaround now.

Thanks for the heads up. I will take a look at it today and hopefully put out a test version with a fix shortly.

Edit: Fixed in 0.4.4.8-test19, available here.

Changes are:
- Updated FG detection to work with the MSFS 2024 SU2 Beta.
  - FSR3 FG is now detected, however a base target FPS must be used as the FG multiplier is variable for this type of FG.
  - MFG for 5000 series GPUs now looks to be settable in the MSFS 2024 SU2 Beta. The app will be updated in a future test version to support auto-detection of this FG type.

 

Edited March 25, 20251 yr by Reset XPDR

Just installed SU2

With MSFS in focus, and AutoFPS on top.  I am seeing the in sim fps counter showing at 60fps.   AutoFPS (test20) is showing FG active, with an fps of 120.

With MSFS not in focus, I am seeing the in sim fps counter AND AutoFPS showing 60fps, with FG showing as inactive/

 

My Rivatuner overlay is also only showing 60fps, in both cases.

It seems to me like SU2 has introduced support for 5000 series multi frame generation but broken framegen for older pre-4000 series GPUs?

 

Edited March 26, 20251 yr by kevinfirth

9 minutes ago, kevinfirth said:

Just installed SU2

With MSFS in focus, and AutoFPS on top.  I am seeing the in sim fps counter showing at 60fps.   AutoFPS (test20) is showing FG active, with an fps of 120.

With MSFS not in focus, I am seeing the in sim fps counter AND AutoFPS showing 60fps, with FG showing as inactive/

 

My Rivatuner overlay is also only showing 60fps, in both cases.

It seems to me like SU2 has introduced support for 5000 series multi frame generation but broken framegen for older pre-4000 series GPUs?

<a href="https://ibb.co/svYt9bqW"><img src="https://i.ibb.co/TB3rMYtW/Screenshot-2025-03-26-103058.png" alt="Screenshot-2025-03-26-103058" border="0"></a>

 

NVidia and FSR3 flavours of FG worked fine in SU2 on a 4090 when I tested them this earlier today, with both showing me double the FPS with CapFrameX when FG was active, so I am not sure why your FG isn't working.

4 minutes ago, Reset XPDR said:

NVidia and FSR3 flavours of FG worked fine in SU2 on a 4090 when I tested them this earlier today, with both showing me double the FPS with CapFrameX when FG was active, so I am not sure why your FG isn't working.

Im running a 3090.  My hypothesis is in implementing multi FG for newer self immolating and unavailable cards, they've broken FG for older cards using the FG mod.

BTW, this is the same FG mod that worked fine in release version and SU1.

Edited March 26, 20251 yr by kevinfirth

7 minutes ago, kevinfirth said:

Im running a 3090.  My hypothesis is in implementing multi FG for newer self immolating and unavailable cards, they've broken FG for older cards using the FG mod.

BTW, this is the same FG mod that worked fine in release version and SU1.

Losing in-game FG is no great loss IMO as I prefer lossless scaling quality-wise over native nVidia FG anyway. If you haven't tried lossless scaling I suggest you give it a go.

Alternatively, the FG mod dev may eventually do an update with a fix for this, but obviously you'd have to wait for that.

Edited March 26, 20251 yr by Reset XPDR

7 minutes ago, Reset XPDR said:

Losing in-game FG is no great loss IMO as I prefer lossless scaling quality-wise over native nVidia FG anyway. If you haven't tried lossless scaling I suggest you give it a go.

Alternatively, the FG mod dev may eventually do an update with a fix for this, but obviously you'd have to wait for that.

No I havent tried LS, didnt want to introduce more complexity to a system that was running just fine with the framegen mod.  (which incidentally, I love for the extra smoothness and performance headroom it gives me, but nthats just my personal preference!)

 

As for AutoFPS not matching what you are seeing in game, the logic it uses is pretty simple in that if FG is found on in MSFS settings it just doubles whatever FPS MSFS is feeding it.

In a way I wish I had never had the app try to show actual FG FPS. It was simple when it first came out, with native nVidia FG only, but then the FG mod, lossless scaling FG (in 1, 2 and 3 version flavours, each different), FSR3 adaptive FG, MFG, and now lossless scaling adaptive FG have all come out, with different detection intricacies for each. It is turning into a maintainability nightmare!

If it gets any worse, I may end up just reverting to the original base FPS for everything, which most other apps do anyway, and be done with the FG detection business. I think it's something most users would get over pretty quickly because when these things break, as they regularly seem to do because of changes on their end, users fairly quickly work out that using base FPS works just as well.

Edited March 26, 20251 yr by Reset XPDR

is ok, this SU2 is unuseable so going back to SU1 anyway 🙂  Cheers

Surprisingly, the latest app works just fine with SU Beta 2. Just saying. No problem at all

17 minutes ago, History said:

Surprisingly, the latest app works just fine with SU Beta 2. Just saying. No problem at all

Latest as in 0.4.4.7 formal release from 3 weeks ago or 0.4.4.8-test20 released today?

22 minutes ago, Reset XPDR said:

Latest as in 0.4.4.7 formal release from 3 weeks ago or 0.4.4.8-test20 released today?

I have left my computer now but I remember there's a green sentence saying "the last app installed" or such

Edited March 26, 20251 yr by History

I know it's a dumb question, and you explained it many times, but im not sure I understood it.

Using FSR3 and FG x2 in SU2, if i set up for example 40 fps in AutoFPS app, it means the sim runs at 80fps? (40 multiplied X2 from framegen). Or the sim runs at 40 (20 mulplied x2 by FG)?

 

As always, thanks for your great work!

 

6 hours ago, ConairMSFS said:

I know it's a dumb question, and you explained it many times, but im not sure I understood it.

Using FSR3 and FG x2 in SU2, if i set up for example 40 fps in AutoFPS app, it means the sim runs at 80fps? (40 multiplied X2 from framegen). Or the sim runs at 40 (20 mulplied x2 by FG)?

 

As always, thanks for your great work!

 

The FSR3 support I added to the latest test version of the app yesterday uses a base FPS for the target as, from what my research uncovered, the multiplier can vary with this FG method hence it is meaningless to pick an FPS based on a specific multiplier. As such, with FSR3 set your target FPS to whatever FPS you aim to get in MSFS without any FG active.

Edited March 26, 20251 yr by Reset XPDR

Since today's MSFS 2020 update, I've had the following problem with the Auto FPS app.
I use FrameGen. Unfortunately, it no longer works with the Auto FPS app. FrameGen is simply no longer displayed or executed. However, with the same version, it works with MSFS 2024 without any problems. Today's 2020 update has messed things up. MSFS Adaptive LOD works with Frame Gen and MSFS 2020 without any problems.

To summarize:

2020 with Auto FPS app (last test version) with Frame Gen doesn't work. It's not displayed in the app.

2024 with Auto FPS app (last test version) with Frame Gen works
it is displayed in the app.

Adaptive LOD in the latest version works with 2020 and 2024.

Today, I only updated MSFS 2020 and the INI A350 version 1.0.6.

I never had any problems before the update.

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.