48 minutes ago, TacomaSailor said:

Went thru a bunch of testing & experimentation on this problem.

In Task Manager - do you see AutoFPS as an App or Background Process?  My problems with no program output to the screen occurs when AutoFPS runs in the background, which by Windows definition, means there is no screen interaction.

I do not understand how AutoFPS ends up in the background.  It happens (AutoFPS moves from an App in the foreground to a background process)  on my system when the MSFS ends abnormally or if I end AutoFPS by closing it or clicking the x in the top left corner of AutoFPS.

The ONLY way I have found to move AutoFPS back to the foreground (make it become an App again) is to kill the background process, use the AutoFPS installer to remove the app and then use the autoinstaller to reinstall AutoFPS.

I have also found that starting MSFS2020_AutoFPS as an administrator process makes it less likely to move to the background.

It is all a bit strange!  But, the app works perfectly and I use it every time I fly.

Kill the Process - I found that I had to explicitly kill (a windows command) the background process BEFORE I did the REMOVE using the autoinstaller.

In an Administrator level DOS Command window: C:\Windows\System32>TASKKILL /IM "MSFS2020_AUTOFPS.EXE" /F

 

It's running as a background process.  When I do the reinstall it works fine again but eventually stops again.  When I do multiple flights I often have to kill it in task manager and problems usually start again after.

On 5/15/2024 at 4:38 PM, GSalden said:

Remove, restart your pc and reinstall the App

thanks that fixed it. All is smooth again 😄

34 minutes ago, sfgiants13 said:

It's running as a background process.  When I do the reinstall it works fine again but eventually stops again.  When I do multiple flights I often have to kill it in task manager and problems usually start again after.

What I found is that it will always run as a background process once it gets moved to the background.  Killing it with task manager does not prevent that.  Using the taskkill command will prevent it from running in the background the next time you start it.

On 5/20/2024 at 10:22 AM, TacomaSailor said:

What I found is that it will always run as a background process once it gets moved to the background.  Killing it with task manager does not prevent that.  Using the taskkill command will prevent it from running in the background the next time you start it.

So far that seems to be doing the trick.  Thanks!

Just joined up to put my two pence in.  It's a wonderful app [thank you] but here's the thing...

When I'm having issues with stuttering and I start the app, for a brief few moments the stutters completely vanish (with no apparent degradation of graphics quality either) - only to return again a few moments later.  What's happening in those few moments as the app 'hooks in' to MSFS and effectively stops the stuttering?  Could that be worked on and expanded perhaps?  It does the job but the smoothness doesn't last!

While I'm here, I read that the app needs to be started before MSFS - is there a specific reason for that?  

😎  

1 hour ago, ClevaTreva said:

I read that the app needs to be started before MSFS

it SHOULD start automatically during MSFS IF you selected auto start during install. Just run install again and select that to get auto start.

In my experience it can be started and restarted at any time but I'm happy with it there always so auto for me. 

Just found and started using this great tool!

One thing I don't understand is why the clouds are set to Medium by AutoFPS when the conditions look like what is seen in the screenshot below.

Normally, I have my clouds set to High and with the GPU util at 47% at this moment and the recover value in AutoFPS is set to below 80%, shouldn't the clouds have been reset to High at this point?

Uncheck decrease cloud quality. 

11 minutes ago, Bobsk8 said:

Uncheck decrease cloud quality. 

🤔

But I want it do decrease the cloud quality but only if reducing the LOD levels isn't enough. I thought that is how it was meant to work and also why you have the Decrease / Recover values? Where a GPU utilization value below 80% should recover my original setting for clouds...that is High and not Medium.

10 hours ago, WebMaximus said:

But I want it do decrease the cloud quality but only if reducing the LOD levels isn't enough.

I have the same version, and an option to select cloud detail based on either GPU load or TLOD.

10 hours ago, WebMaximus said:

But I want it do decrease the cloud quality but only if reducing the LOD levels isn't enough.

I have the same version, and an option to select cloud detail based on either GPU load or TLOD.

Same here but my question was why AutoFPS kept the clouds at Medium in the situation shown in the screenshot when all values were good.

59 minutes ago, WebMaximus said:

Same here but my question was why AutoFPS kept the clouds at Medium in the situation shown in the screenshot when all values were good.

Maybe all values were good BECAUSE the clouds were reduced to medium? 

Duplicate

Edited July 2, 20241 yr by Reset XPDR
Duplicate

On 6/19/2024 at 1:30 AM, ClevaTreva said:

While I'm here, I read that the app needs to be started before MSFS - is there a specific reason for that?  

You can start the app any time, but you will get the best experience if you start the app before you click Fly.

 

13 hours ago, WebMaximus said:

Normally, I have my clouds set to High and with the GPU util at 47% at this moment and the recover value in AutoFPS is set to below 80%, shouldn't the clouds have been reset to High at this point?

Your app screenshot shows that cloud reduction is not active (because the text is black not red) hence your default cloud setting must be medium not high.  Your log file will show what is going on. Note, do not change cloud quality in MSFS settings while in a flight with the app running otherwise the change will not stick on MSFS exist. Change it either with the app not running or in the main menu not in a flight.