48 minutes ago, TacomaSailor said:

I tried something novel for an old programmer - let the xpert deal with it!

I quit using expert options.  I selected Target:PC / FPS:50 / On Top / Flight Type:VFR and you provided amazing results!

All my busy test approaches stay at 60 FPS (30 limit in Sim and nVidia FG) with just the quickest hiccup over the threshold, (very occasional and quite brief and only down to 30 or so) but by the time the wheels touch down I am back to 60 FPS.

And... the LODs both stay above 150 all the time. 

I tried to "trick" or overpower your anticipation by crossing the threshold at 50' and 200 knots with the wheels up (a flyby) but the FPS stayed right at 60.

I don't quite understand because I thought I had set both LODs to a minimum of 150 when I was having problems.

Can't tell you how much I appreciate your work and how clever you must be.  I've been trying to figure out how you came to this procedure - must have been a lot of tedious experimenting.

Thank You again

AutoFPS 0.4.4.9

2024 Beta 1.5.2.0

Win 11 23H2

From other feedback I have received today, it looks like the new SU3 beta, 1.5.2.0 which you are currently using, shows a vast reduction in stutters on landing, so I don't want to take too much credit for what may otherwise be serendipity. 😁

Nonetheless, thank you for your kind words. Yes, I have put a lot of effort into making the non-expert experience as simple yet effective as possible and I am glad that you appreciate it.

BTW, 0.4.4.10, which is a maintenance build, is nearing the end of its test phase and will likely be released tomorrow. IMO, it consolidates the large changes that were introduced in 0.4.4.8 and refined in 0.4.4.9 quite nicely, so hopefully you will enjoy that release even more.

21 minutes ago, Reset XPDR said:

From other feedback I have received today, it looks like the new SU3 beta, 1.5.2.0 which you are currently using, shows a vast reduction in stutters on landing, so I don't want to take too much credit for what may otherwise be serendipity.

Hmm

These landing stutters are still very much there for me.

 

Never had them before the last couple of betas of SU2.

 

Even flying a small default aircraft into a small default remote airport at like 50 TLOD, which is of course well within the reach of my system to be smooth as silk, I still get these new stutters.

The last few test builds I haven't been able to open the AutoFPS window to change settings. 

It shows as running in system try and task bar, but I just can't get it to open. If I Alt+Tab, it just doesn't come up.

Edited May 22, 20251 yr by abennett

3 hours ago, abennett said:

The last few test builds I haven't been able to open the AutoFPS window to change settings. 

It shows as running in system try and task bar, but I just can't get it to open. If I Alt+Tab, it just doesn't come up.

It would be very helpful if you can tell me what specific test version the issue started with.

As you mention the system tray, I assume you have the app installed with the 'app closes to system tray' option checked when you installed it. I just tried it installed that way with 0.4.4.10-test16 and the window restores and hides as expected.

I suggest you try the following:

• It is most likely that the window is actually showing but is offscreen. 
  • On release versions, but not on test versions unfortunately, if you quit the app and restart it within 10 seconds, it resets the window position to default, so you could try reinstalling 0.4.4.9 formal release and do that to rescue the window. 
  • Alternatively, you could try pressing ALT SPACE then M when the AutoFPS icon is selected on the task bar then use the arrow keys to try and return the window to your monitor display area.
• Perhaps try reinstalling with the 'app closes to system tray' option unchecked and see if that gets it back working. If so then try reinstalling with it checked.
• If all else fails, try doing a clean install of the app, ie. by check "Clean Install (new config files)", which will reset everything including the window position, and see if that resolves it.

 

Edited May 23, 20251 yr by Reset XPDR

I hate to add to this 203pp thread (!!) but I have a tiny niggle:

On my version (0.4.4.10 Test 16), when I try to access the Expert/OLOD settings, the window expands when I hover over the Auto OLOD label, but when I try to edit any of the values, it often collapses and I end up editing a value in the TLOD section. Why doesn't my expanded window stick?

Other than that, AutoFPS is working well on my system 🙂

Hmm - I'm using SU3 Beta 1.5.3 and the last two test builds and the RC1 build fail the MSFS compat test.

I tried changing MSFS settings etc, also did a clean install of the app.

App recognizes SU3 and connects, then the sinconnect  activates but when it gets to the session - error and close.

I removed the MSFS cache, roaming downloads and scenery indexes - no help.

Thanx!

It's not going to help, sorry... But I have no issue with MSFS2024 SU3 1.5.3.0 except that I have to reset "Target FG FPS" at every flight.

PS: I'm using the dev test version 0.4.4.10-RC1

Edited May 24, 20251 yr by vbazillio

2 hours ago, vbazillio said:

It's not going to help, sorry... But I have no issue with MSFS2024 SU3 1.5.3.0 except that I have to reset "Target FG FPS" at every flight.

PS: I'm using the dev test version 0.4.4.10-RC1

Good to know. I've tried no community folder, no exe.xml, remove and reinstall app - same incompat issue. Log(in pdf form) attached for @Reset XPDR

MSFS_AutoFPS20250524log.pdf

33 minutes ago, vgbaron said:

Good to know. I've tried no community folder, no exe.xml, remove and reinstall app - same incompat issue. Log(in pdf form) attached for @Reset XPDR

MSFS_AutoFPS20250524log.pdfUnavailable

I think you need to have the mobiflight folder in the community folder for the app to work

14 minutes ago, ttbq1 said:

I think you need to have the mobiflight folder in the community folder for the app to work

just doublechecked - mobiflight event module is there

17 hours ago, Adamski_NZ said:

I hate to add to this 203pp thread (!!) but I have a tiny niggle:

On my version (0.4.4.10 Test 16), when I try to access the Expert/OLOD settings, the window expands when I hover over the Auto OLOD label, but when I try to edit any of the values, it often collapses and I end up editing a value in the TLOD section. Why doesn't my expanded window stick?

Other than that, AutoFPS is working well on my system 🙂

It is because you are moving your mouse away from the AutoOLOD setting area. When you click on a text box to edit it, don't move your mouse until you have hit enter or tab to accept the value.

5 hours ago, vbazillio said:

It's not going to help, sorry... But I have no issue with MSFS2024 SU3 1.5.3.0 except that I have to reset "Target FG FPS" at every flight.

PS: I'm using the dev test version 0.4.4.10-RC1

The log will tell you whether the change is being accepted or not. Are you sure you are actually accepting the change by hitting enter or tab after you enter the number? Is this on a particular profile only or any of them?

If still not working, copy and paste the section of your log file where you attempt to change the setting and I will take a look. It should look something like this around the time mark where you make the setting change:

Quote

2025-05-25 08:13:37.695 [INF] [ MainWindow:TextBox_SetSetting    ] targetFpsPC1 changed to 30
2025-05-25 08:13:37.696 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:PC ATgtFPS:False FltType:Test TgtFPS:30 TLODMethod:FPSCap Tol:20 LOS:False TMin:200 TMin+:true TBase-:False TMax:400 TMax+:False TMax-:True TLODBAlt:1000 TLODTAlt:5000 CustomOLOD:True OLODB:300 OLODT:20 OLODBAlt:2000 OLODTAlt:6000 RSet:True IncCld:True RLvls:2 RFloor:1 RRecov:0 RSuite:2 VRAM+:Max Vh:96% Vr:98%

 

 

5 hours ago, vgbaron said:

Hmm - I'm using SU3 Beta 1.5.3 and the last two test builds and the RC1 build fail the MSFS compat test.

I tried changing MSFS settings etc, also did a clean install of the app.

App recognizes SU3 and connects, then the sinconnect  activates but when it gets to the session - error and close.

I removed the MSFS cache, roaming downloads and scenery indexes - no help.

Thanx!

Your attachment isn't available for some reason. I get:

                                                                                         Oops!

This attachment is not available. It may have been removed or the person who shared it may not have permission to share it to this location.

---

In any case, nothing has changed with the compatibility test for many test builds now and with over 800 downloads of the latest test and RC versions you are the first to report of such a compat test fail with 1.5.3.0.

I will need to see the log file to work out what is going on. I've private messaged you with my email address so that you can send me your log file directly in it's original form.

1 hour ago, Reset XPDR said:

It is because you are moving your mouse away from the AutoOLOD setting area. When you click on a text box to edit it, don't move your mouse until you have hit enter or tab to accept the value.

It's still quite an irritating behaviour though. I can't see why that panel needs to auto-hide anyway - it'd be much simpler if it remained open all the time <??>.

Yes. I agree with Adamski_NZ. Let the panel remain open, please.