On 8/16/2021 at 2:52 PM, Rogen said:

It's a memory value, the higher the value the more memory will be used to fetch textures, thus preventing textures loading and unloading.

My lowly 1070Ti manages with a setting of 640000.000000, higher than really needed... 320000.000000 is more a middle of the road value, that said I never see a black textured building and haven't for years and don't have stuttering in normal use as I'm vsync'd to 30 Hz for a very smooth 30fps and run a DSR screen mode of 2560 x 1440, infact in a lot of areas I can manage a 60 Hz vsync for 60 fps and occcasionly fly @ 4k DSR.

I'd suggest if there is stuttering then something is else overloading either the GPU or CPU. Perhaps it is a particular texture set - PBR tends to chew through video ram like a superchased v8 does on fuel. The best thing to do is to experiment with different values till a sweet spot is found and monitoring GPU and CPU use is an ideal way to see how much load a scenario is placing on either CPU or GPU and thus will act as a guide on managing settings.

Rob Ainscough's video on the use of MAX_TEXTURE_REQUEST_DISTANCE

Cheers

Now that Rob has established that it's a DISTANCE value what would be the right tuning range say for RTX 2080TI?

Thanks.

2 hours ago, Dirk98 said:

Now that Rob has established that it's a DISTANCE value what would be the right tuning range say for RTX 2080TI?

Hi Dirk,

Well I wouldn't say it's actually established what the value is given LM saying there is no cap to the value and to aggressively fetch textures use a value of one million, if the value was metres that would be 1000 KM, who knows... only LM and they are always short on comms.

I any case I'd say trial a few settings yourself, select a suitable airport (as Rob did in his video) and increase the value till you're satified things are both looking and performing good, I don't think you can go wrong as there are 2 other checks that must pass before textures are requested anyway.

1) Object is within the far clip distance. This varies by altitude.
2) Object pixel size at a given distance passes min radius check. This is configurable in 4.3+ using RS_MIN_OBJECT_PIXEL_RADIUS. (default is 2.0px)

Post back what you found to best suit yourself and what airport used would be handy for others to confirm.

I've going to leave mine as it is as its been no issue for myself.

Cheers

 

 

3 hours ago, Rogen said:

Well I wouldn't say it's actually established what the value is given LM saying there is no cap to the value and to aggressively fetch textures use a value of one million, if the value was metres that would be 1000 KM, who knows... only LM and they are always short on comms.

I'm 99% sure its the value in meters. I distinctly remember reading somewhere that the 1000 value meant 1km, and I always put it 32000 with the idea that I probably don't need textures to load further away than 32km out... For me, it's all about the takeoff and approach phases of the flight. When taxiing around EWR I want to be able to turn onto the runway and behold the NYC skyline, not a mess of blackness. This value helps to accomplish that. If you get stutters, the texture loading would certainly be a good candidate to the culprit, and so reducing the texture loading distance should help. For me, texture loading has almost always been associated with stutters.

23 minutes ago, Benjamin J said:

This value helps to accomplish that. If you get stutters, the texture loading would certainly be a good candidate to the culprit, and so reducing the texture loading distance should help. For me, texture loading has almost always been associated with stutters.

How to tune "the texture loading" then if using 32000 meters distance?

Thanks.

15 minutes ago, Dirk98 said:

How to tune "the texture loading" then if using 32000 meters distance?

Thanks.

Dirk, take notice, just in case, Rob_Ainscough uses 320000 not 32000

6 minutes ago, SergioN said:

Dirk, take notice, just in case, Rob_Ainscough uses 320000 not 32000

Benjamin J referred to his setting of 32000, so I asked him how would he adjust texture loading.

Thanks.

6 hours ago, Dirk98 said:

How to tune "the texture loading" then if using 32000 meters distance?

Thanks.

Reduce it, perhaps to 25000... It will probably take some trial and error to find the value that allows you to fly unencumbered by slow texture loading but not have stutters either. Of course the texture resolution you use will also impact this. I'm running at 1024.

On 8/24/2021 at 1:55 AM, Benjamin J said:

Reduce it, perhaps to 25000... It will probably take some trial and error to find the value that allows you to fly unencumbered by slow texture loading but not have stutters either. Of course the texture resolution you use will also impact this. I'm running at 1024.

So that was just about reducing MAX_TEXTURE_REQUEST_DISTANCE value say from your 32000 to 25000. I'll definitely try 32000 first with my medium range RTX 2080TI.

Thanks.

 

1 hour ago, Rob_Ainscough said:

Experiment with a value that works best for your specific hardware and accomplishes the goal of keeping textures loaded (aka not black).

I haven’t notice this value as being a source of long frames (stutters), if you exceed your VRAM it could triggers long frames.  Your 2080Ti should be more than capable.

Cheers Rob.

I use 320000 and don't have stutters. I did and the reason was Realturb products. Disabling this, totally got rid of the every 1 second stutter I was having.

I must add that the combination of Realturb + road vehicles was the stutter feast. Road vehicles to cero and realturb activated got rid of them too.

Edited August 25, 20214 yr by SergioN

To revive the thread a bit for those looking for an answer on that specific problem.

Have tried 32,000 and the results are positive: no texture loadings for example NYC area with DD scenery.

It is a must do adjustment in my book.

Tks Rob