5 minutes ago, Rob G said:

Suddenly, when I open AutoFPS, I see the icon display in the task bar, then it suddenly closes. The sim is up. I have never had this problem before.

Can you help me with this?

What app version? What is the last line in the latest log file, located in %appdata%\MSFS_AutoFPS\log, before it closes and do if lines contain the word "exception" post those?

Does Windows Event Viewer show any app crash details? To check, open Event Viewer, on the tree on the left expand out to Even Viewer (Local) -> Windows Logs ->Application, under actions on the right click Find and search for "AutoFPS" and paste the details of any errors that occur into a PM and send that to me.

4 hours ago, vortac said:

Hello. 

I also want to share my experiences with current latest beta (.11). I have MSFS2024 beta version 1.7.21. 

I set it up with FPS sensitivity, fixed FG with free mode (TLOD between 70-150). 

I had one of my stutter free flight. It was really nice experience to see the difference between my previous setup, FPS Cap. 

I still had some stutters, especially when panning,but this is well known and reported issue with MSFS. 

I would recommend everyone to try FPS sensitivity with free mode. 

I want to say big thank you to Reset XPDR to create that super tool and keep developing it. 

 

Thanks for the feedback. I have been running FreeTLOD mode in most of my MSFS 2024 VFR flights and IMO it is really good too, giving me higher TLOD than ever before with negligible stuttering because of it. As you suggest, this is something users should try as the results, in MSFS 2024 in particular, are very pleasing.

2 hours ago, AlexMD11 said:

Question on settings, I am running FPS lock of 40 internally and then apply 3x FG. I have tried to select “NFR” to 40 fps so that autofps looks to optimise against the base FPS (as that’s the one I try to keep stable), but the NFR box turns yellow an keep resetting to FG (for which I assume I can’t use 40 fps to optimise against). What’s the recommended setting for this case?
Would like to try the free setting but never been able to have smooth panning at TLOD > 100 on the ground with Tobii head tracking despite top end system.. 

Why are you trying to set and select NFR when you are using FG? Just set the FG, which the app is auto-detecting you are using, FPS to 120 (3X your FPS lock). 

Re trying the free setting, yes it may not be effective in situations such as yours, and that is why it is optional, but in remote/VFR areas it may still be worthwhile to try.

A quick update on 0.4.5.8-test progress, which is starting to finalise for formal release. A few more changes of note:

Firstly, based mainly on my, and one other dedicated tester over at github, testing, and in the absence of any feedback to the contrary, the new Fixed Target FPS in FPS Sensitivity mode is going so well that I am planning to phase out FPS Cap mode in a near future app release. In order to ease the transition, 0.4.6.8 will one-off (per profile) detect if you are currently using FPS Cap for your active flight type profile and offer to auto transition you to using Fixed Target FPS in FPS Sensitivity mode.

If you choose yes, it will auto switch your settings to be equivalent for the new mode. If you choose no, you can keep using FPS Cap mode for now, but be aware this will likely be compulsory in a future app version and you will simply be advised of the auto transition outcome. Again, this is because I have nothing to indicate this is a bad idea and the removal of FPS Cap mode will significantly simplify my code base while actually improving the experience of those who had previously used FPS Cap mode. 

Secondly, after experiencing many support requests where users are using an FPS cap and have configured the app incorrectly, resulting in poor or no TLOD automation, I have decided to make the app more forceful in auto resolving the issue for you.  The app will now quietly attempt to detect a system-set FPS cap in the background and if it detects exactly the same FPS cap 5 times in a row (ie. it will really make sure it is not a one-off false detection) and your AutoFPS settings are not set correctly for it, it will now auto correct them for you. This action is consistent with other app settings where if it detects an unworkable settings combination it will auto change the offending setting for you. 

Finally, in implementing the aforementioned forced detected FPS cap settings changes if configured incorrectly, I have realised that there are some instances where fractional FPS caps can be set, namely in VR where the headset refresh rate is an odd number and the pre-motion reprojection FPS lock is half of that, giving a fractional FPS cap. eg. The BigScreenBeyond offers a 75 Hz refresh, which is a 37.5 FPS lock pre-motion reprojection.

Prior to the latest test version, target FPS could only ever be an integer (ie. no decimal places), whereas now it has been changed to allow fractional values of 0.5 only. You can attempt to set any fractional value you want, but when saved it will snap to the nearest integer or 0.5 value. eg. if you set 37.6 it will snap to 37.5, 40 will remain 40 etc.

This change has been done primarly to allow the app to auto set the correct detected fractional target FPS for these VR edge-cases, otherwise it would previously have rounded up or down to the nearest integer, which would not be optimal for TLOD automation. 

As you can see, some fairly notable changes are on the horizon that could potentially negatively affect users in ways I have not yet encountered in my own testing, so if you are one of them please speak up before I lock them in for the final release. The latest 0.4.6.8-test version can be obtained by either enabling the + Tests option with the Silent or Prompted Updates option via the app or download and manually install from here.

Edited April 19Apr 19 by Reset XPDR

2 hours ago, Reset XPDR said:

What app version? What is the last line in the latest log file, located in %appdata%\MSFS_AutoFPS\log, before it closes and do if lines contain the word "exception" post those?

Does Windows Event Viewer show any app crash details? To check, open Event Viewer, on the tree on the left expand out to Even Viewer (Local) -> Windows Logs ->Application, under actions on the right click Find and search for "AutoFPS" and paste the details of any errors that occur into a PM and send that to me.

After reinstalling the app it now stays open. However, I am seeing some things I don't understand. Under General, I am set to Fixed. In Expert Settings I am trying FPS Sensitivity, with Free mode. However, at the top, when I try to change the target framerate for NFR or VR, it won't let me. I type a number and hit enter it goes back to the number it already had. I don't understand why I can't change the framerate field. In the sim I have max framerate set to 35, Dynamic Settings set to 35. Currently AutoFPS has 40 displayed for both NFR and VR and I can't change it to 35 to match the sim.

What's going on here? I am really confused.

Here are answers to your questions. I am using 0.4.6.8-test11. Not sure about last line in log because it's opening correctly now. In the Event Viewer, there are two kinds of errors that occur in pairs for each time it was happening.

Here is from the first error:

Faulting application name: MSFS_AutoFPS.exe, version: 0.4.5.0, time stamp: 0x69bc0000
Faulting module name: KERNELBASE.dll, version: 10.0.26100.8246, time stamp: 0x208e0cb7
Exception code: 0xe0434352
Fault offset: 0x00000000000c79da
Faulting process id: 0x145C
Faulting application start time: 0x1DCD047825B2194
Faulting application path: C:\Users\rgold\AppData\Roaming\MSFS_AutoFPS\bin\MSFS_AutoFPS.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 8c23a653-167f-492b-8763-c5c75d2b4b0b
Faulting package full name: 
Faulting package-relative application ID: 

 

Here is from the second error:

Application: MSFS_AutoFPS.exe
CoreCLR Version: 8.0.2626.16921
.NET Version: 8.0.26
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException: '-2147483648' is not a valid value for property 'SelectedIndex'.
   at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
   at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
   at MSFS_AutoFPS.MainWindow.LoadSettings(Boolean noLogging) in C:\Users\feb29\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\MainWindow.xaml.cs:line 1318
   at MSFS_AutoFPS.MainWindow..ctor(NotifyIconViewModel notifyModel, ServiceModel serviceModel) in C:\Users\feb29\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\MainWindow.xaml.cs:line 208
   at MSFS_AutoFPS.App.OnStartup(StartupEventArgs e) in C:\Users\feb29\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\App.xaml.cs:line 156
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at MSFS_AutoFPS.App.Main()
 

As I said, it is staying open after reinstall. So right now I need to understand why I can't seem to change target framerates.

 

13 minutes ago, Rob G said:

After reinstalling the app it now stays open. However, I am seeing some things I don't understand. Under General, I am set to Fixed. In Expert Settings I am trying FPS Sensitivity, with Free mode. However, at the top, when I try to change the target framerate for NFR or VR, it won't let me. I type a number and hit enter it goes back to the number it already had. I don't understand why I can't change the framerate field. In the sim I have max framerate set to 35, Dynamic Settings set to 35. Currently AutoFPS has 40 displayed for both NFR and VR and I can't change it to 35 to match the sim.

What's going on here? I am really confused.

Here are answers to your questions. I am using 0.4.6.8-test11. Not sure about last line in log because it's opening correctly now. In the Event Viewer, there are two kinds of errors that occur in pairs for each time it was happening.

Here is from the first error:

Faulting application name: MSFS_AutoFPS.exe, version: 0.4.5.0, time stamp: 0x69bc0000
Faulting module name: KERNELBASE.dll, version: 10.0.26100.8246, time stamp: 0x208e0cb7
Exception code: 0xe0434352
Fault offset: 0x00000000000c79da
Faulting process id: 0x145C
Faulting application start time: 0x1DCD047825B2194
Faulting application path: C:\Users\rgold\AppData\Roaming\MSFS_AutoFPS\bin\MSFS_AutoFPS.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 8c23a653-167f-492b-8763-c5c75d2b4b0b
Faulting package full name: 
Faulting package-relative application ID: 

 

Here is from the second error:

Application: MSFS_AutoFPS.exe
CoreCLR Version: 8.0.2626.16921
.NET Version: 8.0.26
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException: '-2147483648' is not a valid value for property 'SelectedIndex'.
   at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
   at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
   at MSFS_AutoFPS.MainWindow.LoadSettings(Boolean noLogging) in C:\Users\feb29\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\MainWindow.xaml.cs:line 1318
   at MSFS_AutoFPS.MainWindow..ctor(NotifyIconViewModel notifyModel, ServiceModel serviceModel) in C:\Users\feb29\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\MainWindow.xaml.cs:line 208
   at MSFS_AutoFPS.App.OnStartup(StartupEventArgs e) in C:\Users\feb29\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\App.xaml.cs:line 156
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at MSFS_AutoFPS.App.Main()
 

As I said, it is staying open after reinstall. So right now I need to understand why I can't seem to change target framerates.

 

Thanks for getting back with the info I requested.

Re the app crash, it looks like the app encountered a dodgy value when setting an initial index for one of the UI controls. Even though it is fixed now, I will look into what caused it to produce that wall of text of an exception message! 

Re target FPS not setting, I just checked on mine and it does change with the base settings you mention, but it could be something with your specific other settings. Can I get you to go to %appdata%\MSFS_AutoFPS, open the MSFS2024_AutoFPS.config file in a text editor and copy and paste all text in a PM to me (so as not to clutter up this thread with a long settings list) and I will use it to set mine up the same and try to reproduce.

Edit: Also, if you could send me the content of your latest log, file location as previously advised, in a PM it will help see what is happening when you try to change target FPS and it does not stick. Thanks.

Edited April 20Apr 20 by Reset XPDR

10 minutes ago, Reset XPDR said:

Thanks for getting back with the info I requested.

Re the app crash, it looks like the app encountered a dodgy value when setting an initial index for one of the UI controls. Even though it is fixed now, I will look into what caused it to produce that wall of text of an exception message! 

Re target FPS not setting, I just checked on mine and it does change with the base settings you mention, but it could be something with your specific other settings. Can I get you to go to %appdata%\MSFS_AutoFPS, open the MSFS2024_AutoFPS.config file in a text editor and copy and paste all text in a PM to me (so as not to clutter up this thread with a long settings list) and I will use it to set mine up the same and try to reproduce.

Edit: Also, if you could send me the content of your latest log, file location as previously advised, in a PM it will help see what is happening when you try to change target FPS and it does not stick. Thanks.

Info sent via msg

ANOTHER UPDATE: IT IS OPENING AND CLOSING AGAIN, EVEN AFTER REBOOTING THE ENTIRE PC. SAME ERRORS.

Edited April 20Apr 20 by Rob G
New Info

14 minutes ago, Rob G said:

Info sent via msg

I am not seeing it in my inbox yet. Edit: Got it now.

Edited April 20Apr 20 by Reset XPDR

An update on @Rob G's issues for anyone following. They were specifically related to the VFR profile, which I had not got around to testing in detail yet. I flushed out three bugs and all have been squashed in 0.4.6.8-12, so @Rob Gis now back in business. This highlights the importance of getting feedback from others on these test builds as, while I try my hardest to cover every conceivable setting combo, it is pretty much impossible to try everything myself with something as complex as this. Therefore is entirely possible that these issues would have slipped through to the final release had @Rob Gnot tried the test version, encountered the issue and raised it. 

 

Edited April 20Apr 20 by Reset XPDR

26 minutes ago, Reset XPDR said:

An update on @Rob G's issues for anyone following. They were specifically related to the VFR profile, which I had not got around to testing in detail yet. I flushed out three bugs and all have been squashed in 0.4.6.8-12, so @Rob Gis now back in business. This highlights the importance of getting feedback from others on these test builds as, while I try my hardest to cover every conceivable setting combo, it is pretty much impossible to try everything myself with something as complex as this. Therefore is entirely possible that these issues would have slipped through to the final release had @Rob Gnot tried the test version, encountered the issue and raised it. 

 

And everyone take note that about 15-20 minutes after reporting my problem, everything was fixed. I think we all can agree that there are few, if any, developers, paid or otherwise, that provide the level of support we get for AutoFPS.

I had a try with DLSS-enabler and my RTX4080; here I took ingame FG3X, so I had 90fps with native 30fps setted. After deleting the enabler-file (I couldn't use it for longer because my monitor went out of its specs) auto-fps remains in 90fps when the modus stayed in FG. Only 2X is bringing back my 60fps (30fps ingame and FG2X). I wonder where the 90fps are stored and from which source the tool is reading out the (wrong) measurements.

https://www.directupload.eu/file/d/9260/2gjn6o4v_jpg.htm and  https://www.directupload.eu/file/d/9260/gxbvmua9_jpg.htm
 

Edited April 20Apr 20 by Kai-Uwe Wei

Looked at the readme but didn’t see it, so I’ll ask here: if I am using non-expert fps cap mode, what is a good base setting to set my TLOD and OLOD in the sim? Typically, I run with sensitivity mode and do 50 TLOD on the ground, and 200 in the air, but think I can push my system further. However, at 200 set in the sim settings, the non expert mode is too aggressive, and goes above 500 TLOD in the air, causing stuttering and vram messages. Is the idea to set it at something somewhere in the middle of what I use in the ground and in the air? 

Edited April 20Apr 20 by agent00729

6 hours ago, Kai-Uwe Wei said:

I had a try with DLSS-enabler and my RTX4080; here I took ingame FG3X, so I had 90fps with native 30fps setted. After deleting the enabler-file (I couldn't use it for longer because my monitor went out of its specs) auto-fps remains in 90fps when the modus stayed in FG. Only 2X is bringing back my 60fps (30fps ingame and FG2X). I wonder where the 90fps are stored and from which source the tool is reading out the (wrong) measurements.

https://www.directupload.eu/file/d/9260/2gjn6o4v_jpg.htm and  https://www.directupload.eu/file/d/9260/gxbvmua9_jpg.htm
 

The app is reading your base FPS from MSFS via SimConnect and it is reading your FG settings from your UserCfg.opt file, the latter of which must still be set to the equivalent of 3X from when you used the mod, not caused by AutoFPS. 

To fix, without MSFS running you will need to go into your UserCfg.opt and change this line:

From 2 to 1, which changes from 3X (ie. 1 rendered plus 2 generated frames) back to 2X (1 generated frame).

When you have fixed this, you can change AutoFPS Target FPS Type back to Auto and FG will now be auto detected correctly at 2X.

 

Edited April 20Apr 20 by Reset XPDR

1 hour ago, agent00729 said:

Looked at the readme but didn’t see it, so I’ll ask here: if I am using non-expert fps cap mode, what is a good base setting to set my TLOD and OLOD in the sim? Typically, I run with sensitivity mode and do 50 TLOD on the ground, and 200 in the air, but think I can push my system further. However, at 200 set in the sim settings, the non expert mode is too aggressive, and goes above 500 TLOD in the air, causing stuttering and vram messages. Is the idea to set it at something somewhere in the middle of what I use in the ground and in the air? 

 

You say that you use non-expert fps cap mode in the first sentence, but then sensitivity mode with specific TLOD settings in your second sentence, which makes it unclear as to what actual mode you are asking about.

In any case, the readme does outline what TLOD settings range it uses in non-expert mode for FPS Cap mode as follows:

Quote

 

If an FPS cap is detected, the FPS Cap TLOD automation method will be used with the following settings:

• Auto Target FPS - disabled and hidden as a user-specified FPS cap is in use
• LOD Step - 5
• TLOD Base Min - VFR 50% of your current MSFS TLOD setting, IFR 25%
• TLOD Top Min - VFR 150% of your current MSFS TLOD setting, IFR 100%
• TLOD Base Extra - enabled with an x2 multiplier
• TLOD Top Extra - enabled with an x2 multiplier
• Mtns - disabled

 

ie. with a default MSFS-set TLOD of 200, in VFR you will get 100-200 on the ground and 300-600 in the air. In IFR you will get 50-100 on the ground and 200-400 in the air.

The fact that you are seeing above 500 in the air implies you are using the VFR profile, so the simplest solution is to switch to IFR to limit TLOD in the air to 400 max. 

If you really meant sensitivity mode in expert mode instead, then you will need to clarify as it is not possible to go above 200 if that is what you have set for TLOD Top Max in this mode.

Edited April 20Apr 20 by Reset XPDR

14 minutes ago, Reset XPDR said:

 

You say that you use non-expert fps cap mode in the first sentence, but then sensitivity mode with specific TLOD settings in your second sentence, which makes it unclear as to what actual mode you are asking about.

In any case, the readme does outline what TLOD settings range it uses in non-expert mode for FPS Cap mode as follows:

ie. with a default MSFS-set TLOD of 200, in VFR you will get 100-200 on the ground and 300-600 in the air. In IFR you will get 50-100 on the ground and 200-400 in the air.

The fact that you are seeing above 500 in the air implies you are using the VFR profile, so the simplest solution is to switch to IFR to limit TLOD in the air to 400 max. 

If you really meant sensitivity mode in expert mode instead, then you will need to clarify as it is not possible to go above 200 if that is what you have set for TLOD Top Max in this mode.

Thanks for getting back. I meant to say I was using sensitivity mode  prior, and am now testing non expert fps cap mode. Also, I was seeing 500 TLOD, even though I had 200 in sim settings, and IFR mode selected. Regardless, what is a good sim setting to set with this non expert mode? For example, is the idea to set it to something I can get good performance in basically any scenario? Because 200 wouldn’t be that, as it is too high of a setting on the ground at a place like EGLL. Let me know if that makes sense.

Edited April 20Apr 20 by agent00729