Another test with no-expert mode. Did a number of touch n' go's at PHNL in the A300. I realized the payware airport scenery is heavy, and FSLTL has a bigger impact (hammers mainthread) than I originally thought. 

AutoFPS handles this very elegantly though. 

CapFrameX 17 min session at AGL 3000-0 around PHNL (heavy airport, lots of objects/buildings in the area)
avg fps 77.5
1% low avg 28.3
smooth 99.7% FTV <2ms 93.6%

Edited March 8, 20242 yr by Cpt_Piett

1 hour ago, captain420 said:

I've tried KLAX with samscene modern cities, and FSLTL AI and with this tool I get around 30fps. Even though I have it locked to 60fps in NVCP and AutoFPS target FPS set to 40.

Well I am lucky to get 35 FPS at KLAX without frame generation under similar circumstances with this app and even lower without it so I'd say you have an unrealistic expectation issue. FSLTL is the real killer here and you control its settings, not my app, so I suggest you look there.

Edited March 7, 20242 yr by Reset XPDR

7 minutes ago, Reset XPDR said:

Well I am lucky to get 35 FPS at KLAX without frame generation under similar circumstances with this app and even lower without it so I'd say you have an unrealistic expectation issue. FSLTL is the real killer here and you control its settings, not my app, so I suggest you look there.

I think you might misunderstand me. On the contrary, I'm very happy with the app. Without it the situation would be much worse (unless I keep TLOD at a constant 50 and clouds high). 

If you're getting 35fps native fps that'll be 70 FG-FPS. So we have similar performance in performance-heavy scenarios (also similar hardware). 

I'm only using CFX to judge performance with the app - and from what I've seen so far, it's stellar. 

Btw just before I posted in this thread, I posted this in another thread:

11 minutes ago, Cpt_Piett said:

Just a quick note on AI traffic impact. It can be significant (no surprise). FSLTL on hammers the mainthread (35ms). Off 24ms. 

Edited March 7, 20242 yr by Cpt_Piett

1 minute ago, Cpt_Piett said:

I think you might misunderstand me. On the contrary, I'm very happy with the app. Without it the situation would be much worse (unless I keep TLOD at a constant 50 and clouds high). 

If you're getting 35fps native fps that'll be 70 FG-FPS. So we have similar performance in performance-heavy scenarios (also similar hardware). 

I'm only using CFX to judge performance with the app - and from what I've seen so far, it's stellar. We're good?

That reply wasn't to you, it was to captain420. Check the log Captain! 😄

And yes, we are good 👍

5 minutes ago, Reset XPDR said:

That reply wasn't to you, it was to captain420. Check the log Captain! 😄

And yes, we are good 👍

Yeah, just realized 😄 I guess two Captains in one thread can be a bit confusing, lol.

@Reset XPDR should I check the log? Or the other Cpt? Been following the app in between flying, looks good hence I haven't checked the log 😅

Edited March 8, 20242 yr by Cpt_Piett

2 minutes ago, Cpt_Piett said:

Yeah, just realized 😄 I guess two Captains in one thread can be a bit confusing, lol.

@Reset XPDR should I check the log? Or the other Cpt? 😅

I thought you were an Admiral now. Well, at least until Luke Skywalker and his buddies showed up and ruined your day. 🤣

2 hours ago, Reset XPDR said:

I've been flying my latest test version, the only change in which is back to 5% default tolerance for non-expert mode rather than 2% in the last test version I published. I think 5% is better so I'll put out another test version shortly putting it back to that.

I think I might have seen you even had tolerance at 10% in one of the builds (yesterday whilst plowing through your readmes as I was fleeing from the RTFM monster)  

Edited March 8, 20242 yr by Cpt_Piett

15 minutes ago, Reset XPDR said:

I thought you were an Admiral now. Well, at least until Luke Skywalker and his buddies showed up and ruined your day. 🤣

Please don't remind me of Vader's son (sorry for the spoiler!) Him and his pitiful rebel buddies brought down the mighty Executor. Not my best day 🤪

18 hours ago, Cpt_Piett said:

After getting the newest version I did an approach to KLAX in the A300 with yet another touch 'n go. TLOD and OLOD adjusted very gradually on descent, reaching TLOD 200 (got max 600) at 6000 AGL and OLOD 200 at 2000 AGL

2 hours ago, Cpt_Piett said:

Just landed in Honolulu in the A300. Interesting to see the TLOD Min dynamic "live". AGL 2000 TLOD 80-100 AGL 1000 TLOD 40-50. OLOD 200 constant IIRC. Clouds high. 

Curious difference between Honolulu yesterday and LAX today. Or the other way around. It might seem that PHNL is much heavier than LAX, which doesn't make much sense (both w/ FSLTL). Perhaps TLOD min dynamic was not active yesterday, due to a different test build. These new builds keep popping up like Ewoks in the jungle. Not complaining though - every new version seems to bring new features and improvements. 

Edited March 8, 20242 yr by Cpt_Piett

2 minutes ago, Cpt_Piett said:

Curious difference between Honolulu yesterday and LAX today. Or the other way around. It might seem that PHNL is much heavier than LAX, which doesn't make much sense (both w/ FSLTL). Perhaps TLOD min dynamic was not active yesterday, due to a different test build. These new builds keep popping up like Ewoks in the jungle. Not complaining though - every new version seems to bring new features and improvements. 

TLOD Min dynamic has been out for 21 hrs, so the paint is still fresh but it looks like both of those flights were with this new feature.

The way to definitely tell it is working is to know what your TLOD is before the app starts changing it (see the log file for the saved TLOD setting) and your default TLOD Min will be half of that. If you are on the ground and your FPS is at least 15% better than your target FPS, then that TLOD Min should bump up to your originally saved TLOD. Similar for on approach, but this time it will be using the boosted TLOD Min until such time as your FPS gets lower than the 5% FPS tolerance threshold when it will switch to the original TLOD Min of 50% of your default.

In short, if FPS conditions are great for departure or arrival, you'll get a boosted FPS Min for those applicable flight phases.

eg. My default TLOD in VR is 100, which means TLOD Min defaults to 50 and that's what I see whenever I start a flight. If after the settling time FPS conditions are great, it will step up to 100 immediately and stay there for the departure. On arrival, it will start out using my boosted TLOD Min of 100 for the approach but if performance is sketchy, it will change TLOD Min back down to 50. You will only know this for sure when you hit 1000 ft and TLOD locks in.

How it works in practice is like a group flight I did today from Winslow Arizona to Phoenix. At the start, FPS conditions were great so I had TLOD Min of 100 on the ground and for most of the flight until we descended in to Phoenix, where the heavy FG scenery took its toll and my TLOD Min switched back to 50 for the landing, without me even noticing the transition (which is gradual BTW as TLOD Min is a target on approach not your actual TLOD on the start of that approach).

I hope that explains it better.

29 minutes ago, Reset XPDR said:

The way to definitely tell it is working is to know what your TLOD is before the app starts changing it (see the log file for the saved TLOD setting) and your default TLOD Min will be half of that.

I'm thinking it's possible that my TLOD pre app start 19hrs ago was 600 (I'm assuming you are referring to the MSFS graphics settings). Today it might have been lower. If TLOD min was half of that, it could explain the much lower TLOD min today. Does that make sense?

29 minutes ago, Reset XPDR said:

where the heavy FG scenery took its toll and my TLOD Min switched back to 50 for the landing, without me even noticing the transition (which is gradual BTW as TLOD Min is a target on approach not your actual TLOD on the start of that approach).

It might have been what I experienced today on approach to PHNL. TLOD min did go as low as 40. No stutters though, so it seems the change is very gradual, as you mention. 

I'll do another TLOD min evaluation once I finish updating to the latest beta build (need to update cache, takes forever to load into the flight). This time I'll make sure TLOD before app-start is 600. 

Edited March 8, 20242 yr by Cpt_Piett

@Cpt_PiettI'll put out a more instrumented test version shortly so you can see what's going on better.

New Test Version 08Mar240150Z here:

• Fixed Cloud Recovery TLOD not being calculated correctly when the new auto TLOD Min activates the increased TLOD Min.
• Added display of test data to show TLOD Min behaviour when using the new auto TLOD Min in non-expert mode feature.

To everyone testing the improved non-expert setting behaviour, please make sure you have set realistic TLOD and OLOD values for your MSFS defaults, as that is what non-expert mode bases its automation upon. eg TLOD Min will be half of what your default TLOD is and if that is very high, your TLOD Min might never be low enough. You can still use your custom TLOD and OLOD ranges with the app in the expert settings area.

Edited March 8, 20242 yr by Reset XPDR

2 hours ago, Reset XPDR said:

@Cpt_PiettI'll put out a more instrumented test version shortly so you can see what's going on better.

Thanks! Got a bit sidetracked with some issues after updating to the latest SU15 beta. I've just installed 08Mar240150Z, just need to sort out some issues first. 

A quick teaser of the final addition I will likely make to AutoFPS 0.4.2 that I mentioned a few weeks ago here, to bring true auto FPS to the MSFS world. If this works, it will change the app from "set and forget" to just "start it up" - no setting required! 😄