10 hours ago, somiller said:

I notice this issue with taxiway lines - at almost all airports with TLOD 50 the taxiway lines are blurry; increase TLOD to 100 moves the blur further out but still visible at most airports. It would be nice if developers would treat these lines as special cases in scenery addons because the effect is SO jarring.

The lines are tied to the MSFS ground resolution at that location.  This information is in the SDK.  It doesn’t matter how high resolution the developer makes the texture if you decrease the TLOD then you’re going to end up with blurry lines and textures on the ground.  Truthfully devs using anything other than 512x512 textures for lines and ground markings is usually overkill because if you use a 2048x2048 it’s not going to show up in that resolution.  Whatever the resolution is for the ground at the airport in the sim is all you can get out of it.  I build airports and this is well known in the 3rd party dev community.  It’s possible MSFS2024 will change this behavior but that is why you are seeing it everywhere and the 3rd party devs cannot fix it.

1 hour ago, thetford569 said:

Whatever the resolution is for the ground at the airport in the sim is all you can get out of it.  I build airports and this is well known in the 3rd party dev community.

Thanks, this makes sense. Nothing to do with AutoFPS then, and highly dependent on 3rd party dev. 

Btw completed a flight with latest update, LHBP-LIMC, minimal stutters. I don't use the TLOD change at ground level feature. I know this is going to sound crazy, but I wish AutoFPS would allow me to use higher TLODs over mountain ranges e.g. the alps, as the terrain draw distance and mesh resolution at higher TLODs + higher altitude makes a big difference. But unfortunately, at higher than about TLOD 400, AutoFPS struggles maintaining target FPS. Not a big issue,, and I'm probably in the minority for running crazy high TLODs. 

Edited August 22, 20241 yr by Cpt_Piett

Ok i. Set cppc to driver how do i know its working?

 

It is in task manager but its 0 cpu load.

Thanks

Mike

 

1 hour ago, Cpt_Piett said:

I know this is going to sound crazy, but I wish AutoFPS would allow me to use higher TLODs over mountain ranges e.g. the alps, as the terrain draw distance and mesh resolution at higher TLODs + higher altitude makes a big difference.

Because you've been so helpful in the development of this app, I'm willing to implement this for you but I'm not really sure how to. I could have the app compare AGL with actual altitude and trigger a higher TLOD (by how much?) if the difference is greater than a minimum threshold difference, say 10000 ft. What do you think?

40 minutes ago, Reset XPDR said:

Because you've been so helpful in the development of this app, I'm willing to implement this for you but I'm not really sure how to. I could have the app compare AGL with actual altitude and trigger a higher TLOD (by how much?) if the difference is greater than a minimum threshold difference, say 10000 ft. What do you think?

That's nice of you to offer to accommodate the request, but I too thought the same when I read it. It's not that simple (for example, you might not be 10000 ft over Everest). Also, the altitude you are above the mountains might be better on occasion to be a bit lower, as you might be wanting to get as much detail as you can. This is something that should already be able to be done with the normal settings that we have. If your max TLOD is set at an altitude that is low enough to cover your flying over the mountains, you should have max TLOD when you do so.

2 minutes ago, mmcmah said:

That's nice of you to offer to accommodate the request, but I too thought the same when I read it. It's not that simple (for example, you might not be 10000 ft over Everest). Also, the altitude you are above the mountains might be better on occasion to be a bit lower, as you might be wanting to get as much detail as you can. This is something that should already be able to be done with the normal settings that we have. If your max TLOD is set at an altitude that is low enough to cover your flying over the mountains, you should have max TLOD when you do so.

When I said 10000 ft difference I meant say you were cruising over Everest at 35000 ft and Everest is 28000 ft, then your AGL will be 7000 ft so the difference between it and your cruise ALT is 28000 ft so you are well above the 10000 ft threshold ie. the app can easily work out current terrain elevation knowing current ASL and AGL. It shouldn't take long to whip up a quick test version using settings in the config file to trial this.

4 hours ago, Cpt_Piett said:

I know this is going to sound crazy, but I wish AutoFPS would allow me to use higher TLODs over mountain ranges e.g. the alps, as the terrain draw distance and mesh resolution at higher TLODs + higher altitude makes a big difference. But unfortunately, at higher than about TLOD 400, AutoFPS struggles maintaining target FPS. Not a big issue,, and I'm probably in the minority for running crazy high TLODs. 

Thinking a bit more about this, why don't you just set TLOD Max to a ridiculously high value in the first place so that, regardless of whether you are flying over mountains or not, TLOD can free range up to whatever your system is capable of? What do you mean by AutoFPS struggles to maintain target FPS above TLOD 400? It shouldn't make any difference what your TLOD max is set to as the auto TLOD will work within whatever target FPS you have set.

In any case, I have nearly finished up a trial test version with high alt terrain auto TLOD increase for you to try out, which I will post up shortly.

Really appreciate your work with this tool, it's truly been game changing. Out of curiosity, would you mind sharing the way you have yours set up? I've been pretty happy with how I've had it set up, but I know there's a bit more fine tuning that can be done on my end.

15 minutes ago, V1ROTA7E said:

Really appreciate your work with this tool, it's truly been game changing. Out of curiosity, would you mind sharing the way you have yours set up? I've been pretty happy with how I've had it set up, but I know there's a bit more fine tuning that can be done on my end.

 

My setup is fairly unique as I am running VR on a Quest 3 with motion reprojection on (like frame generation but for VR) with a locked frame rate of 40 FPS to give me 80 FPS in the headset. As a result, I mostly use auto TLOD mode rather than the main auto FPS functionality that everyone else uses and very conservative TLOD Min and Max of 50 and 100 respectively.

Edited August 22, 20241 yr by Reset XPDR

Thanks for sharing. Do you have any recommendations for flat panels? I tried setting Alt TLOD Base to "0" but was getting quite a few micro stutters as I descended (into EGCC)...it was basically 1 stutter per 10 LOD decrease. So I went back to Alt TLOD Base 700 ft.

27 minutes ago, V1ROTA7E said:

Thanks for sharing. Do you have any recommendations for flat panels? I tried setting Alt TLOD Base to "0" but was getting quite a few micro stutters as I descended (into EGCC)...it was basically 1 stutter per 10 LOD decrease. So I went back to Alt TLOD Base 700 ft.

With .test2 and Alt TLOD Base set to 0, you can still experience TLOD changes down to the ground but the FPS tolerance is doubled so it shouldn't happen too often. I see you are using FPS sensitivity mode, which is generally recommended to use pre-TLOD changes on ground being implemented, however I am now finding FPS tolerance mode behaves better when Alt TLOD Base set to 0. Also, TLOD changes down to the ground is best suited for VFR flights in non-complex areas, so it is not really suitable for IFR into complex scenery airports as the system load changes are too great as you near the airport. In any case, thanks for providing valuable input on this new functionality, which will feed in to the readme instructions on it.

As for recommended settings, they are very system and expectation dependent so I can't really offer anything concrete other than to use settings either side of what you were happy with before AutoFPS came along. eg. if you used to have TLOD set to 200, then TLOD Min of 100 and a TLOD Max of 400 would be most likely suitable.

 

Edited August 22, 20241 yr by Reset XPDR

26 minutes ago, Reset XPDR said:

Also, TLOD changes down to the ground is best suited for VFR flights in non-complex areas, so it is not really suitable for IFR into complex scenery airports as the system load changes are too great as you near the airport.

Ah! So that's what it was. Makes sense. The TLOD Base of 700 seems to work well. The TLOD gradually reduces to TLOD Min + X upon reaching 700 AGL and I have (overall) found it to be a very smooth transition with unnoticeable culling. I'm going to try FPS Tolerance (5%) with this combo, and see if anything improves or gets worse.

 

1 hour ago, Reset XPDR said:

In any case, I have nearly finished up a trial test version with high alt terrain auto TLOD increase for you to try out, which I will post up shortly.

Here is the latest AutoFPS test version v0.4.2.17-test3, which only adds the trial extra TLOD in mountainous areas functionality that @Cpt_Piettindicated he would like incorporated. This new functionality is disabled by default and requires editing of the config file to enable and configure it, so it is otherwise functionally identical to v0.4.2.17-test2 recently released and can be used without fear of confusion between the two versions for normal operation.

If anyone else is interested in trying out the trial extra TLOD in mountainous areas functionality, here are the instructions for it:

• Incorporated trial code, which is disabled by default, to trigger additional TLOD at higher ground elevations, namely mountain regions.
  • Applicable only with FPS Sensitivity and FPS Tolerance TLOD automation methods.
  • Enabled by editing the config file and changing the TLODExtraMtnsTriggerAlt key value to a terrain altitude above which you wish the extra TLOD to be applied.
    • Default is 100000 ft, which effectively disables the feature for any aircraft that can't fly this high (ie. pretty much everything except Darkstar and SR-71).
    • Recommend trying a value somewhere between 5000-10000 ft.
  • The TLODExtraMtnsAmount key sets the additional TLOD amount your existing TLOD Max will increase by. Default is +400.
  • When active, you will see "Mtns +XXX" in the app status line where XXX is TLODExtraMtnsAmount, and TLOD will be allowed to increase up by this extra amount should sufficient FPS headroom exist above your FPS target.

Edited August 22, 20241 yr by Reset XPDR

Come to think of it, a really neat feature would be to increase the TLOD + value to a numerical value instead of the blanket +50. That way, my Base could be 100, and (performance permitting) the overshoot could be say +100 or +105, etc. Then it could potentially interpolate the value with an FPS percentage. i.e. If the FPS value drops below target by 5%, TLOD gets reduced by 25, if after 5 seconds the target is not within %5, it'll drop another 25. Don't want to make things too complicated, it's just when departing airports with mountains around, the TLOD can look like melted ice cream, so having the option to still have it be increased further while on the ground, performance permitting, would be awesome. Hope all that makes sense.

2 hours ago, V1ROTA7E said:

Come to think of it, a really neat feature would be to increase the TLOD + value to a numerical value instead of the blanket +50. That way, my Base could be 100, and (performance permitting) the overshoot could be say +100 or +105, etc. Then it could potentially interpolate the value with an FPS percentage. i.e. If the FPS value drops below target by 5%, TLOD gets reduced by 25, if after 5 seconds the target is not within %5, it'll drop another 25. Don't want to make things too complicated, it's just when departing airports with mountains around, the TLOD can look like melted ice cream, so having the option to still have it be increased further while on the ground, performance permitting, would be awesome. Hope all that makes sense.

What you are describing is essentially what TLOD changes on ground already does, whereby it rapidly ramps up TLOD until in target FPS range then slows right down and becomes less reactive once it gets there. If the only issue you were having was TLOD changing on final descent, it is easy for me to block out TLOD changes in this phase of flight, say below 1000 ft.