@Reset XPDR

Thank you very much for this quick update. That works like a charm!

On 5/1/2024 at 6:46 AM, Cpt_Piett said:

No worries! You'll get back into it in no time 😄 

It's working!

Screenshot should be pretty self-explanatory. Since I have a 4090, I had to increase the resolution to 6144x3240. 

As you also fly airliners : what would you suggest : autoLOD or Sensivity  ?

Up to know I use Sensitivity…

What I would like to accomplish is to eliminate the small stutters that sometimes appear at final at about 10-20 sec before touchdown.

On the other hand more people have stated that after the last updates there appears stutters at final…

4 hours ago, GSalden said:

As you also fly airliners : what would you suggest : autoLOD or Sensivity  ?

Most of the time I use sensitivity at 5, gives the smoothest experience IMO. 

ENGM Oslo. Using FSHud as injector with max 30 parked, max 5 active, FSLTL. Fenix parked at gate. 

FPS is RTSS-locked at 63. Flat frame time graph, no stutters. About to do a flight to Stuttgart - will report back. Or actually - should I choose FlyTampa's EHAM instead? Then I can do a couple of approaches and compare AutoLOD vs Sensitivity. 

Edited May 3, 20242 yr by Cpt_Piett

2 minutes ago, Cpt_Piett said:

Most of the time I use sensitivity at 5, gives the smoothest experience IMO. 

ENGM Oslo. Using FSHud as injector with max 30 parked, max 5 active, FSLTL. Fenix parked at gate. 

FPS is RTSS-locked at 63. Flat frame time graph, no stutters. About to do a flight to Stuttgart - will report back. Or actually - should I choose FlyTampa's EHAM instead? Then I can do a couple of approaches and compare AutoLOD vs Sensitivity. 

Thanks. I will sent you a pm if it is ok with you.

2 minutes ago, GSalden said:

Thanks. I will sent you a pm if it is ok with you.

Sure, no problem. 

AutoFPS v0.4.2.13-test can be downloaded here.

Summary of changes since v0.4.2.12-test:

• Added the ability to automatically reset window position to default (50,50) if app is restarted within 60 seconds of last closing to allow users a simple way to recover window visibility if last window saved position is off screen and can't otherwise be recovered.
• Added saving of the app's hidden settings sections so that the previous state is restored the next time you start the app.

Summary of all changes since v0.4.2.10 formal release:

• Functionality changes
  • Added decrease cloud option for AutoLOD automation method with user definable cloud reduction and recovery GPU loads. Requires GPU-Z companion app to be running in order to provide the app with GPU load information. To better facilitate this, GPU-Z can now be started at any time and the GPU-Z gpu load reading is now a 5 second average to smooth out transient GPU load spikes.
  • Added LOD Step Size setting in AutoTLOD automation mode to allow users experiencing stuttering issues to try different LOD step sizes to help resolve the issue. The default value is 5.
• UI improvements
  • The user can progressively hide parts of the UI when the app window is double clicked anywhere that is not a control. The first double click will hide the expert settings section (if applicable), the second will hide the general settings section and a third double click will restore all hidden settings sections. The last state in use will be restored when next starting the app.
  • The app will now remember whether it was visible in previous session and will restore that state on next startup.
  • The app will now automatically reset window position to default (50,50) if the app is restarted within 60 seconds of last closing to allow users a simple way to recover window visibility if last window saved position is off screen and can't otherwise be recovered.
• Miscellaneous fixes
  • Fixed logging function so that sim values will be recorded even if app window is hidden.
  • Fixed issue where MSFS could be incorrectly detected as being paused when over water at a near constant speed due to rounding.

18 minutes ago, Reset XPDR said:

AutoFPS v0.4.2.13-test can be downloaded here.

Summary of changes since v0.4.2.12-test:

• Added the ability to automatically reset window position to default (50,50) if app is restarted within 60 seconds of last closing to allow users a simple way to recover window visibility if last window saved position is off screen and can't otherwise be recovered.
• Added saving of the app's hidden settings sections so that the previous state is restored the next time you start the app.

Summary of all changes since v0.4.2.10 formal release:

• Functionality changes
  • Added decrease cloud option for AutoLOD automation method with user definable cloud reduction and recovery GPU loads. Requires GPU-Z companion app to be running in order to provide the app with GPU load information. To better facilitate this, GPU-Z can now be started at any time and the GPU-Z gpu load reading is now a 5 second average to smooth out transient GPU load spikes.
  • Added LOD Step Size setting in AutoTLOD automation mode to allow users experiencing stuttering issues to try different LOD step sizes to help resolve the issue. The default value is 5.
• UI improvements
  • The user can progressively hide parts of the UI when the app window is double clicked anywhere that is not a control. The first double click will hide the expert settings section (if applicable), the second will hide the general settings section and a third double click will restore all hidden settings sections. The last state in use will be restored when next starting the app.
  • The app will now remember whether it was visible in previous session and will restore that state on next startup.
  • The app will now automatically reset window position to default (50,50) if the app is restarted within 60 seconds of last closing to allow users a simple way to recover window visibility if last window saved position is off screen and can't otherwise be recovered.
• Miscellaneous fixes
  • Fixed logging function so that sim values will be recorded even if app window is hidden.
  • Fixed issue where MSFS could be incorrectly detected as being paused when over water at a near constant speed due to rounding.

Thanks for the new update. Really appreciate all your great work 😃

On 5/3/2024 at 10:22 AM, GSalden said:

As you also fly airliners : what would you suggest : autoLOD or Sensivity  ?

Did two approaches in the Fenix last night into Schiphol 18R with AI traffic.

First one:

• sensitivity 5 | TLOD min 50 below 1000ft | max 975 (I know, I’m crazy…)
• FSHud as the injector set at max 30 AI parked, max 5 active

Second one:

• AutoTLOD min 50 max 400
• AIG traffic controller set to 50%

Much less frame time variation in 2nd session + slightly better FPS i.e. best result.

Conclusion:

Better performance with AutoTLOD, but difficult to know for sure since settings were not identical. I’m going to switch between both for a while and compare.

Note:

• I should have used the same injector in both sessions, but I was recording a video with OBS for the second session, and FSHud completely messes up the audio when recording, for some reason. Anyway, AIG at 50% probably gives more traffic than FSHud with 30/5
• different TLOD max

 

5 hours ago, Reset XPDR said:

AutoFPS v0.4.2.13-test can be downloaded here.

Can’t wait to test!! Didn’t expect a new version 🥳

 

Edited May 4, 20242 yr by Cpt_Piett

Wanted to give AutoFPS a go again and so I installed AutoFPS v0.4.2.13-test but ran into a small problem. AutoFPS did start but decided to run in the background and stay there without displaying the GUI. What went wrong or what did I do wrong? (I did install this new version exactly as previous ones)

1 hour ago, hvw said:

Wanted to give AutoFPS a go again and so I installed AutoFPS v0.4.2.13-test but ran into a small problem. AutoFPS did start but decided to run in the background and stay there without displaying the GUI. What went wrong or what did I do wrong? (I did install this new version exactly as previous ones)

If I recall from one of the recent release notes, it will now remember if you had it visible or minimized when you last opened it.

5 hours ago, Cpt_Piett said:

Did two approaches in the Fenix last night into Schiphol 18R with AI traffic.

First one:

• sensitivity 5 | TLOD min 50 below 1000ft | max 975 (I know, I’m crazy…)
• FSHud as the injector set at max 30 AI parked, max 5 active

Second one:

• AutoTLOD min 50 max 400
• AIG traffic controller set to 50%

Much less frame time variation in 2nd session + slightly better FPS i.e. best result.

Conclusion:

Better performance with AutoTLOD, but difficult to know for sure since settings were not identical. I’m going to switch between both for a while and compare.

Note:

• I should have used the same injector in both sessions, but I was recording a video with OBS for the second session, and FSHud completely messes up the audio when recording, for some reason. Anyway, AIG at 50% probably gives more traffic than FSHud with 30/5
• different TLOD max

 

Can’t wait to test!! Didn’t expect a new version 🥳

 

Thank you for these tests. I will start with AutoTlod + PL as a starting point trying to eliminate the last small stutters at final.

19 minutes ago, mmcmah said:

If I recall from one of the recent release notes, it will now remember if you had it visible or minimized when you last opened it.

Thanks. I guess I have to reset the setting in question in the cfg file. Right?

1 minute ago, hvw said:

Thanks. I guess I have to reset the setting in question in the cfg file. Right?

I think you just need to leave the window visible next time it closes.

23 minutes ago, mmcmah said:

I think you just need to leave the window visible next time it closes.

The GUI (Window) does NOT open after installing the application.  But thanks for your suggestion.

Completely uninstalling and reinstalling it again fixed the problem

Edited May 4, 20242 yr by hvw
Solved the issue

11 hours ago, Reset XPDR said:

AutoFPS v0.4.2.13-test can be downloaded here.

@Reset XPDR If you didn't select 'Auto-Start with FSUIPC/MSFS' on the initial install, it seems impossible to get the installer to add it at a later date i.e. with an update. I have tried several times and the EXE.XML remains untouched. I have also 'removed' the app using the button in the app and reinstalled but it still doesn't add itself to the EXE.XML (like it used to).

Could you please confirm that this is the correct entry:

Quote

    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>MSFS2020_AutoFPS</Name>
        <Path>C:\LOCAL PC PATH TO MSFS2020_AutoFPS.exe</Path>
        <NewConsole>False</NewConsole>
    </Launch.Addon>

Also strange, the main window is now 'invisible' after an update. I can see that App is open but the window remains invisible and not in the Taskbar. EDIT - closing the app and reopening it makes it 'visible'. It's only 'invisible' on the initial install.

Regards,
Toby

Edited May 4, 20242 yr by toby23