I made my first long haul flight after updating this program and I was really impressed with how well it helped the sim perform after nine hours of flying. That is how I can tell how good the program is. I took off in MVFR at LEMD and landed at KJFK in LIFR -RA and BR. It was smooth as silk on the approach and didn’t stutter taxiing into the gate. Thank you so much for updating us! It made a huge difference!!
The 'On Top' feature is useful for those of us that use Nvidia's Limit Background Application Framerate setting. I use it to bring GPU/CPU temps down, if you like browsing the web, watching RU-vid videos whilst flying (on autopilot between destinations). Thanks for your work, subscribed! Edit: My sim has started to freeze. Not sure if it is the app, but it's the only change I have made. Further testing, live traffic setting was causing the freezing, not the auto fps app.
You need to make it clear in your videos that this is NOT the same program as DynamicLOD. Could you not tell there was confusion based on comments left in the first video of this author's version, that you presented to us a couple days back? What is adding to the confusion is; although this author's version is clearly different in the background code (with less features and adjustments from the original plus not suitable for fixed FPS settings like the original): however he is still using the exact same desktop icon; the exact same UI window, (minus the more adjustable settings of the original) both elements shown clearly in your videos AND furthermore, confusingly and frankly suspiciously started his version at 4.X, (And not 1.x) making people think it is a continuation of DynamicLOD version 3.6! Go back and pay attention to the first video comments and you will see other people stating they are using an older version and other comments, etc. So I am not the only one confused here. P.S. Above; I wasted time with this dev author asking him why he was removing features, etc only to find out after a few message exchanges; he finally told me he was not the original author, LOL! No big deal and apologized for the confusion because he was clearly getting frustrated and based on the circumstances, I don't blame him, he, he. @@IslandSimPilot
Really like the altitude threshold being a variable. Didn’t realise scenery popping is a DX12 issue, what’s going on there. It might be nice to have a profile for VFR and another for IFR cos it seems to me they may benefit from different settings. Great program.
I commented on your previous video IRC that it need the on top/draw on top feature so we could monitor performance better in flight and so happy that's been implemented and so quickly. Pleasantly surprised to find flying GA in good weather conditions that my maximum TLOD was topping out and I was able to increase it by quite a bit. Something I wouldn't have known withoutvthis great little app.
In VR if you are locking frames and/or using ASW for example then TLOD won’t increase because fps won’t increase. For this case use the other version -DynamicTlod according to AGL
Thanks, that may explain why my LOD pretty much just stayed a 50 with this. I’m happy with the performance I get with the original Dynamic LOD anyway so not lost anything by trying.
Don't really like anything "auto". DynamicTLOD let me customize the setting according to my flight. I really like that aspect because I fly in VR and that control made VR flying more enjoyable.
I agree! This doesn’t seem to be as effective as DynamicLOD for us VR users. I do have my frame rate locked to 45fps or half the 90fps native. So basing the adjustments based on AGL is way more effective since my fps rarely move more than 1 or 2 fps from my set goal of 45. But thanks for keeping us updated on these great tools!
I'm sorry, I can barely understand you. Sound like you have MMS (mush-mouth syndrome). Your words sound mushy, and are you breathing alright? You sound terribly hard to understand. Maybe you need a new mic? Or try breathing thru your nose maybe. Mush-mouth IS manageable.
Nice update, thx. One other key parameter to be used to control FPS should be the Terrain Shadows in my opinion. Cheers, PS/ I noticed that I can launch this app even AFTER the sim is running !
Thank you so much Capt. Great video very clear explanation of this new version. If it wasn't for you I wouldn't have my Sim running they way it is running now, thank you so much..
Just few words to say that I recently discovered the MSFS TBM 930 which is absolutely an amazing aircraft once you tame the G3000. It's an easy and versatile turboprop aircraft. VNAV mode perfectly works here and ILS Localizer and Glide Slope are very easily cought as well as the VNAV Glide Path. You just have to take care to "Direct To" the first approach point of your flight plan since there is no connexion between the last STAR point and the first Approach point in this G3000. In addition I realised that in Developper mode, once landed and parked on your favorite airport, you can use the menu "Tools/Aircraft Selector/" and choose another aircraft at the same spot. Like so, you can, say, take an helicopter and fly the last miles to your home sweet home or pay a visit to a beautiful spot🙂. Cheers
Thanks so much for keeping us posted on this excellent Tool. Managing cloud levels is a great step ahead, allowing the ultra setting as long as possible.
Your videos are awesome but respectfully I will suggest you to watch your "ahhhhh" after your random pauses, and try to make them a little bit faster, maybe you will have to start planning a little bit your scripts... (when we start making videos we all suffer from that, believe me, but there is no way around, you make a script and you will speed up your videos).
Tried version 1 of this (in vr), it was so smooth I was in heaven, when I checked though it was LOD 50 on the ground, changed to LOD 60 at about 2000’, then back to LOD 50 at all altitudes above that even though my frame rate was well above what I had set within the program. Strange behavior so I just went back to using the version with user set heights/LODs which for me works beautifully. Thanks for all the work you do for the flight sim community, it’s very much appreciated.
Quick question, love the content! My monitor is 165hz, but I have my fps capped at 50. Do you recommend I change my monitor hz through NVCP or should I just leave it?
No, because this utility only adjusts 3 parameters within the Game graphics settings. These 3 are the most CPU intensive though. So using this utility can allow you to tweak up a few other settings to higher levels depending on your system. You would need something like MSI Afterburner or the monitoring utility in the developers section in-game to help you out or just use the old school method and adjust a setting, one at a time and see how your system reacts. Keep in mind this game is using code dating back to 2015 so make 1-3 adjustments and if they work, shutdown the program and restart to make additional adjustments. Make too many changes at a time while in-flight and the performance gets unpredictable. (Some settings also don't take effect unless you restart too. The game won't tell you this either.)
Thanks for the informative video. However; this is messy now for people that lock-in a fixed frame-rate for VR, I'll still stick to the older version that had an actual user adjustable fps target recovery setting for all settings= TLOD/OLOD and Clouds. Extensive testing has shown in VR at least, if you lock-in a fixed frame-rate, (via XR toolkit or MSI AB/Riva Tuner) to the lowest level you see while flying in the densest features like a city, random micro-stutters completely go away because you always have some CPU/GPU overhead to work with when transiting between rural and the Suburbs/Cityscapes or any other situation that suddenly required additional CPU/GPU resources. This also allows you to crank up game detail settings to higher levels and use this utility, (at least the older version anyway) to ensure you maintain your minimum FPS with no stutters as well. So a fixed 15% cloud recovery value is useless in a fixed FPS case. The 1% FPS recovery is still OK though, Go back and make it for the clouds as well? For example in my system using the older version of the utility program, I would set minimum FPS to 29 and recovery FPS to 30. My fixed FPS is also 30. To accommodate the cloud 15% NON-ADJUSTABLE recovery limit, I would have to set my minimum FPS to 25. To force this large a drop in FPS, micro-stutters WILL occur every time!!! I don't understand why the developer keeps taking away user adjustable features, LOL!!!
The 15% recovery was an addition to Cloud Reduction Recovery functionality, not a removal of something you had before, so that's not correct. It is non adjustable because if people go setting it to 1% like you want to, your clouds would continuously toggle in and out of cloud reduction and would get many more questions and complaints about this than your single complaint. Also the readme quite clearly states this app does not work with a target FPS set very near to or the same as your FPS cap, yet that is what you are trying to do. If you still don't understand all this then all I can do is suggest you uninstall the app and find something else that does meet your expectations.
Thanks for the reply; I understand clearly but it is clear you misinterpreted my writing from your defensive attitude in your reply. I was making a suggestion and not making a complaint, hence the "LOL" at the end! But I was confused why to took away a feature again. I'm currently using version 3.6. It works wonderfully with a FPS cap by the way! (No complaints and totally happy with it!!!!!!!!!!!!) This old version has cloud recovery adjustable in FPS above your target minimum level. It works fine, most of us are smart enough to realize that the clouds might change in quality during the flight BECAUSE YOU HAD A SETTING IN THIS OLDER VERSION THAT EXPLAINS IT CLEARLY! Why not just put the setting back in for us smarter peeps that don't care if the clouds might change detail from time to time? Peeps that don't want to see the clouds pop back and forth can just raise the setting to a higher recovery level or disable cloud details changes entirely, right? The older version meets expectations AND WORKS WITH FIXED FPS, your newer version DOES NOT! If YOU don't understand all this then I will just keep using the older version that works perfectly! @@ResetXPDR
@@bakzetary3145While AutoFPS has its roots in DynamicLOD, it is a completely different app with a different purpose, specifically to be simpler to use and to automate those things that matter the most for attaining a target FPS. In doing so, cloud recovery was retained but the primary recovery mechanism is different - DynamicLOD's is a recovery FPS and AutoFPS's is a recovery TLOD. They are not directly comparable, so referring to such functionality in the "old" app being missing in the "new" one is not really relevant. I am pleased that DynamicLOD_ResetEdition 0.3.6 works for you (there is a new 0.3.8 version BTW) but please don't disparage AutoFPS because it doesn't do what an existing app that is still being developed and supported does and that has been clearly stated from the outset that it was never intended to do.
Also I think you are forgetting the original purpose of the utility: To provide a minimum steady FPS with the secondary benefit of reducing or eliminating micro stutters. Something the utility does an excellent job at. In your quest to tweak the utility further, you keep removing features that reduces the utilities usefulness for the largest possible number of users. This time it is the user adjustable cloud recover setting. Before, it was removing the adjustable Object level of detail, (OLOD). I am glad you realized the benefit of returning that function back into the program in your latest version. Finally, now you are also saying that current version will not work if target FPS is set to close to the FIXED FPS setting. I can assure the older version 3.6 works just perfectly with only 1 FPS difference between the 2 settings! (I run it now for many days at a 2 FPS difference just to reduce the noticeable fluctuations detail changes a little less often. (Which is the whole mechanic of the program: therefore seeing detail changes on the fly is the trade off here, no way around that!) If you set other graphics setting more precisely to the limits of your CPU/GPU; the only time this program will "kick-in" is when approaching higher detailed terrain mainly around the cities and suburbs. Based on my testing, this program works with the best results and virtually zero micro-stutters when approaching cities. If you're out in the rural areas and this program is continuously working out there then I would recommend lowering other graphic settings outside what the program adjusts for best results in every type of terrain. In conclusion; all I am asking is keep the utility as flexible as possible. @@ResetXPDR
@bakzetary3145 I will say this one more time and I am done with this fruitless conversation. They are different apps with different objectives, some of which are not comparable and cloud reduction recovery is one. We are done. Enjoy 0.3.6.
Hey Mike, apologies, I posted on my channel yesterday evening that someone had the audacity to invite my girlfriend and I out to dinner 😂 Don’t they know my priorities?! But we will be flying Sunday at 3 my friend
Loved the previous version of this program. Updated due to the OLOD being included but I’ve found that in this version once I get to 60fps which I’m capped at through nvcp, the TLOD stops increasing and my clouds don’t increase in quality.
Hi. When I go out of the full screen with Taskmamager and open the Auto FPS window, it tells me that DX12, PC mode and that frame generation is inactive. Do you know why?
Already been using since it came out a couple days ago.... Love it minus wish we could choose in the app FG Settings, PC Settings and VR Settings without sim open in the either of the 3 with also allowing Expert Settings to be different for each of the 3 via app selection.... Has anyone found that in VR your TLOD is always at your minimum setting regardless if you are well above 1000ft ALT Default when TLOD at Min on Ground/Landing Checked in Expert Settings and unchecked TLOD at Min on Ground/Landing the max TLOD engages at any ALT even below default 1000ft when you have VR headset headroom? Thank You RESETXPDR for all your coding work....
You can just edit the config file for the program and put in the settings you want for pc, Vr and fg. The GitHub page mentions where the program is stored and the name of the configuration file. I just used Notepad to open the file, changed things and then saved the file.
You are most welcome. The only reason that TLOD would stay at minimum well above 1000 ft with TLOD min on gnd/ldg checked is if your system is not achieving your Target VR FPS. If this is not the case ,raise an issue where you downloaded it giving specific details on how to reliably reproduce the issue and I will look into it. TLOD adjusting at any alt with TLOD min on gnd/ldg unchecked, anywhere within the range TLOD min to TLOD max depending on FPS headroom, is exactly how that feature is supposed to work.
Yes that’s what I found. Frame rate well above what I set but pretty much stuck at 50 LOD. Just reverted back to the original Dynamic LOD program which works nicely for me in vr.
@@peterregan8691 : I still have it installed 0.3.7 and while trial by fire with AGL Settings I may in fact return to that version. I just seem to be able to dial in better visuals with less impact to FPS while having more manual control plus presets depending on how I am enjoying MSFS.
@@ResetXPDR : The update did not go so well was my guess so I did a full dump and reinstall. The TLOD and OLOD worked thereafter however seemed stressing on FPS a little. Mind you I am rendering at 4k on monitor, 2k per eye, have second monitor and streaming with OBS at 1080p on a RTX3080ti... All Is good and I hope this 0.4.1 becomes more refined with some of the goodies with 3.7.1 in the future. Till then, I think I am going back to your 3.7.1 where I have more manual control and presets.
I'm puzzled about FG framerates. I have a 3090 Ti, so I don't have a Frame Gen option. Yet I see the option in Expert Mode switching between FG Active and FG Inactive - especially if I change the a target FPS, but sometimes just randomly. For example, I have the standard FPS target set to 60. I'll see the FG Active @ 120. Then, if I manually change the FG target to 90, it becomes 'Inactive.' If I change the standard target to 45, then FG becomes active again, and shows 90. I didn't see a good explanation for this in the ReadMe file. Is this app generating it's own Frame Generation? How can I stop it? I don't need or want FrameGen.
If you have ever tried the FG mod and disabled or removed it without turning off the FG option in MSFS first, it is possible this is the cause of your incorrect FG detection in the app. I suggest you go into your UserCfg.Opt file and look for the line DLSSG and change it from a 1 to a 0, which will hopefully fix this for you.
@@nevillecrook371 DX12, DLSS Quality, no vSync. I had previously installed the 'Fake' Frame Gen mod for the 2xxx and 3xxx-series nVidia card. It gave me Frame Gen, but had some unwanted side effects. I wonder whether that contributes.
hey bro, i have two questions, firstly,have you heard or isnt it file or way that can correct the flickering and jittering caused by the frame gen mod as there already exists this type of files for another games like gta v for example
@@ResetXPDR Found it. For anyone else: "If you use an FPS cap, or Vsync for the same purpose, you will need to set your target FPS to be around 10% lower than that cap. This allows the automated TLOD increase logic to function properly because it needs FPS to get above the target FPS plus the FPS tolerance to activate an increase in TLOD. If doing so causes unacceptable tearing of the image on your monitor, or breaks motion reprojection if you use it with VR, then this app isn't suitable for you."
Thanks for showing this. I have triple 32s running I9-900k overclocked and a 3080 overclocked and with this Auto FPS I can get high 30s and low 40s at Ultra settings. I do have one question- I am running dlss super but cant run frame gen due to tearing across 3 monitors. I am downscaling and then upscaling to 4k on 1440 monitors like your other videos. Since I upscale to 4k, my monitors have the 4k res available even technically it is not. Do you run at the higher res on your monitor? I tried it and while it brings my FPS down to the low 30s it does seem more detailed. What do you run at?
What I would like to know, may Auto FPS be added to the startup list of MSFS AddonsLinker? Or is it better to start it seperately, even before MSFS AddonsLinker is started?
Yesterday I installed Auto-FPS and tried it. Overall it works quite well. However, I had 2 CTD's while loading a flight in Tromso (ENTC). After I started AUTO-FPS on the third attempt after loading the flight, there was no CTD. What could be the cause of this? I use 3 monitors and have limited the FPS to 45 in AMD Adrenalin. If I switch from the main MSFS monitor to another monitor while using Auto-FPS, the FPS changes up or down. Without Auto-FPS, the FPS remains locked.
Concur too. Community folder mod volume, also connection speed to the internet is also an issue. Larger RAM memory; the game will load more resources into RAM too. I updated from a Gen 3 M.2 running at 3K to a Gen 5 M.2 running at 12K and only saw a 10 second load speed improvement, LOL!@@Patrick_AV
I am always getting the error message when starting MSFS: Auto Fps is already running - exiting. Autostart is not enabled. When I klick the desktop icon the whole simulator stops working. Does someone has a solition for me?
Hey brother, so what one do you use? DynamicLOD or AutoFPS? I have both have turned LOD off when running AUTO. Not sure if I should fully remove the LOD mod
Above 1000 ft or (higher) the TLOD is still staying at 50. It does not scale back to 100 wich is the desired value in he settings. What am I missing? Thanks!
Can anyone tell me if this is worth messing with for my system - 2060 Super, i7 9700, 32GB RAM? MSFS has always looked blurry and had microstutters for me, no matter what I do. I mostly fly down low in light aircraft. Lowering LOD doesn't seem to help. DLSS might have helped some, its hard to say. DCS runs great. XP12 runs better than MSFS, but not great either. Thanks.
@@JesterMax24 Definitely give the frame gen mod a shot, that seems like it would be perfect for you. And yes, AutoFPS could very well help you as well, it's a fantastic program. Here is the FG mod: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UPhCiLJFx7s.html
Interesting. I don't agree with your ascertion that the pop-in is not a symptom of this program. If you reduce TLOD aggresively from 200 down to 50, the exact effect from that is that you INTRODUCE pop-in. I leave the TLOD at 400, I have a 4090, why wouldn't I and the amount of pop-in I get is massively reduced, hardly noticable I would say. For desktop use anyway if you have a powerful PC then I would stay clear of AutoMSFS, it's good if you don't want to play with graphical settings but from what I've seen it's fairly aggresive on the graphics reductions, and at the end of the day, running a utility like this will itself be a draw on resources, so if you can set your system up for a smooth experience without it, that has to be the best approach.
@@IslandSimPilot Thanks for the reply, When I remove my headset I see it's working, but I have to remove the headset, I did check the box to keep it always on top. I checked the GitHub page, there's nothing about Vr, unless I missed something but I did ask the question, waiting for a reply.
It will do this if you are not achieving your target FPS or if you are but your cloud recovery TLOD is set too high. For the former, set a more achievable lower target FPS and for the latter, cloud recovery is not an alt it is a TLOD value and it should be set to around 50 higher than TLOD min.
