1 hour ago, Keirtt said:

@Reset XPDR I'm loving AutoFPS but I do have a quick question. One thing I've noticed is occasionally I'll see my fps in AutoFPS showing 150+ fps at times which is incorrect since I have my fps locked at 115. I went to go turn on debug to see the in game fps and as soon as I did that, AutoFPS began reflecting the correct FPS and never went beyond the 115 cap. Any ideas why this is happening? Thanks!

AutoFPS reports the raw FPS that MSFS publishes via SimConnect, then scales it up depending what graphics mode it detects you are running or have manually configured. It shouldn't make any difference whether the in-game FPS view is showing or not. PM me the contents of a log file, located in %appdata%\MSFS_AutoFPS\log, where you are seeing this 150+ FPS and I'll see if anything looks out of place.

Edited April 1Apr 1 by Reset XPDR

12 hours ago, Reset XPDR said:

AutoFPS reports the raw FPS that MSFS publishes via SimConnect, then scales it up depending what graphics mode it detects you are running or have manually configured. It shouldn't make any difference whether the in-game FPS view is showing or not. PM me the contents of a log file, located in %appdata%\MSFS_AutoFPS\log, where you are seeing this 150+ FPS and I'll see if anything looks out of place.

Thanks for the reply and sorry for my delayed response. Currently doing a long haul, but still seeing some of the same behavior. Below I've attached two screenshots. You'll see in the first screenshot, AutoFPS is showing 138FPS, which I could tell it definitely wasn't because panning around wasn't totally smooth. In the second picture, I enable the developer mode and turn on FPS, and you see AutoFPS reverts back to the correct FPS. Also, it became noticeably smoother again. Not sure what's up but I appreciate all your help and this great product!

 

2 hours ago, Keirtt said:

Thanks for the reply and sorry for my delayed response. Currently doing a long haul, but still seeing some of the same behavior. Below I've attached two screenshots. You'll see in the first screenshot, AutoFPS is showing 138FPS, which I could tell it definitely wasn't because panning around wasn't totally smooth. In the second picture, I enable the developer mode and turn on FPS, and you see AutoFPS reverts back to the correct FPS. Also, it became noticeably smoother again. Not sure what's up but I appreciate all your help and this great product!

 

Thanks, but I'm still going to need to see the associated log file to tell more about what is going on. Also, exactly how are you capping your FPS to 115? Where and to what specific value are you setting this? And what type of FG are you using and is it configured in MSFS or elsewhere?

Edited April 1Apr 1 by Reset XPDR

Hello, 

i've a question regarding the MSFS performance option: Can I leave the default values with a 5800X3D or do I have to set a specific core affinity in the configuration file? A read something about this topic but I couldn't figure out under which conditions it is necessary to edit the config file. 

8 hours ago, skylane182 said:

Hello, 

i've a question regarding the MSFS performance option: Can I leave the default values with a 5800X3D or do I have to set a specific core affinity in the configuration file? A read something about this topic but I couldn't figure out under which conditions it is necessary to edit the config file. 

The default values should be fine for a 5800X3D, which will choose every even (ie. physical) core for MSFS, so 8 cores total for your CPU which is plenty. If you are not on 0.4.6.7-RC, I suggest you update to that as you can individually select which MSFS performance options you want from the UI, without having to go into the config file, and will tell you what core configuration it has chosen in the Physical Cores tooltip. eg.

You can get the latest 0.4.6.7-RC from here or just enable + Test for updates when the app first starts up and you can just auto update to it.

 

Edited April 2Apr 2 by Reset XPDR

When I try and launch MSFS auto FPS I get an error in 2024, why is this?

I also use 2020, is there something else I need to put into 2024 for it to work?

42 minutes ago, Danthepilot77 said:

When I try and launch MSFS auto FPS I get an error in 2024, why is this?

I also use 2020, is there something else I need to put into 2024 for it to work?

What specific error? In AutoFPS or MSFS 2024 itself? As long as you are on the latest AutoFPS version, 0.4.6.6 available here, nothing specific is required for the app to work in either MSFS 2020 or 2024, including the latest 2024 SU5 beta.

If you are on this latest app version and it is still not working, PM me the contents of your latest log file, located in %appdata%\MSFS_AutoFPS\log, where this happens and I will take a look.

Edited April 3Apr 3 by Reset XPDR

18 hours ago, Reset XPDR said:

The default values should be fine for a 5800X3D, which will choose every even (ie. physical) core for MSFS, so 8 cores total for your CPU which is plenty. If you are not on 0.4.6.7-RC, I suggest you update to that as you can individually select which MSFS performance options you want from the UI, without having to go into the config file, and will tell you what core configuration it has chosen in the Physical Cores tooltip. eg.

Thank you for your reply, as always very kind and helpful 🙂

I tried it on two flights without changing anything (so using the defaul values) and couldn't determine any significant difference between the performance option on or off. Maybe it's because my system does already run on optimum power settings so only the core affinity and process priority would be affected and I assume the impact is to small to notice on my system. I hoped I would help with microstutters, I'll try increasing my minimum framerate next. 

13 hours ago, skylane182 said:

Thank you for your reply, as always very kind and helpful 🙂

I tried it on two flights without changing anything (so using the defaul values) and couldn't determine any significant difference between the performance option on or off. Maybe it's because my system does already run on optimum power settings so only the core affinity and process priority would be affected and I assume the impact is to small to notice on my system. I hoped I would help with microstutters, I'll try increasing my minimum framerate next. 

Some users say they get better results with it enabled, some say without and most say it makes no difference. The good thing is that it is easy to enable/disable, so IMO its worth a shot on the off chance you are in the better results group, like I am.

Is there any advice / best practice on using AutoFPS with the new DLSS Dynamic MutiFrame Gen. I cap at 35 NFR and use AutoFPS in auto fps mode and it seems fine.

Installed the latest test version today and even though I have a 7800X3D I was curious about the priority setting and the power plan adjustment, but noticed in the logs and whilst in the sim on the first attempt that the power plan did not change dynamically, but managed to find a workaround and what was causing it. I am running the norwegian version of Windows and AutoFPS was looking for "high performance" or "ultra performance" specifically, but mine is named "Optimal Ytelse" in norwegian. I figured out how to change the power plan name using cmd or powershell and ran the command powercfg -changename 1eacde4f-8de7-4761-bb8f-1c2249ce4e31 "Ultimate Performance". That did the trick, but the GUIDs for the power plans does not change from language to language so my suggestion would be that AutoFPS instead looks for these two GUIDs: 1eacde4f-8de7-4761-bb8f-1c2249ce4e31 (Ultimate Performance GUID) and 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High Performance GUID). GUIDs can be verified by first running the command powercfg /L that lists the power plans available. 

4 hours ago, Benjamin H said:

Installed the latest test version today and even though I have a 7800X3D I was curious about the priority setting and the power plan adjustment, but noticed in the logs and whilst in the sim on the first attempt that the power plan did not change dynamically, but managed to find a workaround and what was causing it. I am running the norwegian version of Windows and AutoFPS was looking for "high performance" or "ultra performance" specifically, but mine is named "Optimal Ytelse" in norwegian. I figured out how to change the power plan name using cmd or powershell and ran the command powercfg -changename 1eacde4f-8de7-4761-bb8f-1c2249ce4e31 "Ultimate Performance". That did the trick, but the GUIDs for the power plans does not change from language to language so my suggestion would be that AutoFPS instead looks for these two GUIDs: 1eacde4f-8de7-4761-bb8f-1c2249ce4e31 (Ultimate Performance GUID) and 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High Performance GUID). GUIDs can be verified by first running the command powercfg /L that lists the power plans available. 

You are correct that the GUID for High Performance (and Balanced and Power Saver for that fact) do not change with different languages, but Ultimate Performance always gets a unique GUID as when created it is duplicated from a template that does not give you the same GUID as the template.

As such, I will change the app in the next test release I will put out shortly to use GUIDs instead of names to select High Performance and Balanced. However, unless you have a practical solution otherwise that can deal with different language names for Ultimate Performance, I will not be able to do the same for Ultimate Performance, so you will need to work around that as you already have done. BTW, I did consider having the app create a temporary Ultimate Performance profile while it is running but that requires elevation of the app to admin privelidges, which I do not want users to have to do.

 

powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61 powercfg -changename <new-guid> "My Custom Name"

 

10 hours ago, GraDe said:

Is there any advice / best practice on using AutoFPS with the new DLSS Dynamic MutiFrame Gen. I cap at 35 NFR and use AutoFPS in auto fps mode and it seems fine.

I was wondering when this question would come up and we have been here before with Lossless Scaling Adaptive Scaling. The issue with any type of dynamic frame generation is that the multiplier constantly varies and is not actually detectable, so the only practical solution is to use NFR as you have been doing. 

@Benjamin H, as promised, 0.4.6.7-RC10 or later, available here, has the following change of relevance to your suggestion earlier:

- Changed best power plan selection in MSFS Performance Optimiser to detect High Performance and Balanced plans by GUID instead of language‑dependent names, improving reliability across all system locales.

As previously mentioned, Ultimate Performance could not be included as its GUID is different for everyone, but renaming such a profile to "Ultimate Performance" as you already have done will still work.

MSFS_AutoFPS v0.4.6.7 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase.

This release introduces new MSFS Performance Optimiser controls for physical cores, process priority, and power‑plan management in Expert Mode, adds a Start Max option for TLOD Extra, refines FPS Cap mode, and enhances Test Mode performance monitoring while delivering targeted stability, logging, and usability improvements across the app.