Just now, mmcmah said:

Yes, they can be changed in sim to a max of 200 for TLOD and 400 for OLOD in the sim menu.

Much appreciated sir, thank you.

Just now, iFlySimX said:

In the MSFS graphics settings. They are sliders...you will see them there.

Thank you too.

Thanks so much to the dev for this app.

I have a couple questions on how best to use it. My setup is a 

Ryzen 7900x

32gb DDR5 6000mhz ram

7900 XTX GPU

1000W PSU

2tb NVME

Quest 3 using AV1 encoding 200mbps virtual desktop high res setting at 72 FPS SSW always enabled for flight sim.

I started the app, and put 36 FPS (half of the 72 from headset) and it lowered my settings for take off on the ground to the minimum of 50 and cloud level medium - as I climbed to 3k feet it all showed FPS 36 at green but the TLOD and clouds stayed the exact same (50 and medium)

any idea why this is? Using virtual desktop perf overlay it showed I was getting a steady 72 FPS as well. Do I need to change the target FPS to 72 instead of 36? Or is there something else I'm missing? Thanks!

AutoFPS Settings:

Target PC FPS 36

Use expert options & open window on app start both checked.

FPS tolerance 5%

Tlod minimum 50

Tlod maximum 400

Tlod min on ground/landing checked

Decrease cloud quality checked

Cloud recovery tlod 100

Pause when MSFS loses focus not checked

I took off from JFK, and made it to 6k altitude with no change.

 

Quick install question. GitHub shows 3 assets for this app, the install or exe file and two source code items, one a zip file. Must I download all 3 to use this app, or just the install file? And do I unzip the source code file before running the install?

Thanks,

Rich

Only the exe

11 hours ago, Reset XPDR said:

That is the first report I've had of it showing DX11 instead of DX12. The method the app uses is quite simple. It looks for the PreferD3D12 in your usercfg.opt file and says DX11 for a 0 setting and DX12 for a 1 setting. It only checks while the app is starting, so if you change DX version while in MSFS but haven't restarted you could get this apparent discrepancy, although technically it is correct because the DX mode doesn't change unless you restart.

The only impact of an actual incorrect DX version detection is that if the app thinks you are in DX11 then it won't show any FG detection and status as DX11 doesn't allow FG.

In any case, thanks for mentioning this. Please let me know if it happens again and whether you had been changing DX version in the MSFS settings menu.

Thank you for the reply and info.  Just a quick note to answer the questions you asked because I need to spend more time on this (hopefully over the next few days). 

The display shows DX11 every time I run the app.  And I have not changed the setting in MSFS at all.  I checked usercfg.opt and it shows this:

FSRModeVR PERFORMANCE
    PrimaryScalingVR 0.800000
    SecondaryScalingVR 1.000000
    SharpenAmountVR 1.000000
    VSync 0
    HDR10 1
    Raytracing 0
    PreferD3D12 1

Also, here's a portion of the log- it mentions Steam but I'm on MSFS Store version and don't have Steam on my PC.  I may have caused the problem when I first ran the Installer and chose to use Autostart (accidentally clicking Steam).  But I've deleted the app and reinstalled it but the problem persists.  

  
2024-02-26 22:02:11.110 [INF] [ App:InitSystray                                    ] Creating SysTray Icon ... 
2024-02-26 22:02:11.204 [INF] [ ServiceController:Run                         ] Service starting ... 
2024-02-26 22:02:11.206 [INF] [ IPCManager:WaitForSimulator            ] Simulator not started - waiting 30s between Retries 
2024-02-26 22:03:41.279 [INF] [ MobiSimConnect:Connect                   ] SimConnect Connection open 
2024-02-26 22:03:41.279 [INF] [ IPCManager:WaitForConnection           ] Connection not established - waiting 30s between Retries 
2024-02-26 22:03:43.250 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2024-02-26 22:03:46.749 [DBG] [ MobiSimConnect:SimConnect_Receiv ] Sending Ping to MobiFlight WASM Module 
2024-02-26 22:03:46.858 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2024-02-26 22:03:46.966 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2024-02-26 22:03:56.550 [INF] [ IPCManager:WaitForSessionReady   ] Session not ready - waiting 5s between Retries 
2024-02-26 22:05:06.665 [DBG] [ MemoryManager:GetActiveDXVersion ] Steam MSFS version detected - DX11 
2024-02-26 22:05:06.665 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368 
 

I'll check back soon.  Thanks again!

 

16 minutes ago, Mike7777 said:

Thank you for the reply and info.  Just a quick note to answer the questions you asked because I need to spend more time on this (hopefully over the next few days). 

The display shows DX11 every time I run the app.  And I have not changed the setting in MSFS at all.  I checked usercfg.opt and it shows this:

FSRModeVR PERFORMANCE
    PrimaryScalingVR 0.800000
    SecondaryScalingVR 1.000000
    SharpenAmountVR 1.000000
    VSync 0
    HDR10 1
    Raytracing 0
    PreferD3D12 1

Also, here's a portion of the log- it mentions Steam but I'm on MSFS Store version and don't have Steam on my PC.  I may have caused the problem when I first ran the Installer and chose to use Autostart (accidentally clicking Steam).  But I've deleted the app and reinstalled it but the problem persists.  

  
2024-02-26 22:02:11.110 [INF] [ App:InitSystray                                    ] Creating SysTray Icon ... 
2024-02-26 22:02:11.204 [INF] [ ServiceController:Run                         ] Service starting ... 
2024-02-26 22:02:11.206 [INF] [ IPCManager:WaitForSimulator            ] Simulator not started - waiting 30s between Retries 
2024-02-26 22:03:41.279 [INF] [ MobiSimConnect:Connect                   ] SimConnect Connection open 
2024-02-26 22:03:41.279 [INF] [ IPCManager:WaitForConnection           ] Connection not established - waiting 30s between Retries 
2024-02-26 22:03:43.250 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2024-02-26 22:03:46.749 [DBG] [ MobiSimConnect:SimConnect_Receiv ] Sending Ping to MobiFlight WASM Module 
2024-02-26 22:03:46.858 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2024-02-26 22:03:46.966 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2024-02-26 22:03:56.550 [INF] [ IPCManager:WaitForSessionReady   ] Session not ready - waiting 5s between Retries 
2024-02-26 22:05:06.665 [DBG] [ MemoryManager:GetActiveDXVersion ] Steam MSFS version detected - DX11 
2024-02-26 22:05:06.665 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368 
 

I'll check back soon.  Thanks again!

 

Thanks for the detailed info on this issue.

What this tells me is that the Steam version is indeed being detected and in the code that can only happen if it finds a UserCfg.opt file where Steam, not the MS Store, puts it, namely at C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator. The MS Store version puts its UserCfg.opt file somewhere different, namely C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache. If you have never installed the Steam version of MSFS, and you are sure, I have no idea how the Steam UserCfg.opt file got there.

In any case, the fix for you should be to go to C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator and rename the UserCfg.opt file there to something like UserCfg.opt.bak and see if that fixes it.

Edited February 27, 20242 yr by Reset XPDR

44 minutes ago, Mike7777 said:

I may have caused the problem when I first ran the Installer and chose to use Autostart (accidentally clicking Steam). 

Also, this confused me somewhat as I gather you are talking about the AutoFPS installer here. If so, it has two Autostart options: FSUIPC or MSFS. ie. there is no Steam Autostart option in the installer. Can you please clarify what you meant. Thanks.

ok  just installed  it   just got  question  what  does it  mean  when it  says auto  paused(when climbing), do  i need  to un select or  select a setting  or  is  it  normal

Edited February 27, 20242 yr by pete_auau

1 minute ago, pete_auau said:

ok  just installed  it   just got  question  what  does it  mean  when it  says auto  paused, do  i need  to un select or  select a setting  or  is  it  normal

From the readme:

• Pause when MSFS loses focus - This will stop TLOD and, if applicable, cloud quality from changing while you are focused on another app and not MSFS. It is particularly useful for when using FG as the FG active and inactive frame rate can vary quite considerably and because FG is not always an exact doubling of non-FG FPS. When expert settings are disabled, the app will enable this setting.

FYI, since I get a few questions about auto pause, I am thinking about disabling it by default when Use Expert Options is unchecked in the next AutoFPS release as it seems to cause more confusion than being useful to new users of the app. As the readme already says, it is useful in a particular FG circumstance so it is probably not useful being on by default for most.

Would anyone object to me disabling auto pause by default?

34 minutes ago, Reset XPDR said:

From the readme:

• Pause when MSFS loses focus - This will stop TLOD and, if applicable, cloud quality from changing while you are focused on another app and not MSFS. It is particularly useful for when using FG as the FG active and inactive frame rate can vary quite considerably and because FG is not always an exact doubling of non-FG FPS. When expert settings are disabled, the app will enable this setting.

yep  just  found  that out  just after  i posted thx

11 minutes ago, Reset XPDR said:

FYI, since I get a few questions about auto pause, I am thinking about disabling it by default when Use Expert Options is unchecked in the next AutoFPS release as it seems to cause more confusion than being useful to new users of the app. As the readme already says, it is useful in a particular FG circumstance so it is probably not useful being on by default for most.

Would anyone object to me disabling auto pause by default?

fine  by  me

7 minutes ago, pete_auau said:

yep  just  found  that out  just after  i posted thx

Sorry I was a bit blunt about it. As mentioned subsequently, this feature is obviously causing confusion with new users so I am going to change how it works out the box. You just happened to latest person to bring it up and it made me do something about it, so thank you for being the catalyst of change!

8 minutes ago, Reset XPDR said:

Sorry I was a bit blunt about it. As mentioned subsequently, this feature is obviously causing confusion with new users so I am going to change how it works out the box. You just happened to latest person to bring it up and it made me do something about it, so thank you for being the catalyst of change!

Nah my fault by not researching  more  in detail,  even  though i did  read  the github   info 🙂