Good morning everyone! Just grabbed 0.4.3.2.

Did a flight into very heavy scenery yesterday, namely Fenix into EGLC London City w/ AI traffic, Orbx airport, London City Pack and of course PG in the area. I can't think of many more demanding scenarios. Had set target FPS to 80 (with FPS unlocked this time) in IFR mode with TLOD Min at 50 (+ ticked) and TLOD Max 975. Auto OLOD with Max 1000 Min 20 - but after my extensive tests yesterday, OLOD seems to have a negligible influence on performance.

I made a video, and upon watching it, I did see some (minuscule) stutters - but I think that's almost unavoidable in this type of situation. I was actually surprised by how smooth things were! While flying the approach, I can't say I noticed anything - was probably too focused coming down the 5.5 degree glide slope at 1400fpm 😉

I haven't checked the log in several days now. In fact I don’t think I've even enabled it in config. Just checked and it seems logging is disabled by default. 

Not sure if there's any way I could help identify these issues. @mmcmah - do you have any suggestions e.g. location, aircraft - that I could test? And it could be useful to know if the stutters you experience are similar to the ones that can be seen in my video. Did you fly in a very dense area when you tested VFR mode? 

Edited March 20, 20242 yr by Cpt_Piett

Anyway, I'm currently in the TBM850 at the northernmost airport in mainland Norway as I thought I'd try the VFR mode a little today. Just took off and around 3000ft I've already got TLOD above 600. FPS stays a little bit above my target of 80. 

For comparison I switched to IFR - now FPS is 115 and TLOD just above 300. As I don't really see much benefit in FPS above 80, VFR with a much higher TLOD makes the most sense in this type of situation. The IFR/VFR terminology could possibly be a bit confusing (e.g. I’m currently flying in IMC), but I don’t think I’ve seen a single post about it in this thread, so it’s probably fine. 

I'm currently using FPS tolerance, to see if there's any difference to the more recent FPS sensitivity. I've left it at default 5%. Not sure what I should look for though, and beside it’s not really relevant to me as I’m not having the issues others are describing.

I’ve been doing some quick tests to see how TLOD will change when descending in VFR mode. 

1st test: Descent from AGL 3000ft to 500ft above the ocean. At 500ft I'm getting FPS 74 and TLOD 575. I have TLOD Min set to 50 with the "+" ticked. Got FPS priority in status line. 

2nd test: I descended from AGL 3000ft. At AGL 200-300ft TLOD stays above 600, FPS around my target of 80. I'm not brave enough to descend below 200ft - but then again I don't think AutoFPS would try to reduce TLOD from above 600 to TLOD Min below 200ft...

So it seems VFR will give me as high TLOD as my hardware can handle as long as my FPS stays around target, no matter how close to the ground I am. 

After this little experiment I checked the readme and everything makes sense.

Quote

TLOD will be locked any time you are below 100 ft or are on the ground, except if TLOD Min + is enabled and gets activated where it will be higher.

Once in the air above 100 ft, your TLOD will dynamically change to achieve your target FPS.

Once below 100 ft, your TLOD will lock to whatever it last was and will stay that way until you take off and climb above 100 ft.

I’m guessing the lock below 100ft is to reduce the chance of ground texture issues.

11 hours ago, Reset XPDR said:

VFR mode only sets TLOD Min on the ground (+ if you are getting extra performance and have + enabled), but then after that it will not work down to TLOD Min unless performance conditions have deteriorated, which your log file clearly shows has happened and again it is due to have such a larger TLOD range.

This seems to be working as intended, according to my observations. Even though I have TLOD max set at 975.

Initial conclusion: I’ll stand by what I wrote in my mini-guide:

On 3/18/2024 at 8:04 AM, Cpt_Piett said:

IFR/VFR

• Dense areas: IFR. This is because in these situations I need the TLOD min lock on ground landing, for a stable approach into a busy airport.
• Remote areas: VFR. Regardless of aircraft type. The difference in expert mode is that TLOD Min and descent rate will be handled automatically in VFR mode. Also, in VFR mode, TLOD Min is only used as the lowest TLOD the app will go to and can be much higher on landing.

Edited March 20, 20242 yr by Cpt_Piett

1 hour ago, Cpt_Piett said:

Anyway, I'm currently in the TBM850 at the northernmost airport in mainland Norway as I thought I'd try the VFR mode a little today. Just took off and around 3000ft I've already got TLOD above 600. FPS stays a little bit above my target of 80. 

For comparison I switched to IFR - now FPS is 115 and TLOD just above 300. As I don't really see much benefit in FPS above 80, VFR with a much higher TLOD makes the most sense in this type of situation. The IFR/VFR terminology could possibly be a bit confusing (e.g. I’m currently flying in IMC), but I don’t think I’ve seen a single post about it in this thread, so it’s probably fine. 

I'm currently using FPS tolerance, to see if there's any difference to the more recent FPS sensitivity. I've left it at default 5%. Not sure what I should look for though, and beside it’s not really relevant to me as I’m not having the issues others are describing.

I’ve been doing some quick tests to see how TLOD will change when descending in VFR mode. 

1st test: Descent from AGL 3000ft to 500ft above the ocean. At 500ft I'm getting FPS 74 and TLOD 575. I have TLOD Min set to 50 with the "+" ticked. Got FPS priority in status line. 

2nd test: I descended from AGL 3000ft. At AGL 200-300ft TLOD stays above 600, FPS around my target of 80. I'm not brave enough to descend below 200ft - but then again I don't think AutoFPS would try to reduce TLOD from above 600 to TLOD Min below 200ft...

So it seems VFR will give me as high TLOD as my hardware can handle as long as my FPS stays around target, no matter how close to the ground I am. 

After this little experiment I checked the readme and everything makes sense.

I’m guessing the lock below 100ft is to reduce the chance of ground texture issues.

This seems to be working as intended, according to my observations. Even though I have TLOD max set at 975.

Initial conclusion: I’ll stand by what I wrote in my mini-guide:

I will try to post a video with some of the stutters that happen. This was not in a crowded area. It was at the FSDT LSZH literally doing circuits around the airport at no more than 2000 ft AGL. Any time I turned towards the airport from a short distance, unless I had gotten to a level of keeping the TLOD steady, I would induce stutters that would create a self-reinforcing cycle of stutters/FPS drops/TLOD changes and repeat.

23 minutes ago, mmcmah said:

I will try to post a video with some of the stutters that happen. This was not in a crowded area. It was at the FSDT LSZH literally doing circuits around the airport at no more than 2000 ft AGL. Any time I turned towards the airport from a short distance, unless I had gotten to a level of keeping the TLOD steady, I would induce stutters that would create a self-reinforcing cycle of stutters/FPS drops/TLOD changes and repeat.

And just to confirm, this was in VFR mode?

More testing in VFR (expert): Just did a toucn 'n go at ENTC (less dense urban area) in the TBM850. 

• descent from 5000ft to ground: TLOD 600-450
• climb: 600 at 3400ft

I.e. very gradual changes. TLOD Min 50+. 

28 minutes ago, Cpt_Piett said:

descent from 5000ft to ground: TLOD 600-450

I have to ask:  just how obvious is TLOD 600 over 100 or 200?  

3 hours ago, Cpt_Piett said:

And just to confirm, this was in VFR mode?

Yes, that's in VFR. IFR Expert mode is one that I can configure to stop dropping TLOD below a certain altitude.

1 hour ago, Noel said:

I have to ask:  just how obvious is TLOD 600 over 100 or 200?  

I find that to be true. If I load into any scenery that has mountains in the distance (with my overall graphics settings, YMMV as usual), 100 looks fine but has rounded terrain at any short+ distance. 200, which is what I have set as my minimum, gets better, but still has rounded terrain at medium distance and a scarcity of trees that is noticeable. I have my maximum set to 800 because that's the point at which I see lots of terrain features at altitude and distance and doesn't bring my system to a crawl in scenery with lots of terrain features.

I’m running a 4090 and a 13900 so I don’t really need this tool but it does help when I’m landing at a big airport with FSLTL. I mostly using default setting with auto fps and the + Modes. I set TLOD max to 400. I feel like I have some head room left to increase some settings. Are there any recommendations?

Also, I’m not really sure how OLOD should be optimized? The higher I fly, the smaller the OLOD gets. Is this how it should normally work?

1 minute ago, petz_e said:

I’m running a 4090 and a 13900 so I don’t really need this tool but it does help when I’m landing at a big airport with FSLTL. I mostly using default setting with auto fps and the + Modes. I set TLOD max to 400. I feel like I have some head room left to increase some settings. Are there any recommendations?

Also, I’m not really sure how OLOD should be optimized? The higher I fly, the smaller the OLOD gets. Is this how it should normally work?

I have the same hardware. I use IFR with Expert mode for most things because it gives me the most control. I have it set to 200 as TLOD Min at 1000 ft AGL (so that I don't induce any stutters closer to the ground when flying around complex scenery and traffic). My TLOD Max is 800 and my FPS are currently sitting at 30 FPS below what I have my frames set to in NCP (which is 70). This allows the TLOD to increase nicely while climbing out but still being restrained by the fact that it needs to get back to the TLOD Min at 1000 if I change my mind and descend.

As for the OLOD, yes, it should go down as you increase your altitude. It really doesn't do much outside of airports or being very close to scenery, so you definitely don't need it al altitude. However, it really doesn't seem to impact performance, so you can test leaving it higher.

I can post my settings later if you want.

3 hours ago, Noel said:

I have to ask:  just how obvious is TLOD 600 over 100 or 200?  

Join the line of people asking me that question lol. IMHO: massive difference at high altitude during scenic flights. Check out my Lofoten video. Or Innsbruck. To my surprise TLOD not only affect terrain textures but also mesh resolution. If you don’t care about blurry and rounded mountains in the distance, don’t bother. This is very much up to individual preferences I think. When approaching Everest and Matterhorn, I want to see them in all their majestic glory!

Just had to open a window as it’s getting quite balmy up here in the attic with the PC on the floor below pumping out 80+ degrees air. The TBM850 has been in a 12,000ft hold for several hours as the forum activity seems to have exploded today. TLOD 600 does make my 12900 run hot 🔥 4090 hardly affected.

This is TLOD 560 at 12,000ft:

Edited March 20, 20242 yr by Cpt_Piett

1 hour ago, mmcmah said:

I have my maximum set to 800 because that's the point at which I see lots of terrain features at altitude and distance and doesn't bring my system to a crawl in scenery with lots of terrain features.

I think above 600 is for fringe situations only. In my Lofoten video I demonstrated terrain and mesh being rendered up to 100km / 54nm away at TLOD 950.

Edited March 20, 20242 yr by Cpt_Piett

1 hour ago, petz_e said:

I’m running a 4090 and a 13900 so I don’t really need this tool but it does help when I’m landing at a big airport with FSLTL. I mostly using default setting with auto fps and the + Modes. I set TLOD max to 400. I feel like I have some head room left to increase some settings. Are there any recommendations?

Also, I’m not really sure how OLOD should be optimized? The higher I fly, the smaller the OLOD gets. Is this how it should normally work?

I’d suggest looking at my guide + videos a few pages back where I elaborate in depth on this. I’m trying to figure out a way to make those more accessible as they’re quickly drowning.

1 hour ago, mmcmah said:

As for the OLOD, yes, it should go down as you increase your altitude. It really doesn't do much outside of airports or being very close to scenery, so you definitely don't need it al altitude. However, it really doesn't seem to impact performance, so you can test leaving it higher.

100% agree. I had it at 1000 over Manhattan at 3000ft IIRC. I haven’t seen OLOD affecting anything other than airport objects, although I could be wrong.

Edited March 20, 20242 yr by Cpt_Piett

New AutoFPS 0.4.3.3-test version is available here. @Cpt_PiettThe new auto pause on sim pause/menu may help with the 0 FPS issue you were having the other day when exiting a flight if it is still occurring. This auto pausing code is experimental as simconnect does not have a native way of telling the app that the user is in the menu, so it works off seeing whether your ground speed and AGL are exactly the same as a second ago, implying that you are paused or in the menu, and it does seem to work. Please let me know if it doesn't.

Changes are:

• Added sim pause detection for active pause or when escaped to the settings menu, which will now pause the app to stop making setting changes and to freeze any running FPS settling timer while the sim is paused. This should also improve stability for when exiting a flight as the app will have been paused before the user chooses to exit the flight, thus minimising app changes to MSFS settings. Note it does not work when stopped on the ground but that doesn't really matter as only initial TLOD and cloud quality changes can occur in this state anyway.
• Fixed major issue with certain TLOD Min, Max and Cloud Recovery TLOD setting combinations causing recursive loading of app settings resulting is a stack overflow and crashing the app.

 

 

Edited March 20, 20242 yr by Reset XPDR

54 minutes ago, Reset XPDR said:

New AutoFPS 0.4.3.3-test version is available here. @Cpt_PiettThe new auto pause on sim pause/menu may help with the 0 FPS issue you were having the other day when exiting a flight if it is still occurring.

Thanks, can't wait to try it out! In fact I'll be so brave/silly as to install it while at FL170 over Nice. 

EDIT: Earlier today logging worked, even though it was set to false. After changing to 0.4.3.3, it doesn't seem to, even when set to true (I closed AutoFPS before editing .config): 

<add key="LogSimValues" value="true" />

EDIT: Changed back to false, and it's working...

Edited March 20, 20242 yr by Cpt_Piett