15 minutes ago, Reset XPDR said:

In the two screenshots where you said you were having the issue, your auto method was set to FPS Tolerance mode and 20% which is why you were having the problem. In your most recent screenshot, your auto method changed to FPS Sensitivity which is why it started working again, even with a sensitivity setting of 20. As the name suggests, FPS Tolerance needs an FPS tolerance to be breached whereas FPS sensitivity does not. In short, stick with FPS sensitivity with your stated use case.

Thank you. Will do.

New test version 0.4.2.17-test4 is now available here. Feedback welcome as always.

Changes since v0.4.2.17-test3:

• TLOD Extra for Mountains settings added to the UI
  • Enabling/disabling via checkbox reveals/collapses additional settings. Disabled by default.
  • Separate settings allowable for VFR and IFR modes.
  • Added 10 second smoothing of terrain altitude measurement to stop rapid activation/deactivation of this feature when skirting the altitude threshold.
• TLOD Changes on Ground refinements based on extensive flight testing.
  • TLOD will rapidly change to seek target FPS then will require larger deviations to change further.
  • On takeoff and descending on approach through 1000 ft, TLOD will automatically reduce by 25% in anticipation of likely FPS drops.
  • TLOD will otherwise not change above 5 kts on the ground.
  • Up to 1000 ft, TLOD reductions will be larger and easier to trigger than increases as reductions less impact on associated stutters that may be introduced.

TLOD Extra for Mountains disabled (default)

 

TLOD Extra for Mountains enabled

1 hour ago, Reset XPDR said:

TLOD Extra for Mountains settings added to the UI

• Enabling/disabling via checkbox reveals/collapses additional settings. Disabled by default.
• Separate settings allowable for VFR and IFR modes.
• Added 10 second smoothing of terrain altitude measurement to stop rapid activation/deactivation of this feature when skirting the altitude threshold.

 

Thanks so much for this! Will test later today 😄

4 hours ago, Reset XPDR said:

New test version 0.4.2.17-test4 is now available here. Feedback welcome as always.

Changes since v0.4.2.17-test3:

• TLOD Extra for Mountains settings added to the UI
  • Enabling/disabling via checkbox reveals/collapses additional settings. Disabled by default.
  • Separate settings allowable for VFR and IFR modes.
  • Added 10 second smoothing of terrain altitude measurement to stop rapid activation/deactivation of this feature when skirting the altitude threshold.
• TLOD Changes on Ground refinements based on extensive flight testing.
  • TLOD will rapidly change to seek target FPS then will require larger deviations to change further.
  • On takeoff and descending on approach through 1000 ft, TLOD will automatically reduce by 25% in anticipation of likely FPS drops.
  • TLOD will otherwise not change above 5 kts on the ground.
  • Up to 1000 ft, TLOD reductions will be larger and easier to trigger than increases as reductions less impact on associated stutters that may be introduced.

TLOD Extra for Mountains disabled (default)

 

TLOD Extra for Mountains enabled

Brilliant! Will test later as well.

You’re the best!

MSFS Compatability Test Failed.  App Disabled (latest version).  See Readme to resolve. But not sure what I've done wrong here?  

2 hours ago, Langeveldt said:

MSFS Compatability Test Failed.  App Disabled (latest version).  See Readme to resolve. But not sure what I've done wrong here?  

Same problem here, with latest test version 4

Been doing some testing with the latest Test version, but haven't gotten the error others are reporting. Just did a flight from EDDH-EDDM. It worked very well, but there still may be some issues with Alt TLOD  Base 0, especially with areas that have Photogrammetry (haven't tried with PG disabled). With the camera stationary, FPS stabilize and the TLOD increases to maintain the FPS target, no surprises there. The issues start when you look around (up & down, left & right) while getting set up during preflight. Since the TLOD is variable, it induces stuttering...similar to how SU5 didn't have the PreCache option, so it was culling stuff out of view, but as soon as you looked around, it had to quickly load in and caused stuttering. This is basically what's happening, but in reverse. I decided to revert back to ALT Base of 700.

I've also been trying to dial in the Target PC FPS...Using LSFG I'll set a target of 54, native FG I've been using 65. As much as I love LSFG, I'd like to run smooth without it because it can still cause issues sometimes. I'd really like to use 80 as a Target with native FG, but the TLOD reduction is too much to be worth it, especially with traffic.

Also been tossing around the idea of starting to increase or decrease the FPS Sensitivity to see if that helps with Alt TLOD Base.

5 hours ago, Langeveldt said:

MSFS Compatability Test Failed.  App Disabled (latest version).  See Readme to resolve. But not sure what I've done wrong here?  

 

3 hours ago, Jac_49 said:

Same problem here, with latest test version 4

 

Very strange, since I haven't gone anywhere near the code that checks this for months. Can you guys message me your log file relating to when this happened so I can look into it. Thanks.

1 hour ago, V1ROTA7E said:

Been doing some testing with the latest Test version, but haven't gotten the error others are reporting. Just did a flight from EDDH-EDDM. It worked very well, but there still may be some issues with Alt TLOD  Base 0, especially with areas that have Photogrammetry (haven't tried with PG disabled). With the camera stationary, FPS stabilize and the TLOD increases to maintain the FPS target, no surprises there. The issues start when you look around (up & down, left & right) while getting set up during preflight. Since the TLOD is variable, it induces stuttering...similar to how SU5 didn't have the PreCache option, so it was culling stuff out of view, but as soon as you looked around, it had to quickly load in and caused stuttering. This is basically what's happening, but in reverse. I decided to revert back to ALT Base of 700.

I've also been trying to dial in the Target PC FPS...Using LSFG I'll set a target of 54, native FG I've been using 65. As much as I love LSFG, I'd like to run smooth without it because it can still cause issues sometimes. I'd really like to use 80 as a Target with native FG, but the TLOD reduction is too much to be worth it, especially with traffic.

Also been tossing around the idea of starting to increase or decrease the FPS Sensitivity to see if that helps with Alt TLOD Base.

Thanks for the feedback.

As you have discovered, TLOD changing on the ground with complex scenery can be quite stuttery if you switch between internal and external views, but especially when panning because there can be such a large FPS change doing so which induces TLOD to deviate. Nonetheless it should be a little bit better than previous test versions, especially after the first couple of minutes once a suitable TLOD FPS balance has been achieved for a given scenario. My suggestion is that if you do want to use this new feature that you only use it for VFR flights in simple scenery areas without FG and not use it on your IFR profile. Also, as you suggest, try different FPS sensitivity settings and see if that helps.

Re TLOD being too low for your target FPS, this is really an expectation issue of your system vs MSFS as all the app is really doing is automatically showing you what level of TLOD you need to achieve that desired target FPS, which you could also achieve manually without the app by adjusting TLOD in the settings yourself. As difficult as it may be to accept, if the graphics quality from too low a TLOD is not acceptable for a particular FPS target, then your FPS target is too high for what your system is capable of, despite you having some of the best hardware out there right now.

I've tested v0.4.2.17-test4 quite a bit today. GA flying over the European Alps, photogrammetry cities, the new enhanced Asobo airports. It's working really well. I think the new mountain logic didn't work initially as I had already set TLOD max to 975. So I basically didn't have any headroom for anything higher. Which is completely fine. Above TLOD 600 there's only a very subtle difference. Overall I'm really happy with the new changes. 

Edited August 23, 20241 yr by Cpt_Piett

5 hours ago, Reset XPDR said:

With the camera stationary, FPS stabilize and the TLOD increases to maintain the FPS target, no surprises there. The issues start when you look around (up & down, left & right) while getting set up during preflight. Since the TLOD is variable, it induces stuttering...similar to how SU5 didn't have the PreCache option, so it was culling stuff out of view, but as soon as you looked around, it had to quickly load in and caused stuttering. This is basically what's happening, but in reverse.

5 hours ago, Reset XPDR said:

Thanks for the feedback.

As you have discovered, TLOD changing on the ground with complex scenery can be quite stuttery if you switch between internal and external views, but especially when panning because there can be such a large FPS change doing so which induces TLOD to deviate. Nonetheless it should be a little bit better than previous test versions, especially after the first couple of minutes once a suitable TLOD FPS balance has been achieved for a given scenario.

I've thought a bit more on this and have the idea that instead of using the 5 second FPS rolling average like is used in all other modes. Following the initial rapid course TLOD adjustment, I could use a much longer longer FPS rolling average, say 30 seconds or a minute, for the remaining time on the ground so that it needs a much longer FPS change trend before adjusting TLOD again, meaning panning around shouldn't trigger a TLOD change so often. I'll try coding it up and see how it goes.

5 hours ago, Reset XPDR said:

As difficult as it may be to accept, if the graphics quality from too low a TLOD is not acceptable for a particular FPS target, then your FPS target is too high for what your system is capable of, despite you having some of the best hardware out there right now.

Are you saying I can't have the whole world??? 😂 You're absolutely right. Finding that keeping the difference between the base and top smaller induces far less stuttering. The Max + is an awesome feature.

I think that there might be a bug in -test4. I started in IFR and then switched to VFR after the climbout. Despite having enough FPS headroom, the program would increase the TLOD. However, as soon as I switched the focus AWAY from MSFS, it started increasing the TLOD. Once I clicked back in MSFS, the TLOD would freeze until I shifted focus again.

In the screenshot above, I had quit AutoFPS to then relaunch it to see if it would increase the TLOD.

This is what it looks like when I have shifted focus away from MSFS:

If I change the FPS Sensitivity from 20 to 10 nothing changes on the behavior. If I change it to 5, the program starts adjusting the TLOD while the focus is on MSFS.