I just opened autoFPS, which prompted me to install the latest test verion, which I did. But when I try to open the program, nothing happens. It doesn't show up at all. What coulod be wrong?

Watching in the task manager, I see it open and then immediately close.

Edited July 24Jul 24 by Rob G
More info

After installing latest test version, AutoFPS will not load either in game or trying to launch it manually. This is test23. I went back to test22 and all is working fine I just make sure it doesn't autoupdate.

Edited July 24Jul 24 by cappy42

6 minutes ago, cappy42 said:

After installing latest test version, AutoFPS will not load either in game or trying to launch it manually.

You're not alone, as you can see from the post just above yours :-(

Edited July 24Jul 24 by Rob G

On my system, AutoFPS test 23 won't autostart with MSFS, but it does start manually once in the sim.

Sorry about this. I just stumbled across the issue myself when trying out non-expert mode and am looking in to it now.

Can others experiencing this advise whether using Expert or non-expert when encountering this no start. Any other relevant details of your last known good config will also be helpful.

8 minutes ago, Reset XPDR said:

Sorry about this. I just stumbled across the issue myself when trying out non-expert mode and am looking in to it now.

Can others experiencing this advise whether using Expert or non-expert when encountering this no start. Any other relevant details of your last known good config will also be helpful.

I am using non-expert mode

Just now, Rob G said:

I am using non-expert mode

Thanks. I am pretty sure I have found and fixed it already. I will have it out in Test24 very shortly.

Edit. Test24 is out. Per below, if you can auto update through the app because it won't start, download and install from one of the links I just posted below.

Can you confirm that it fixes it.

Edited July 24Jul 24 by Reset XPDR

NOTAM - 0.5.2.0-test25 has now been released, which fixes an app CTD when starting up in non-Expert mode caused by a bug introduced in test23. If you cannot start test23 at all because of this, download and run the test25 installer from its direct link here or, if that has been superseded, get the latest version from the bottom of the 0.5.2.0-test download page here.

My apologies for the inconvenience. I haven't had an issue like this with a test version for a long time and hope it doesn't happen again. Please do not let it discourage you from participating in test builds as the feedback I get from them is invaluable in shaping the final releases!

Edit: Updated app version and references to -test25 just released.

Edited July 24Jul 24 by Reset XPDR

1 hour ago, Adamski_NZ said:

On my system, AutoFPS test 23 won't autostart with MSFS, but it does start manually once in the sim.

This may be the same issue as others were reporting when using non-Expert mode. Please update to test24 and advise whether this is still an issue for you.

Edit: I just tried test24 and MSFS auto-start myself and it is starting up fine, so hopefully you will experience the same.

Edited July 24Jul 24 by Reset XPDR

No need to apologise! You're always great at rolling out fixes quickly and, of course, we're all extremely grateful for this life-saver of an app :)

My Test23 CTD'd in expert mode. I'll grab Test24 and report back!

BTW, if anyone is wondering why I am messing around with profiles, which is where this CTD causing bug lived, is that I am expanding the total number of flight profiles from 6 to 8 (and even up to 12 is possible if you edit the config file) and the app Reset button has a flight profile settings reset to default capability that is accessible only when in Expert mode, sim detected but not in a flight.

Hopefully users will find them as useful as I do with all the testing I do!

Edited July 24Jul 24 by Reset XPDR

Just now, Adamski_NZ said:

My Test23 CTD'd in expert mode. I'll grab Test24 and report back!

Interesting. Can you send me the text details from the two Event Viewer (under Event Viewer->Windows Logs->Application) error events for that crash. Should look something like (this one is from the non-Expert mode bug):

Faulting application name: MSFS_AutoFPS.exe, version: 0.4.5.0, time stamp: 0x6a3b0000
Faulting module name: KERNELBASE.dll, version: 10.0.26100.8875, time stamp: 0xca32cd54
Exception code: 0xe0434352
Fault offset: 0x00000000000c1ada
Faulting process id: 0x8F1C
Faulting application start time: 0x1DD1B1CC3959F48
Faulting application path: C:\Users\username\AppData\Roaming\MSFS_AutoFPS\bin\MSFS_AutoFPS.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 2ffe15e6-850c-4078-aa26-0aacf2d2f16f
Faulting package full name: 
Faulting package-relative application ID: 

and:

Application: MSFS_AutoFPS.exe
CoreCLR Version: 8.0.2926.32403
.NET Version: 8.0.29
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException: Object reference not set to an instance of an object.
   at MSFS_AutoFPS.ServiceModel.LoadConfiguration() in C:\Users\username\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\ServiceModel.cs:line 839
   at MSFS_AutoFPS.ServiceModel..ctor() in C:\Users\username\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\ServiceModel.cs:line 573
   at MSFS_AutoFPS.App.OnStartup(StartupEventArgs e) in C:\Users\username\Documents\GitHub\MSFS_AutoFPS\MSFS_AutoFPS\App.xaml.cs:line 122
   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()

Edited July 24Jul 24 by Reset XPDR

ok this might sound silly but if my autofps won't open, how do I get the new version??

12 minutes ago, Rob G said:

ok this might sound silly but if my autofps won't open, how do I get the new version??

From the post I made earlier:

1 hour ago, Reset XPDR said:

If you cannot start test23 at all because of this, download and run the test24 installer from its direct link here or, if that has been superseded, get the latest version from the bottom of the 0.5.2.0-test download page here.

10 minutes ago, Reset XPDR said:

From the post I made earlier:

Sorry I missed that. The problem is fixed for me. You are amazing.