ankh21

So, AutoFPS works as intended. Playing around with the target frame rate value, reduction and recovery kicked in as expected! Why i have been confused? It seems to me, that the frame rate count in the widget is not that respondend. I don't know the refresh rate, but during several test scenarios, i opened the RTSS overlay and saw several lows in the frame rate, but the widget gave me solid numbers. So i guess, as i experienced the non-recovery yesterday, i only watched the frame rate in the widget, but i guess in reality i had several dips, so AutoFPS did not recover the settings as the real frame rate was not stable enough to do so. Case closed :)

Thanks a lot. I forgot to mention that of course „recover“ was set to ground, as another user got caught by that trap some days before. And your manual is very clear, so I always check that first. Your description for the test setup is very detailed and easy to understand, like all your explanations, appreciate that a lot! I will run this test tomorrow as Mr. Sandman just came over, and report back. I never experienced that before, so i am very interested in the results. Thanks, Matthias

Sorry for asking, but has something changed in the recovery process? I am on 0.5.4.5.-test 11. Sitting at the gate in Frankfurt, I got an auto-reduction, cause my framerate decreased while watching east (City of Frankfurt). Later I got cleared for departure on 25 C, facing west. An although my frames were stable higher than the threshold and VRAM was 90%, AutoFPS did not recover either TLOD nor the customized setting. As far as I remember, I got this behavior only after landing as long as you are not below 2 or 3 knots. But holding short at a runway, I am quite sure it always increased the settings in the past? But sometimes my brain is playing tricks on me, so please apologize if my question is nonsense.

I am not the author, but "fixed" is, in my observation, very strict to hold the FPS set. For me, as the author mentioned in the post above, "manual" with a slightly lower FPS set gives very stable and smooth results. So in your case, you can try 55 FPS. Then, the small dips to 57 are ignored and only more severe drops are handled by AutoFPS.

Wow! Two more than welcomed features in one update, works like charm! As autumn brings early sunsets here in Germany flying real time while monitoring the effects of certain settings or changes via AutoFPS is now very nice. With the bright UI, it has been a little bit annoying. Now, I can just place the UI in one corner of the screen and just let it sit there with little to no visual impact. Thank you so much! Matthias

As always with MS Flight Sim, there is no easy or fit to all answer. I have a 4080 Super, and there are some things to be aware of. So, FrameGen on? Photogrammetry on? Rezisable Bar on? IFR airliner flying or more picking blossoms? Addons or running programs? To answer your question dealing with NVIDIA app, I prefer NV inspector, so I don’t user the NV app itself. So, with my CPU and a 4080 Super, IFR with PMDG 737 most of the time, caped FR at 31, AutoFPS, FG on with 3x, preset L (M gives excessive shimmering, K is smearing the numbers too much), photogrammetry OFF, ReBar OFF (both eats VRAM), texture resolution only on HIGH, FsHud for ATC and some other small addons, I have a very smooth experience with 90% VRAM usage or less in most situations. Changing only one thing (photogrammetry, texture resolution, etc.), I am at the VRAM max really quick. Just for orientation.

Hm, couldn’t start via FS shortcut (server not available), but could start via the Xbox App without any problems and complete a flight. Interesting. Matthias from Germany

Yes, just noticed several reports in the PMDG forum. It seems to be related to the Simbrief import. Mh, 737 fleet grounded, simulation as real as it gets 🫣

word not allowed, I did not experience a WASM crash before, but with the latest fix 4.00.057 I do! Again I deleted the only panel state I have saved, was able to complete a flight, but with the next flight, again WASM crash. So for me the hotfix makes it worse. Strange!

Test 16, works great! No more spike triggered TLOD decrease during window change! Chapeau! Matthias

Haha, you are that fast I cannot test and send log files as quick as you write new code lines…even if there are two 😜. So, I will save the log file from yesterday as AutoFPS installs the new version as soon as I fire up Flight Simulator. And after that I will test the new version. But I am sure, that my „problem“ of spike induced TLOD decrease will be cured with this new version. During flight, the new DynFG option seems to be my favorite as i have very stable frame rates and very rare TLOD changes with a 500 set max. Just a dream! Thank you so much!

Don't rush! As i mentioned in my original post, i already did this, but i am worried it was a little bit hidden in the text. "I have limited FS2024 to 31 frames, giving me 62 with build in FG on, dynamic frames set to 30 for small headroom (inside FS settings) So, I set FIXED under General tab, Target to DynFG and FPS to 30" (thats AutoPFS settings). So, AutoFPS sees 31 frames in the count, but Target Frame rate is already set to 30 as you suggested. I fixed the FS 2024 limiter to 31, to prevent interaction of the dynamic frame rate limiter too early. Sorry, i am not used to write in English, so i apologize for missleading statements. Matthias

Will do as soon as i am at home today. Thanks for your detailed explanations!! The critical point seems to be, that loosing focus of the FS main window generates spikes. AutoFPS says, that it has detected several spikes. So the reduction is not by general load on the GPU, but by spike detection during focus switch. Log will be sent soon! Thanks a lot!

Hi everybody! I was wondering, if anyone has recognized hard coded TLOD reduction in certain add on scenery?! I bought EDDS by Aerosoft, great scenery with lots of details and great performance. But as using AutoFPS, I was not used to lights and scenery popping in and out during approach, and somehow blurry terrain. Normally, with AutoFPS, I have very smooth and nearly invisible transitions. So I checked with developer mode, and there was a constant reduction of TLOD factor, reduced to 0,5 - 0,6, with stable frame rate! I only see this behavior with dynamic frame setting on, when the framerate drops under the fixed limit. But with framerate above? So I started the same flight at EDDF, TLOD factor 1.0….KLGA 1.0….back to EDDS down to 0.5 - 0.6.. Is it possible to hard code TLOD into scenery to mimic better performance? For me, this was the explanation for the scenery popping I only encountered with EDDS. I did a forum search but found nothing. Matthias

Hi, just a short little test feedback: works great. Seems to be less fluctuating compared to reading the postFG numbers via RTSS. In my case, I have limited FS to 31 frames, giving me 62 with build in FG on, dynamic frames set to 30 for small headroom. So, I set FIXED under General tab, Target to DynFG and FPS to 30. but there seems to be one side effect: during pre flight preparation , I have to switch between several windows. With the older FG reading via RTSS, AutoFPS recognized FG to become inactive and ignored the lower framerate. Now, it detects spiking, and so, it lowers TLOD to min, but being on ground, TLOD does not recover when switching back to FS main window. I remember, that is was designed to freeze TLOD reduction in certain situations. Clicking on the RESET button brings back a TLOD plus recovery, but as I use AutoFPS minimized in normal situations, it would be nice to ignore spike protection when switching between several windows. I hope, my writing is clear enough 🫣 Greetings, Matthias