ankh21

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

Mh, to which version of Active Sky is this guide related to? I have Active Sky FS, version 9495, and i can hardly find half of the settings mentioned here.

Haha, just imagine it as a cost saving company advise not to change the rubber of the wipers before they are nothing more than an idea...so the animation is as real as life can get ;-)

Mh, i flew the PMDG 737-600 yesterday and the wipers cleared the windsheeld, the raindrops were gone...although the area is perhaps a little bit too small and more to the bottom-center of the windsheeld. Will check this again, but i am pretty sure, it was not just imagination :)

No, running on the 3D cores was fine, AMD driver controlled or via BIOS settings, both gave priority to the 3D cores. I don't know, if is was due to a BIOS / MOBA problem or something else. I made two BIOS upgrades after that but was not in the mood to enable the virtualization back. I cannot remember exactly...i think, it was in the FsHUD Discord channel, where another user mentioned a similar performance problem, and disabling SVM mode in the BIOS did the trick for him, too. Might be a very specific problem of my MSI motherboard. Just an idea, as i said.