Update just tried again with TBM from ASE to TEX lots of clouds at sunset with 200ft ceiling and snow.

NVCP set to 30 with AutoFPS framerate set to 28

Stellar smooth with very little variation anywhere. Still some rounded mountains but not nearly as bad as before.

target fps set at 48fps should i lower that?

vsync is on with 144hz monitor hence why 48 

thanks 

mike

8 minutes ago, mikeymike said:

target fps set at 48fps should i lower that?

vsync is on with 144hz monitor hence why 48 

thanks 

mike

If you have an FPS lock somewhere, it's very important to set target FPS in the app lower than this. Even though the release version can deal with target being a couple of FPS below the lock, you might consider lowering it even further if you find that TLOD is not increasing in a reasonable way. 

Also, as Reset mentioned, if target FPS is too high, LODs will likely not increase much above minimum. 

Example: I had just set my target FPS unreasonably high, and LOD would stay at min until I lowered the target FPS. I hope this makes sense. 

Edited March 17, 20242 yr by Cpt_Piett

35 minutes ago, Cpt_Piett said:

If you have an FPS lock somewhere, it's very important to set target FPS in the app lower than this. Even though the release version can deal with target being a couple of FPS below the lock, you might consider lowering it even further if you find that TLOD is not increasing in a reasonable way. 

Also, as Reset mentioned, if target FPS is too high, LODs will likely not increase much above minimum. 

Example: I had just set my target FPS unreasonably high, and LOD would stay at min until I lowered the target FPS. I hope this makes sense. 

I see,

Yes, that makes sense .

thank you very much to you both.

this a very unique tool.

thank you and much appreciated.

mike

Dear Developer,

Thank you - sorry to report but the latest latest test versions and the release version of 0.4.2 are broken for me sadly. 

Horrible stutter, 20 sec doing nothing, black screen, it even crashes! Especially when starting flight its frozen for 20 sec and frequently freezes for 10-20 seconds doing nothing in VR - toppest rig.

13900k/4090/32gb 8200cl34 ram/varjo aero win 11 openxr toolkit (39 ppd, dx12, dlss perf, HAGS, game mode, toolkit turbo mode, forced rebar, motion smoothing 45fps, fast vsync, 2 frames render ahead, reflex/latency off)

Used to be ultra smooth.

Please: could anyone please link the 12Mar240940Z version? thank you - it's been overwritten on github and i foolishly deleted the local file.

Thank you very much!

Best, Max

 

1 hour ago, maxstep said:

Dear Developer,

Thank you - sorry to report but the latest latest test versions and the release version of 0.4.2 are broken for me sadly. 

Horrible stutter, 20 sec doing nothing, black screen, it even crashes! Especially when starting flight its frozen for 20 sec and frequently freezes for 10-20 seconds doing nothing in VR - toppest rig.

13900k/4090/32gb 8200cl34 ram/varjo aero win 11 openxr toolkit (39 ppd, dx12, dlss perf, HAGS, game mode, toolkit turbo mode, forced rebar, motion smoothing 45fps, fast vsync, 2 frames render ahead, reflex/latency off)

Used to be ultra smooth.

Please: could anyone please link the 12Mar240940Z version? thank you - it's been overwritten on github and i foolishly deleted the local file.

Thank you very much!

Best, Max

 

That  sounds more like an issue with  your PC? Does it work properly if you don't start the app?

Just finished a breathtaking approach into Rio's Santos Dumont. Flying past Cristo Redentor at 5,500ft with inexplicably high settings thanks to AutoFPSwas an almost otherworldly experience... How far this sim has come!

At the time of the screenshot below I was getting: TLOD 684 OLOD 756 at a steady 80 FPS with almost zero frame time variability (i.e. virtually stutter-free). It's hard to fathom how this is possible. Must be some kind of sorcery...

Not long before that I was getting this... go figure! 🤷‍♂️

 

Edited March 17, 20242 yr by Cpt_Piett

2 hours ago, maxstep said:

Dear Developer,

Thank you - sorry to report but the latest latest test versions and the release version of 0.4.2 are broken for me sadly. 

Horrible stutter, 20 sec doing nothing, black screen, it even crashes! Especially when starting flight its frozen for 20 sec and frequently freezes for 10-20 seconds doing nothing in VR - toppest rig.

13900k/4090/32gb 8200cl34 ram/varjo aero win 11 openxr toolkit (39 ppd, dx12, dlss perf, HAGS, game mode, toolkit turbo mode, forced rebar, motion smoothing 45fps, fast vsync, 2 frames render ahead, reflex/latency off)

Used to be ultra smooth.

Please: could anyone please link the 12Mar240940Z version? thank you - it's been overwritten on github and i foolishly deleted the local file.

Thank you very much!

Best, Max

 

I replied to you on github but you may not have seen it yet. You can get 0940Z here.

I can confirm also I am getting stutters fps fluctuations .using AutoFPS f, first time user yesterday.

did a circuit flight around England on the 737.

heavy dense clouds for miles.

min TLOD at 170 and max 300

Decrease cloud quality checked but remained at ultra .

auto Olod at 200 min and max .

auto target fps set IFR

im confused as others have no issue 

 

I’m running a 7950x3d with a 3080ti

thanks 

mike 

@mikeymike As you're using auto target fps the app should manage TLOD, OLOD and clouds to give you decent FPS. Are you saying that FPS is too low? Or that it changes too much?

Although AutoFPS in auto target fps mode does a great job at giving a decent frame rate based on your hardware, it's important to know that it will not eliminate all causes of stutters. Stutters can be there for a variety of reasons - even at higher FPS. 

@mikeymike sorry to tag you again, just wanted to say that I edited my post, you might want to re-check if you already read the original version. 

Edited March 17, 20242 yr by Cpt_Piett

Hi All,

I, like pretty much all of you, love this app.

I have noticed that most screenshots from users show "FG active" however mine shows "PC".

Am I missing something or is this because I'm running DX11?  And I apologise if this has been answered previously.

Jase

 

FYI, I am

Just now, JaseMelbo said:

Hi All,

I, like pretty much all of you, love this app.

I have noticed that most screenshots from users show "FG active" however mine shows "PC".

Am I missing something or is this because I'm running DX11?  And I apologise if this has been answered previously.

Jase

 

They are using Frame Generation, which is only available with DX12, HAGS, Enabled in MSFS and with a video card capable of FG.

Just now, Reset XPDR said:

FYI, I am

They are using Frame Generation, which is only available with DX12, HAGS, Enabled in MSFS and with a video card capable of FG.

Awsesome - I have a 3060ti and use DX11 - thanks for this app.  It's great.

Jase

FYI, I will be releasing progressive update builds for the next AutoFPS version, which is only planned to be a minor maintenance release so they are more a preview than full on test builds, the latest version of which you can always get here. I will also keep all previous test build installers there from now on so you can go backwards or forwards anytime you want, mainly the former if you experience issues with the latest test release.

Note that I have changed the test build naming convention to be numerical for the last digit e.g 0.4.3.1-test, 0.4.3.2-test etc. This is so users always know what test build they are on when after it is installed as it will be shown in the running app, which should clear up confusion with the DTG convention used previously that only applied to the installer.

eg. you'll see something like this:

 

Edit: Oh, and I may as well mention what is in this new test build.

Initial Test Version 0.4.3.1-test:

• Added last window position saving/restoration on next startup. This may only work for single monitor as I haven't worked out how to place the app on a specific monitor yet, but it seems to be working fine on my dual monitor setup. If something goes wrong and it doesn't appear anywhere, you can just go into the config file and delete the two lines windowLeft and windowTop and it should reset it back to default.
• Improved MSFS settings saving and restoration to immediately reset cloud quality if a previously abnormal shutdown of either MSFS or this app was detected and to provide more log file detail on MSFS settings saving and restoration activities.
• Enhanced logging of cloud quality settings to use the actual textual description from the MSFS settings menu rather than the numeric it is stored as in MSFS memory.

Edited March 18, 20242 yr by Reset XPDR

For those with RTX40-series GPUs with native FG, or RTX30-series using the FG mod:

For frame generation to work properly, the native FPS (i.e. without FG) needs to be high enough for the FG AI tech to be able to do its job properly. Too low native FPS can induce stutters, even at seemingly high FG-FPS. E.g. with my 4090, I start to see stutters/tearing as FG-FPS drops to 50-60 FPS and below. This is to be expected, and there's nothing AutoFPS can do to alleviate this. 

I would suggest aiming for at least native FPS 30 (i.e. FG-FPS 60) to reduce the chance of seeing FG-induced stutters. The best way to do this is to reduce the load on the CPU, as MSFS is mostly CPU-limited. Things that puts a high load on the CPU: complex scenery, PG cities, complex aircraft, AI traffic. 

To check native FPS, open developer mode and check FPS overlay. There it's also possible to check how the mainthread (i.e. CPU) is doing. If the mainthread numbers are red most of the time, there's too much load on the CPU, and then it won't matter how well the GPU is doing: FPS will be limited by CPU ("mainthread-limited"), and most likely, there will be stutters. 

 

Edited March 18, 20242 yr by Cpt_Piett