31 minutes ago, Sonosusto said:

Hey I tried the new test version 6. VFR only in lower population areas (TJSJ to MDPP payware) and it worked well in non-expert mode. Still, a lot of stutters upon final landing though. Less the sim or app, and more likely my hardware 

AI traffic (especially bgl) can cause loading stutters. Airports can do it too. Even with the best hardware. I get a few here and there, but nothing as bad as I did with P3D or FSX.

Edited August 31, 20241 yr by CFIJose

7 minutes ago, CFIJose said:

AI traffic (especially blg) can cause loading stutters. Airports can do it too. Even with the best hardware. I get a few here and there, but nothing as bad as I did with P3D or FSX.

Yeah this happens with everything turned off. Though you make a good point. thanks for the feedback. i was thinking this...

The app slowly tunes up TLOD on take off but seems to retain a higher TLOD on approach/final.

Is there a way to have tuned down so my poor cpu isnt trying to dial back thr tlod in final? or is this just me?

Edited August 31, 20241 yr by Sonosusto

15 minutes ago, Sonosusto said:

Yeah this happens with everything turned off. Though you make a good point. thanks for the feedback. i was thinking this...

The app slowly tunes up TLOD on take off but seems to retain a higher TLOD on approach/final.

Is there a way to have tuned down so my poor cpu isnt trying to dial back thr tlod in final? or is this just me?

Those pauses will happen without autofps. So, it's not the ap or your system. It's just ms flightsims. Those micro pauses have happening forever. I never saw them on XP sims. Maybe 2024 will render scenery with multi core support and we can finally see less stutters when add-on scenery or AI are present. Some with faster systems claim, they don't exist. I have to see it to believe it.

Just now, CFIJose said:

Those pauses will happen without autofps. So, it's not the ap or your system. It's just ms flightsims. Those micro pauses have happening forever. I never saw them on XP sims. Maybe 2024 will render scenery with multi core support and we can finally see less stutters when add-on scenery or AI are present. Some with faster systems claim, they don't exist. I have to see it to believe it.

yeah. hopefully. i was thinking maybe there's a way to tune down the tlod in advance of the approach without using expert settings

or maybe its because I gave up using expert settings because it makes my fps worse haha

Just now, Sonosusto said:

yeah. hopefully. i was thinking maybe there's a way to tune down the tlod in advance of the approach without using expert settings

or maybe its because I gave up using expert settings because it makes my fps worse haha

I think it has to do more with distance & aircraft speed. Slow down early, load scenery far away.

Just completed a shared cockpit flight in the Fenix A320 with a friend. Flight plan LDRI to LSZH i.e. over the Alps. Several times during the flight, my friend had TLOD increasing too much, causing FPS to fall as low as 13 and stutters. It seemed AutoFPS was targeting TLOD and not FPS. 

His settings:

His log file below. It probably includes yesterday's flight as well. He did change the Target FPS at some stage, and eventually set it to AutoTarget. 

https://drive.google.com/file/d/1Bg3WD3xyjg9pV2Nygg-2MDHY7bLbNzvH/view?usp=sharing

His hardware: 

Edited August 31, 20241 yr by Cpt_Piett

9 hours ago, Cpt_Piett said:

Just completed a shared cockpit flight in the Fenix A320 with a friend. Flight plan LDRI to LSZH i.e. over the Alps. Several times during the flight, my friend had TLOD increasing too much, causing FPS to fall as low as 13 and stutters. It seemed AutoFPS was targeting TLOD and not FPS. 

His settings:

His log file below. It probably includes yesterday's flight as well. He did change the Target FPS at some stage, and eventually set it to AutoTarget. 

https://drive.google.com/file/d/1Bg3WD3xyjg9pV2Nygg-2MDHY7bLbNzvH/view?usp=sharing

His hardware: 

Looks like TLOD Min Extra was calculated too high because the FPS target was so low, which is an issue I uncovered yesterday when I tried the new TLOD Min Extra logic out on my 3060 laptop yesterday. In your friend's case it is exacerbated because his MSFS settings look quite ambitious for his level of hardware and very low FPS targets are hard for the app to work with. I suggest he turns his settings down and perhaps not use TLOD Min Extra until I sort out lower end hardware behaviour.

15 hours ago, Cpt_Piett said:

Just made a touch and go at LIPB Bolzano in the Fenix A320. Airport is at 787ft surrounded by the Alps. On final approach, TLOD was quite low (240) even though I had enough headroom. Also the Mtn logic went on and off as I was overflying valleys then mountains and so on. Looking at the approach chart for LOC DME RWY 01 and this makes sense. 

At the departure airport of Venice Lipz (sea level) I was getting a TLOD of 400 i.e. TLOD Min Extra was active. 

Questions:

• Should the Mtn logic be active for longer - to avoid it going off too soon when overflying valleys? It will take quite a while for TLOD to increase again when the Mtn logic is active again
• Did TLOD (with get TLOD Min Extra) get too low on descent even though I had enough headroom?

Note: this is not criticism, just observations. Just trying to understand the new logic.

Settings:

Part of log file (touchdown in bold):

2024-08-31 20:00:12.053 [INF] [ LODController:UpdateVariables    ] FPS: 102 FGAct: True Pri: TLOD TLOD: 298 OLOD: 179 AGL: 1485 FPM: -38 Clouds: Ultra 
2024-08-31 20:00:22.164 [INF] [ LODController:UpdateVariables    ] FPS: 101 FGAct: True Pri: TLOD TLOD: 311 OLOD: 167 AGL: 2328 FPM: -117 Clouds: Ultra 
2024-08-31 20:00:32.279 [INF] [ LODController:UpdateVariables    ] FPS: 93 FGAct: True Pri: TLOD TLOD: 371 OLOD: 158 AGL: 1830 FPM: -186 Clouds: Ultra 
2024-08-31 20:00:42.391 [INF] [ LODController:UpdateVariables    ] FPS: 93 FGAct: True Pri: TLOD TLOD: 373 OLOD: 149 AGL: 2034 FPM: -1078 Clouds: Ultra 
2024-08-31 20:00:52.500 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 292 OLOD: 191 AGL: 1163 FPM: -2308 Clouds: Ultra 
2024-08-31 20:01:02.612 [INF] [ LODController:UpdateVariables    ] FPS: 100 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 872 FPM: -2001 Clouds: Ultra 
2024-08-31 20:01:12.727 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 263 OLOD: 188 AGL: 1578 FPM: -2041 Clouds: Ultra 
2024-08-31 20:01:22.835 [INF] [ LODController:UpdateVariables    ] FPS: 92 FGAct: True Pri: TLOD TLOD: 321 OLOD: 179 AGL: 1394 FPM: -929 Clouds: Ultra 
2024-08-31 20:01:32.946 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 292 OLOD: 185 AGL: 1226 FPM: -206 Clouds: Ultra 
2024-08-31 20:01:43.053 [INF] [ LODController:UpdateVariables    ] FPS: 99 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 726 FPM: -31 Clouds: Ultra 
2024-08-31 20:01:53.165 [INF] [ LODController:UpdateVariables    ] FPS: 100 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 914 FPM: 50 Clouds: Ultra 
2024-08-31 20:02:03.293 [INF] [ LODController:UpdateVariables    ] FPS: 88 FGAct: True Pri: TLOD TLOD: 288 OLOD: 188 AGL: 1306 FPM: -60 Clouds: Ultra 
2024-08-31 20:02:13.405 [INF] [ LODController:UpdateVariables    ] FPS: 95 FGAct: True Pri: TLOD TLOD: 289 OLOD: 188 AGL: 1228 FPM: -547 Clouds: Ultra 
2024-08-31 20:02:23.518 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 258 OLOD: 194 AGL: 1069 FPM: -1400 Clouds: Ultra 
2024-08-31 20:02:33.629 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 818 FPM: -1482 Clouds: Ultra 
2024-08-31 20:02:43.739 [INF] [ LODController:UpdateVariables    ] FPS: 97 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 560 FPM: -1363 Clouds: Ultra 
2024-08-31 20:02:53.849 [INF] [ LODController:UpdateVariables    ] FPS: 96 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 443 FPM: -270 Clouds: Ultra 
2024-08-31 20:03:03.960 [INF] [ LODController:UpdateVariables    ] FPS: 94 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 395 FPM: -121 Clouds: Ultra 
2024-08-31 20:03:14.073 [INF] [ LODController:UpdateVariables    ] FPS: 90 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 306 FPM: -838 Clouds: Ultra 
2024-08-31 20:03:24.181 [INF] [ LODController:UpdateVariables    ] FPS: 87 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 219 FPM: -799 Clouds: Ultra 
2024-08-31 20:03:34.310 [INF] [ LODController:UpdateVariables    ] FPS: 82 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 37 FPM: -757 Clouds: Ultra 
2024-08-31 20:03:44.433 [INF] [ LODController:UpdateVariables    ] FPS: 86 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 10 FPM: -2 Clouds: Ultra 
2024-08-31 20:03:54.545 [INF] [ LODController:UpdateVariables    ] FPS: 86 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 35 FPM: 725 Clouds: Ultra 
2024-08-31 20:04:04.657 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 240 OLOD: 200 AGL: 497 FPM: 3222 Clouds: Ultra 
2024-08-31 20:04:14.782 [INF] [ LODController:UpdateVariables    ] FPS: 105 FGAct: True Pri: TLOD TLOD: 246 OLOD: 200 AGL: 1086 FPM: 3581 Clouds: Ultra 
2024-08-31 20:04:24.895 [INF] [ LODController:UpdateVariables    ] FPS: 96 FGAct: True Pri: TLOD TLOD: 306 OLOD: 170 AGL: 1685 FPM: 3284 Clouds: Ultra 
2024-08-31 20:04:35.005 [INF] [ LODController:UpdateVariables    ] FPS: 92 FGAct: True Pri: TLOD TLOD: 366 OLOD: 152 AGL: 2066 FPM: 1875 Clouds: Ultra 
2024-08-31 20:04:45.115 [INF] [ LODController:UpdateVariables    ] FPS: 92 FGAct: True Pri: TLOD TLOD: 400 OLOD: 137 AGL: 2394 FPM: 1958 Clouds: Ultra 
2024-08-31 20:04:55.223 [INF] [ LODController:UpdateVariables    ] FPS: 98 FGAct: True Pri: TLOD TLOD: 400 OLOD: 122 AGL: 2732 FPM: 2013 Clouds: Ultra 
2024-08-31 20:05:05.334 [INF] [ LODController:UpdateVariables    ] FPS: 97 FGAct: True Pri: FPS TLOD: 400 OLOD: 104 AGL: 3125 FPM: 2680 Clouds: Ultra

EDIT: After Bolzano I did an approach into LSZH Zürich. Got the same on final approach i.e. TLOD+ 240 priority. So I guess this value is calculated at some point during the descent. 

Complete log file:https://drive.google.com/file/d/1TDZk8NhKdqPFoSY_hhATcjqzQAey1md4/view?usp=sharing

 

Re Mtn TLOD Extra turning on and off in valleys, I had a feeling this might end up happening so I will need to come up with either a time delay for turning it off, say X minutes after terrain elevation dropping below the trigger threshold, or a much lower off trigger altitude or just leave it on indefinitely once triggered on. Any preference?

Re The times you are getting TLOD Min of 240 correspond with when Mtn TLOD Extra is not active when your TLOD is sitting at TLOD Max of 400. The logic currently takes 40% off what TLOD you were getting at the time the app crosses from FPS Priority to TLOD Priority on descent and 40% off 400 is 240. The times when TLOD was dropping to 480 minimum was when Mtn TLOD Extra was active and it was 40% of 800 (400 + 400).

What I am finding really hard to code is how much to increase TLOD on the ground or decrease TLOD on decent when there is lots of headroom because the amount is very system and scenario dependent, so while I can tune it for my rig at one location it might be way off somewhere else and none of that may be right for someone else's system (as your friend found out). I am still pondering how to improve this, whether I come up with better formulas, try changing TLOD Min in smaller steps then waiting for FPS to stabilise or just scrapping the whole lot as too hard to get working across the variety of systems and settings out there.

I'll see what I can come up with in the next few days, but yes it currently far from perfect and I appreciate you, and others, pointing out where notable discrepancies are occurring.

Edited September 1, 20241 yr by Reset XPDR

13 hours ago, Sonosusto said:

yeah. hopefully. i was thinking maybe there's a way to tune down the tlod in advance of the approach without using expert settings

or maybe its because I gave up using expert settings because it makes my fps worse haha

Non-expert mode does turn down tlod in advance of the approach but it does it with your MSFS default settings, so if it is not low enough for landing you have your default setting too high.

2 hours ago, Reset XPDR said:

Re Mtn TLOD Extra turning on and off in valleys, I had a feeling this might end up happening so I will need to come up with either a time delay for turning it off, say X minutes after terrain elevation dropping below the trigger threshold, or a much lower off trigger altitude or just leave it on indefinitely once triggered on. Any preference?

@Cpt_PiettI've gone ahead and implemented in the next test build a 5 minute timer of being under the terrain elevation threshold before Mtn TLOD Extra will start gradually reducing by 10 TLOD per second until it has dwindled back to 0.

2 hours ago, Reset XPDR said:

I'll see what I can come up with in the next few days

I've come up with a progressive TLOD Min change on ground, like I had originally proposed, that seems to be working pretty well on my gaming laptop in a wide variety of scenarios and target FPSs. I'll test it on my main gaming rig tomorrow and see if it gets favourable results too.

1 hour ago, Reset XPDR said:

@Cpt_PiettI've gone ahead and implemented in the next test build a 5 minute timer of being under the terrain elevation threshold before Mtn TLOD Extra will start gradually reducing by 10 TLOD per second until it has dwindled back to 0.

I think this could be the best workaround for now - and better than the other options you suggested. Gradually reducing TLOD seems like a good idea as well. In my case I had TLOD gradually increasing from 400 to 800 once Mtn TLOD Extra kicked it, then suddenly going back to 400 once I was below the trigger altitude. 

My temporary workaround until the next test build is to lower Mtn Alt Min to e.g. 500ft.

3 hours ago, Reset XPDR said:

Re The times you are getting TLOD Min of 240 correspond with when Mtn TLOD Extra is not active when your TLOD is sitting at TLOD Max of 400. The logic currently takes 40% off what TLOD you were getting at the time the app crosses from FPS Priority to TLOD Priority on descent and 40% off 400 is 240. The times when TLOD was dropping to 480 minimum was when Mtn TLOD Extra was active and it was 40% of 800 (400 + 400).

Thanks for explaining - it makes perfect sense. I guess changing from 40% to say 20% would result in an excessive TLOD Min on final approach for many people. 

3 hours ago, Reset XPDR said:

What I am finding really hard to code is how much to increase TLOD on the ground or decrease TLOD on decent when there is lots of headroom because the amount is very system and scenario dependent, so while I can tune it for my rig at one location it might be way off somewhere else and none of that may be right for someone else's system (as your friend found out). I am still pondering how to improve this, whether I come up with better formulas, try changing TLOD Min in smaller steps then waiting for FPS to stabilise or just scrapping the whole lot as too hard to get working across the variety of systems and settings out there.

I can see the dilemma here. 

1 hour ago, Reset XPDR said:

I've come up with a progressive TLOD Min change on ground, like I had originally proposed, that seems to be working pretty well on my gaming laptop in a wide variety of scenarios and target FPSs. I'll test it on my main gaming rig tomorrow and see if it gets favourable results too.

I can't speak for everyone else, but I think I need to test this to better understand how it will work. 

Edited September 1, 20241 yr by Cpt_Piett

I've had a strange issue with the latest test version whilst parked on the ground. Even though I have more than enough headroom, I have stutters when panning around the cockpit. This resolves once I've climbed to a certain altitude. 

Example: I'm getting around 90 FPS and TLOD 400 (which is my TLOD max) with TLOD Min Extra active at Vienna Intl in the 737-600. TLOD doesn't change when climbing as I'm already at TLOD max. So it doesn't really make sense to me. The only thing I can think of is that panning around the cockpit puts too much load on the CPU temporarily, even though FPS is more than good enough. 

I'll test with a lower TLOD max and see if it's still the same. It's not a huge issue, just thought I'd mention it. 

EDIT: Just landed at LOWK Klagenfurt which is a low density area. With TLOD at 80, there's no stutters when panning. I think the issue is partly that I'm using custom views. So when changing from e.g. overhead panel to default cockpit view, I get stutters. Whereas when using the mouse to pan around, it's better. 

Edited September 1, 20241 yr by Cpt_Piett

8 hours ago, Cpt_Piett said:

11 hours ago, Reset XPDR said:

Re The times you are getting TLOD Min of 240 correspond with when Mtn TLOD Extra is not active when your TLOD is sitting at TLOD Max of 400. The logic currently takes 40% off what TLOD you were getting at the time the app crosses from FPS Priority to TLOD Priority on descent and 40% off 400 is 240. The times when TLOD was dropping to 480 minimum was when Mtn TLOD Extra was active and it was 40% of 800 (400 + 400).

Thanks for explaining - it makes perfect sense. I guess changing from 40% to say 20% would result in an excessive TLOD Min on final approach for many people. 

I think I might be able to improve this for cases like this. Rather than just take a blind 40% reduction, if you are sitting at TLOD Max at the time and have headroom, then I can do a similar, but only single, TLOD increase calculation to what I do on the ground and then take 40% off. ie. te 40% off takes into account any headroom that you have available. I'll put that in the new test build too.

 

7 hours ago, Cpt_Piett said:

I've had a strange issue with the latest test version whilst parked on the ground. Even though I have more than enough headroom, I have stutters when panning around the cockpit. This resolves once I've climbed to a certain altitude. 

Other than having really high TLOD on the ground, I'm not sure why this is happening. See if it still does it in the next test build, which I will release today.

 

8 hours ago, Reset XPDR said:

I think I might be able to improve this for cases like this. Rather than just take a blind 40% reduction, if you are sitting at TLOD Max at the time and have headroom, then I can do a similar, but only single, TLOD increase calculation to what I do on the ground and then take 40% off. ie. te 40% off takes into account any headroom that you have available. I'll put that in the new test build too.

I was a bit ambitious thinking I would get this working in a new test build today. I've been at it for a while and currently cannot stop the app toggling between FPS and TLOD priority modes at certain times, so I'll have another try tomorrow when my head is clearer.

On the good new front, I've managed to reduce the FPS settle time between TLOD Min Extra increases on the ground by replacing a set time span of 15-20 seconds, which was sometimes too long and sometimes not long enough, with FPS trend detection where it will detect when the FPS gets to its lowest point after increasing TLOD then will wait until FPS peaks after that and will then end the timer. This is much more dynamic and responsive that the set timer I was previously using and I plan to extend this to all settle timer functions so they are event not time triggered.

In summary, I have TLOD Min Extra seeking on the ground working quite well, TLOD Mtn Extra now working with a 5 minute deactivation timer and stepped reduction, FPS settling now event rather than time based, but TLOD Min Extra on descent currently eluding my muddled brain, which I will hopefully rectify tomorrow.

5 hours ago, Reset XPDR said:

In summary, I have TLOD Min Extra seeking on the ground working quite well, TLOD Mtn Extra now working with a 5 minute deactivation timer and stepped reduction, FPS settling now event rather than time based, but TLOD Min Extra on descent currently eluding my muddled brain, which I will hopefully rectify tomorrow.

This sounds very promising, looking forward to the next build!