Good night :)

10 hours ago, Reset XPDR said:

Try Man FG 4X, Manual Target FPS of 125 and adjust from there. That will give it some headroom below your 136 cap and should work fine.

I can confirm that using this same logic with the nexus mod gave me the best results. I lock my FPS in the sim to 30 and used the mod to get 2x to achieve 60 which works wonders. Using the logic above, I used Man FG 2x and a manual target of 58 and that worked very well.
I wanted to experiment with the mod's dynamic FG option enabled for the odd occasion where I can't achieve 30 FPS and when I did that, I changed the AutoFPS setting to DynFG and kept the target at 58. Things worked well but as soon as I clicked on another window and focus was lost from the sim window and then I refocused the sim's window, the FPS dropped to 15 as reported by AutoFPS FS Source and it was stuck there. The only way to go back to the native 30 FPS was by disabling the mod's dynamic FG. I went back to Man FG 2X and things were back to perfect.

Is this a problem with the mod or this due to a misconfigured setting in AutoFPS caused by me when switching to DynFG with the FPS value set to 58? I find the number 15 (30/2) intriguing and you will probably know right away what was happening.

Thanks.

Edited Wednesday at 08:06 PM2 days by xsever

Alrighty then. It's a new day so I'll have another go at answering the queries from yesterday. Firstly:

13 hours ago, f.skywalker said:

Thanks a lot for the great work.

What you’ve given us here is simply perfect.

I do have a question, though.

I uninstalled and reinstalled the app.

Now, unfortunately, the app no longer starts automatically with MSFS2024 or FSUIPC. Is there a trick to this?

I can't get it to work; I always have to start the app manually.

11 hours ago, f.skywalker said:

Thanks a lot for the help.

I’ve been using the app since it was first released.

I’m also very familiar with the update methods.

However, the auto-start feature unfortunately isn't working.

I’ve tried everything, but the app just won't start automatically.

It only works manually—which isn't a problem, strictly speaking—but I’d prefer auto-start.

There were no functional changes to auto-start functionality in the app installer in 0.5.2.0 (in fact since Feb this year), so it should still be working.

Just run the installer, select MSFS as the auto-start option, make sure MSFS 2024 is checked then click update. You should then see the following:

To confirm it has been added correctly, open your MSFS 2024 Exe.xml file in notepad and look for an MSFS_AutoFPS auto-start entry:

Start MSFS 2024 and it the app should auto-start about halfway through the loading process.

If this still isn't working, please tell me specifically where in these instructions it occurs.

11 hours ago, grandfred29 said:

Hello reset,

I don't find dynfg how to have it.

I ve tried the setting who are in one of your last screenshots but i can't find this seting :(

The readme FAQ covers this as follows:

How to use

• App defaults to last-used mode on startup.

• Auto-switches to detected mode on flight load (excludes Man FG, which is manually selected and locked).

• Target FPS dropdown allows editing inactive mode’s setting.

• Dropdown background turns orange when target FPS differs from current mode.

• VR-friendly: users can adjust target FPS in 2D before adorning and activating VR headset.

• Dynamic/adaptive FG of any type should be configured under Man FG.

Man FG (Manual FG)

• Allows future-proofing for externally set or unsupported FG types via manual tuning.

• Manual FG selection from 2X to 8X.

• Use DynFG for dynamic/adaptive FG setups:

  • Target FPS is set using the NFR (1×) value.

  • FPS displays as NFR because DynFG’s dynamic behaviour prevents reliable detection of its actual FG multiplier at any specific point in time.

  • Use MSFS, not RTSS, as the FPS source as it provides the NFR FPS required for this mode. 0.5.3.0 will force this behaviour.

• Functions as a forced mode, remaining active across app restarts until manually changed to a different graphics mode.

• Select Auto to return to auto detection of all other modes.

ie. Select this:

then this:

11 hours ago, AnkH said:

I started to use the Nexus Mod to enable 4x frame gen on my 4090 some months ago and I would never fly without anymore. But somehow I am gain at a total loss regarding the proper setup of AutoFPS for my IFR flights in regard of this. I have my FPS capped at 36 in the sim, I have dynamic settings turned on with the setting at 35FPS. No external limiter anymore. Do I use the auto mode for this setup? The current .dll from Nexus Mods limits the FPS after frame generation not to 144 (as you could guess when fixing them at 36, as 4x 36 equals 144), but at 136. Dont ask me why, according to a single reply on Nexus Mods it is normal if nVIDIA Reflex is used (which is on in my sim).

11 hours ago, Reset XPDR said:

Try Man FG 4X, Manual Target FPS of 125 and adjust from there. That will give it some headroom below your 136 cap and should work fine.

11 hours ago, AnkH said:

Doesnt matter if the number is not evenly dividable through 4? Or should I use 128 instead?

I'll revise my advice to say that it depends on whether your FPS cap of 36 is a Fixed or NTE FPS, as defined in the readme FAQ as follows:

What is a Fixed FPS vs an NTE FPS in reference to this app?

• A Fixed FPS is when your FPS is truly locked to one value with almost no variation (e.g., 72‑72‑72‑72‑72 across the detection windows).

  • In this case, use Fixed Target FPS and set it to match your lock.

  • The app will warn you if your settings don’t match a detected fixed FPS.

• An NTE FPS (“Not‑To‑Exceed FPS”) is when you have an FPS cap but your FPS still varies too much to be considered fixed.

  • In this case, do not use Fixed Target FPS.

  • Use Manual Target FPS and set the target slightly below the cap for stable TLOD behaviour.

• The app only classifies FPS as “Fixed” after five stable checks; one‑off dips are ignored.

If your FPS cap of 36 is Fixed, as defined above, then use Fixed Target Man 4X FG and try a target value of 136 (based on what you say the Nexus mod caps it to, not its real 144 potential).

If your FPS cap of 36 is NTE, as defined above, then use Manual Target Man 4X FG and try a target value at least 5% below 136. 128, as you have suggested, should be fine.

If you are still struggling with what to set, PM me the contents of the log file, located in %appdata%\MSFS_AutoFPS, of your best attempt and I will take a look.

11 hours ago, kevinfirth said:

My app has updated to 0.5.2.0

However, I seem to have lost the threshold setting for spike detection? Was that removed please?

Yes it was removed from the UI as I received no feedback during the test program that anyone had tried changing that value so IMO it was not worth it taking up UI real estate. It can still be changed in the common config file per the readme description of this new feature:

Periodic Spike Detection/Protection:

• Detection is auto enabled in Expert mode, requiring detection of the shared RTSS frame time buffer to activate.

• ...

• A "SpikeThresholdMultiplier" common config file option, defaulting to 2.0, determines the multiple of the frame time median at which a spike will be counted.

1 hour ago, xsever said:

I can confirm that using this same logic with the nexus mod gave me the best results. I lock my FPS in the sim to 30 and used the mod to get 2x to achieve 60 which works wonders. Using the logic above, I used Man FG 2x and a manual target of 58 and that worked very well.
I wanted to experiment with the mod's dynamic FG option enabled for the odd occasion where I can't achieve 30 FPS and when I did that, I changed the AutoFPS setting to DynFG and kept the target at 58. Things worked well but as soon as I clicked on another window and focus was lost from the sim window and then I refocused the sim's window, the FPS dropped to 15 as reported by AutoFPS FS Source and it was stuck there. The only way to go back to the native 30 FPS was by disabling the mod's dynamic FG. I went back to Man FG 2X and things were back to perfect.

Is this a problem with the mod or this due to a misconfigured setting in AutoFPS caused by me when switching to DynFG with the FPS value set to 58? I find the number 15 (30/2) intriguing and you will probably know right away what was happening.

Thanks.

Per the readme excerpt I posted a few posts ago, when using DynFG, everything in the app is in NFR-speak so your target FPS should have been set to 29 FPS (Actually, if you are using a true Fixed 30 FPS cap, then you should be using Fixed and the target set to 30 per my last post).

Regardless, the mod you are using could be the one capping your FPS to 30 if that is what you have set for its target in the mod, which would explain the 15 FPS NFR the app is showing. I believe that with the mod you should be setting your desired post-FG FPS ie 60, not the NFR FPS AutoFPS requires, so I suggest you try that.

I know that it can be a bit confusing with all this NFR and post-FG speak, but the general rule is as follows:

• MSFS Settings - all NFR-speak.

• MSFS_AutoFPS - all post-FG speak, EXCEPT DynSet which is NFR-speak.

• Dynamic/Adaptive FG driver/mod settings - target FPS post-FG speak.

Edited Wednesday at 09:58 PM2 days by Reset XPDR

2 minutes ago, Reset XPDR said:

Regardless, the mod you are using could be the one capping your FPS to 30 if that is what you have set for its target in the mod, which would explain the 15 FPS NFR the app is showing. I believe that with the mod you should be setting your desired post-FG FPS ie 60, not the NFR FPS AutoFPS requires, so I suggest you try that.

Thank you for the timely feedback. The target set in the mod is 60 while the target set in the sim is 30. Man FG X2 and FPS=58 worked wonders so the FPS value definitely needs to be the post-FG value. Regard the weird 15 FPS, @AnkH suggested I turn on two settings inside the mod which I will do tomorrow and revert back. Since him and I are using this mod, maybe we can help you address it in the readme as it is getting more popular amongst simmers with 3000- and 4000-series cards.

6 minutes ago, xsever said:

Thank you for the timely feedback. The target set in the mod is 60 while the target set in the sim is 30. Man FG X2 and FPS=58 worked wonders so the FPS value definitely needs to be the post-FG value. Regard the weird 15 FPS, @AnkH suggested I turn on two settings inside the mod which I will do tomorrow and revert back. Since him and I are using this mod, maybe we can help you address it in the readme as it is getting more popular amongst simmers with 3000- and 4000-series cards.

That would be helpful. I have the mod, but just haven't used it as I am quite happy with plain old FSR3 2X. I will give it a go now to see what I find too.

Edited Wednesday at 10:08 PM2 days by Reset XPDR

40 minutes ago, Reset XPDR said:

That would be helpful. I have the mod, but just haven't used it as I am quite happy with plain old FSR3 2X. I will give it a go now to see what I find too.

@xsever , unfortunately MSFS CTDs as soon as I enable any form of FG with the Nexus mod running, so I am currently unable to assess this. Nonetheless, the underlying principle of using an NFR base for DynFG-related Target and displayed FPS in MSFS_AutoFPS should be sound as that is the lowest common denominator of any form of FG. Let me know what you discover with Nexus mod settings relating to this feature.

7 hours ago, Reset XPDR said:

Yes it was removed from the UI as I received no feedback during the test program that anyone had tried changing that value so IMO it was not worth it taking up UI real estate. It can still be changed in the common config file per the readme description of this new feature:

I'm sorry, I did try it and found it very useful, but stressful family situation meant I had little time to make any meaningful reports back. To your absolute credit you responded to issues and issued new versions faster than I was able to look at them sadly 🙁 perhaps it could be made as a hide/showable option in the future pls?

Edited yesterday at 05:04 AM1 day by kevinfirth

41 minutes ago, kevinfirth said:

I'm sorry, I did try it and found it very useful, but stressful family situation meant I had little time to make any meaningful reports back. To your absolute credit you responded to issues and issued new versions faster than I was able to look at them sadly 🙁 perhaps it could be made as a hide/showable option in the future pls?

I will do that, since I have made it so that the spike protection checkbox only ever appears if you have RTSS running anyway and could do the same for the hide-able stack panel upon which it would live, so users not using RTSS would not see it anyway. It will make it reappear in the first 0.4.3.0 test build.

Edited yesterday at 07:46 AM1 day by Reset XPDR

10 hours ago, Reset XPDR said:

Regardless, the mod you are using could be the one capping your FPS to 30 if that is what you have set for its target in the mod, which would explain the 15 FPS NFR the app is showing. I believe that with the mod you should be setting your desired post-FG FPS ie 60, not the NFR FPS AutoFPS requires, so I suggest you try that.

I did more testing about this and I think there's something wrong with dynamic FG in the mod because it's the only constant that is resulting in the "15 FPS" bug. As soon as I disable dynamic FG, the FPS gradually recover to 30 FPS in an almost time linear way: 15 18 20 ..... 30 30. I even tried Manual instead of Fixed and set the FPS target to 57 (0.95 x 60) and the bug still occurred when focus was lost and regained. I went back to Manual FG X2 and 57 and everything worked fine. TLDR: This is not an issue with AutoFPS but with the mod itself I believe.

9 hours ago, Reset XPDR said:

@xsever , unfortunately MSFS CTDs as soon as I enable any form of FG with the Nexus mod running, so I am currently unable to assess this. Nonetheless, the underlying principle of using an NFR base for DynFG-related Target and displayed FPS in MSFS_AutoFPS should be sound as that is the lowest common denominator of any form of FG. Let me know what you discover with Nexus mod settings relating to this feature.

What I discovered reminded me why I didn't use this mod in the past: as soon as you pop out a display from the cockpit, the mod crashes and crashes the sim with it. Could this be your problem as well?
I read that this was a limitation of the mod in April 2026 but I had hoped that this was resolved by now. I am now at a crossroads: 1) Nexus mod and no popped-out displays on my two additional monitors or 2) no nexus mod and stick with Lossless Scaling but benefit from popped-out displays. I'm gonna have to do some testing to see which path I can live with more.

13 hours ago, Reset XPDR said:

Alrighty then. It's a new day so I'll have another go at answering the queries from yesterday. Firstly:

There were no functional changes to auto-start functionality in the app installer in 0.5.2.0 (in fact since Feb this year), so it should still be working.

Just run the installer, select MSFS as the auto-start option, make sure MSFS 2024 is checked then click update. You should then see the following:

To confirm it has been added correctly, open your MSFS 2024 Exe.xml file in notepad and look for an MSFS_AutoFPS auto-start entry:

Start MSFS 2024 and it the app should auto-start about halfway through the loading process.

If this still isn't working, please tell me specifically where in these instructions it occurs.

I found the problem.

After reinstalling the app, I had installed it with administrator privileges.

Now I’ve installed it without admin rights, and everything is working as it should. I had forgotten to install it without admin rights during the reinstallation.

Thanks for help

Frank from EDDM

3 hours ago, xsever said:

I did more testing about this and I think there's something wrong with dynamic FG in the mod because it's the only constant that is resulting in the "15 FPS" bug. As soon as I disable dynamic FG, the FPS gradually recover to 30 FPS in an almost time linear way: 15 18 20 ..... 30 30. I even tried Manual instead of Fixed and set the FPS target to 57 (0.95 x 60) and the bug still occurred when focus was lost and regained. I went back to Manual FG X2 and 57 and everything worked fine. TLDR: This is not an issue with AutoFPS but with the mod itself I believe.

What I discovered reminded me why I didn't use this mod in the past: as soon as you pop out a display from the cockpit, the mod crashes and crashes the sim with it. Could this be your problem as well?
I read that this was a limitation of the mod in April 2026 but I had hoped that this was resolved by now. I am now at a crossroads: 1) Nexus mod and no popped-out displays on my two additional monitors or 2) no nexus mod and stick with Lossless Scaling but benefit from popped-out displays. I'm gonna have to do some testing to see which path I can live with more.

No popped out displays on mine. It used to CTD in the past when I had RTSS running, but even with that turned off it still CTDs. Apart from testing with my app on the rare occasions it doesn't cause an MSFS CTD, I rarely use FG of any form as I mainly fly in VR where it is not applicable anyway, so no big deal.