2 hours ago, hvw said:

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

Completely uninstalling and reinstalling it again fixed the problem

As @mmcmahsays, the app remembers whether you had the window showing last time or not and starts with that. If it starts not showing, just double click on the icon in the system tray and the window will show. Uninstalling and reinstalling works too, as it resets the config file, but shouldn't ever be necessary for this.

8 minutes ago, toby23 said:

@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.

Regards,
Toby

I don't normally use autostart so I just tried an update install with autostart selected and it successfully added AutoFPS to my EXE.xml. Rerunning the installer and selecting remove autostart restored my EXE.xml file correctly too.

The only thing I can think of is there is a permissions issue with accessing your EXE.xml file. You could either try running the AutoFPS installer as admin, which may have the undesired side effect of needing you to run AutoFPS as admin all the time, or just manually edit your EXE.xml file per the readme and add the following section:

  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>MSFS2020_AutoFPS</Name>
    <Path>C:\Users\<username>\AppData\Roaming\MSFS2020_AutoFPS\bin\MSFS2020_AutoFPS.exe</Path>
  </Launch.Addon>

Thanks, it's definitely not adding the entry to the EXE.xml on my system but other apps have no problem writing to it...

16 minutes ago, Reset XPDR said:

As @mmcmahsays, the app remembers whether you had the window showing last time or not and starts with that. If it starts not showing, just double click on the icon in the system tray and the window will show. Uninstalling and reinstalling works too, as it resets the config file, but shouldn't ever be necessary for this.

There was nothing to double click on. The GUI/Window didn't show up 🙂 

Just now, toby23 said:

Thanks, it's definitely not adding the entry to the EXE.xml on my system but other apps have no problem writing to it...

I have not changed the installer code for a long time and it seems to work for most others so I am not sure what is going on here. At least there is a manual way to fix it.

1 minute ago, hvw said:

There was nothing to double click on. The GUI/Window didn't show up 🙂 

Sounds like a corrupt config file which is fixed by the uninstall and reinstall that you did anyway.

7 minutes ago, Reset XPDR said:

I have not changed the installer code for a long time and it seems to work for most others so I am not sure what is going on here. At least there is a manual way to fix it.

This started with version 4.2.12.

7 minutes ago, Reset XPDR said:

Sounds like a corrupt config file which is fixed by the uninstall and reinstall that you did anyway.

It did, in such a way that I now can open the GUI by clicking the icon in the system tray. No problem, as long as I can work around it this way, it is fine for me

 

@Reset XPDR

While I was testing with AI ac settings / PL / AutoFPS I had lots thick clouds on my left view monitor and a few on the front view monitor.

I upped the FPS setting in AutoFPS to 50 and saw that Clouds remain at Ultra.

Is this correct with my current settings ?

2 hours ago, GSalden said:

@Reset XPDR

While I was testing with AI ac settings / PL / AutoFPS I had lots thick clouds on my left view monitor and a few on the front view monitor.

I upped the FPS setting in AutoFPS to 50 and saw that Clouds remain at Ultra.

Is this correct with my current settings ?

Yes it is correct. Your FG Active FPS is set to 50 but FG is currently inactive, so the app halves that target value internally to 25 and the 33 FPS FG Inactive FPS your screen shot shows you were achieving is above that so the clouds stay at Ultra. If you'd given MSFS the focus again, your FG Active FPS would have shot up to over 60 FPS and you are still above the your target FG Active FPS of 50, so clouds will still remain at ultra. This is how it should behave with FG active and inactive.

@Reset XPDR

I just switched over to AutoFPS from DynamicLOD 0.3.1 and it seems you've brought this a long way. Thanks!😁

Thanks for this Mod.  Absolutely brilliant upgrade for FPS.

Is removing DymanicLOD as straight forward as deleting the installation folder and deleting the Desktop short cut or is there more to it?

1 hour ago, FBW737 said:

Is removing DymanicLOD as straight forward as deleting the installation folder and deleting the Desktop short cut or is there more to it?

That will do it, however any auto-start options will still be present and just won't activate and you shouldn't get an error message. You could also run the original installer and there is a remove option, which removes everything cleanly.

Is there any idea, why this tool is close to unusable to me due to second long stutters and generall stuttery experience when flying around.

When i dont use it, i have more or less stable 40-60 fps (LOD 200, 4K resolution, DLAA, DX11, most settings on High or Ultra).

Do i have to deactivate something in the graphic settings so have this great experience most people describe?