17 minutes ago, mmcmah said:

Early on in the development of the app, Reset had to set it to not alter the TLOD while on the ground, because it would trigger blurry textures. Maybe once the DX12 blurry texture bug was resolved, Reset allowed the TLOD to change while on the ground, and this might now be causing excess blurring?

I have actually stopped using the app on a regular basis because I find that the frequent changing of TLOD yields more stutters than simply setting a TLOD of 200.

I might try it again to see if that's still the case, as I made that decision shortly after the most recent UK World Update.

I have zero stutters using the app, since it was released, especially on approach to large airports. Wouldn't fly without it.

48 minutes ago, mmcmah said:

Early on in the development of the app, Reset had to set it to not alter the TLOD while on the ground, because it would trigger blurry textures. Maybe once the DX12 blurry texture bug was resolved, Reset allowed the TLOD to change while on the ground, and this might now be causing excess blurring?

I don’t think it changes below the min altitude set. I think the blurry textures is simply due to too low TLOD (resolves with higher TLOD).

‘I’m still using AutoFPS every flight. No stutters when I use reasonable TLOD (usually max 400). I do get stutters with too much AI traffic though, but that’s a different issue.

I am reading this recent discussion about blurriness of ground textures when using AutoFPS and low TLOD with interest. In my VR flying, I don't seem to experience the issue but perhaps that's because VR is not as sharp as 2D in the first place.

As @Bobsk8suggests, I am also curious whether the issue happens when users manually set TLOD rather than using AutoFPS ie. is it the tool or is it just low TLOD no matter how it is being set - AutoFPS or not.

Edit: Just loaded a flight in 2D at RKSI stock scenery and tried TLOD 100 or 50 and Auto FPS on and off. While scenery distance changed between TLOD 100 and 50, ground texture quality looked the same to me, regardless of whether AutoFPS set it or not.

I also tried starting the same flight up in VR, first at TLOD 100 without AutoFPS running then started AutoFPS, which changed TLOD to 50 on the ground, while staring at the same spot on the ground textures from the cockpit and nothing changed ground texture quality-wise.

As such, I don't know what is going on with other users' observations. Perhaps it is only because I am going between 50 and 100 TLOD or because I am using a stock, instead of payware, airport?

 

 

Edited August 3, 20241 yr by Reset XPDR

3 hours ago, mmcmah said:

Maybe once the DX12 blurry texture bug was resolved, Reset allowed the TLOD to change while on the ground, and this might now be causing excess blurring?

The app still doesn't change TLOD on the ground, except when it initially sets it when you load in for the flight or if you change TLOD min in the app after this and it sets the new TLOD.

Edited August 3, 20241 yr by Reset XPDR

9 hours ago, Reset XPDR said:

As @Bobsk8suggests, I am also curious whether the issue happens when users manually set TLOD rather than using AutoFPS ie. is it the tool or is it just low TLOD no matter how it is being set - AutoFPS or not.

It happens with low TLOD with or without AutoFPS like in my screenshots a few posts up. Those were from default (handcrafted) Zürich.

Edited August 3, 20241 yr by Cpt_Piett

Inetersting. As I wrote, I am pretty sure that also some adn sceneries are unaffected regarding ground textures. Wondering why...

Doesn't O-LOD affect the textures on ground? I always use O-LOD 200 and T-LOD 80 on ground and I haven't noticed any difference in textures between T-LOD 80 and 200 using AUTO FPS.

2 minutes ago, Ixoye said:

Doesn't O-LOD affect the textures on ground?

Dont think so, because I have OLOD 200 set in above pictures and only TLOD changes have an effect

OLOD doesn’t affect textures, but airport objects. And it seems low TLOD affects textures differently at different airports. I haven’t tested this a lot though.

Edited August 3, 20241 yr by Cpt_Piett

On 8/3/2024 at 7:30 AM, mmcmah said:

Early on in the development of the app, Reset had to set it to not alter the TLOD while on the ground, because it would trigger blurry textures. Maybe once the DX12 blurry texture bug was resolved, Reset allowed the TLOD to change while on the ground, and this might now be causing excess blurring?

Just did a quick and dirty test build that allows AutoFPS to change TLOD on the ground and it doesn't seem to trigger ground texture corruption anymore, so it does appear that Asobo finally fixed the DX12 ground texture corruption issue. I also didn't see any ground texture blurring as TLOD went up automatically from 50 to over 200.

Edited August 4, 20241 yr by Reset XPDR

I've done a few flights now in DX12 with the ground TLOD automation test function in action and it is working quite well. There was very minor texture flickering in a specific 1m square spot at PAJN but otherwise the ground textures have been well behaved at about 10 airports I've been to today.

I thought I might experience stutters with TLOD changing on the ground but, on my system at least, they seem to be negligible. This is hopefully due to the logic I have used where TLOD can only change at a high rate if you are stationary, but as soon as you start moving the rate of change gets limited to one TLOD per second.

There is minimal change to the UI when this mode is active in that "FPS Priority (Air & Gnd)" will now show at all times, not just in the air, to show you that it is active, as shown below. When not active you will otherwise see "FPS Priority (Air only)" to clearly differentiate the two modes.

While I was under the hood, I also updated the installer to update V7 dot net and mobisim wasm to the latest versions, namely 7.0.20 and 1.01 respectively. My dot net was already up to date but my mobisim wasm wasn't and the updated version is working just fine.

While I have the app open for minor changes, is there any issue with existing functionality that I should be looking at to fix? Also, can someone tell me whether the app works with the lossless scaling app, which I don't have, by showing the correct FPS when it is active or do users just have to factor in a doubling of FPS like they initially had to do before I worked out how to display FG FPS correctly? If the latter, I may just get the lossless scaling app and see if I can get it working properly.

47 minutes ago, Reset XPDR said:

there any issue with existing functionality that I should be looking at to fix?

Hi and thanks again for a vital app! Not an issue but I keep forgetting to load GPUz before my flight for monitoring. Is it possible to auto start this by selecting the exe in your app somewhere? Wouldn't need a gui we could put it in an ini file or equivalent. We could even put it in the same directory as afps if that helps! Would be nice if the app indicated in some way also that it WAS connected to and  reading info from GPUz. If I'm missing something obvious I apologise! 

I'll crawl back in my hole now lol 😎

Edited August 5, 20241 yr by sloppysmusic
Tippo

49 minutes ago, sloppysmusic said:

I keep forgetting to load GPUz before my flight for monitoring. Is it possible to auto start this by selecting the exe in your app somewhere?

GPU-Z can be auto-started, minimised to the system tray, when Windows starts from within GPU-Z settings itself and has a negligible system overhead, as shown below. That's how I do it and I don't have to worry about it at all.

 

49 minutes ago, sloppysmusic said:

Would be nice if the app indicated in some way also that it WAS connected to and  reading info from GPUz.

AutoFPS does indicate it is connected to GPU-Z by showing the GPU load in the app status line. It only tells you that you are not running it if you are not currently running it and have chosen GPU load as the the Cloud Quality activation method. Otherwise GPU-Z is optional hence no explicit connection message.

Edited August 5, 20241 yr by Reset XPDR

1 hour ago, sloppysmusic said:

 I keep forgetting to load GPUz before my flight for monitoring. Is it possible to auto start this by selecting the exe in your app somewhere?
😎

 

19 minutes ago, Reset XPDR said:

GPU-Z can be auto-started, minimised to the system tray, when Windows start

 

Alternatively, if using Addons Lineker, you can set any exe to run with MSFS, even adding a delayed start if desired.

3 hours ago, Reset XPDR said:

I've done a few flights now in DX12 with the ground TLOD automation test function in action and it is working quite well. There was very minor texture flickering in a specific 1m square spot at PAJN but otherwise the ground textures have been well behaved at about 10 airports I've been to today.

I thought I might experience stutters with TLOD changing on the ground but, on my system at least, they seem to be negligible. This is hopefully due to the logic I have used where TLOD can only change at a high rate if you are stationary, but as soon as you start moving the rate of change gets limited to one TLOD per second.

There is minimal change to the UI when this mode is active in that "FPS Priority (Air & Gnd)" will now show at all times, not just in the air, to show you that it is active, as shown below. When not active you will otherwise see "FPS Priority (Air only)" to clearly differentiate the two modes.

While I was under the hood, I also updated the installer to update V7 dot net and mobisim wasm to the latest versions, namely 7.0.20 and 1.01 respectively. My dot net was already up to date but my mobisim wasm wasn't and the updated version is working just fine.

While I have the app open for minor changes, is there any issue with existing functionality that I should be looking at to fix? Also, can someone tell me whether the app works with the lossless scaling app, which I don't have, by showing the correct FPS when it is active or do users just have to factor in a doubling of FPS like they initially had to do before I worked out how to display FG FPS correctly? If the latter, I may just get the lossless scaling app and see if I can get it working properly.

Any idea when this new (beta)version will be released ?

Btyw : Losless Scaling is working great here ( 4080 and 4090 )