I tried the following settings and my terminal buildings were either missing or transparent at ImagineSim KATL and KLGA. The SCENERY_DRAW_DISTANCE=64000.000000 was causing the problem. 

[GRAPHICS]
ENABLE_MEMORY_OPTIMIZATION=0
MAX_TEXTURE_REQUEST_DISTANCE=320000.000000

[SCENERY]
SCENERY_DRAW_DISTANCE=64000.000000

Edited November 30, 20187 yr by Wise87

25 minutes ago, Wise87 said:

The SCENERY_DRAW_DISTANCE=64000.000000 was causing the problem.

I doubt that was the problem unless you ran out of VRAM, that 64000 value is assigned thru standard P3D Graphics settings UI when you set to AG distance slide to all the way to the right ... the max value you can use is 128000 if you edit the prepar3d.cfg manually.

39 minutes ago, w6kd said:

32000 or 320000?

320000 is the value I've been using, sorry for any typo's.  But per LM's information, you can set this to 1000000, there is no limit.  I have no idea what the units of measure are for MAX_TEXTURE_REQUEST_DISTANCE ... here is Beau's (LM) exact words:

There's no cap on this value itself because it's intended as a limit. If you want textures requesting aggressively, you can set it something very high like 1000000. There are two other checks that must pass before textures are requested:
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 we made configurable in 4.3 using RS_MIN_OBJECT_PIXEL_RADIUS. (default is 2.0px)

Cheers, Rob.

Just out of curiosity is anyone using these tweaks and seeing any difference from not applying them? It’s always been preached to not tweak the settings and if LM wanted you to make changes it would be in the UI. 

2 hours ago, Wise87 said:

Just out of curiosity is anyone using these tweaks and seeing any difference from not applying them? It’s always been preached to not tweak the settings and if LM wanted you to make changes it would be in the UI. 

I've been trying them out this morning with my standard test flight around KLAX using TrackIR.  Take off from 25L, make a 20nm downwind over Long Beach and land 25R.  When I turn onto the crosswind over the Pacific and look left to the city all the autgen buildings are black and the textures pop after a couple of seconds.  But the FSDT KLAX is still fully visible, which is an improvement from before.  My VRAM usage is just under 9GB vs. 5GB before.  RAM is 10GB vs 8.5GB.

[GRAPHICS]
MAX_TEXTURE_REQUEST_DISTANCE=320000.000000
ENABLE_MEMORY_OPTIMIZATION=0

[TERRAIN]
TEXTURE_SIZE_EXP=10
UseGlobalTerrainView=True

My autogen settings were not maxed out for this test which was a leftover from previously having Orbx SoCal loaded, which is a frame killer and stutter inducer.  I'm going to re-run the test with only OpenLC NA and max autogen.

As soon as I look left:

After a couple of seconds:

Video showing autogen texture popping:

 

 

Edited November 30, 20187 yr by LRW
Added video showing autogen texture popping

Gonna be upgrading to 4.4 now.

Rob what about these 2 settings :

MaxRegionsPurgePerFrame=
POP_FREE_AUTOGEN=

Any recommendation what I should be setting these at?

My CPU is an AMD TR 2990WX No OC just Turbo Boost enable and HT off and SLI RTX 2080Tis. 32GB DDR4 Ram XMP 3200 CL14.

Thanks.

Edited November 30, 20187 yr by American 833 Heavy

On ‎11‎/‎29‎/‎2018 at 11:05 PM, Rob Ainscough said:

[DISPLAY]

MaintainSystemCopyOfDeviceTextures=0

MaintainSystemCopyOfDeviceTextures -- (Older) Present in earlier versions of P3D and defaults to 1, setting to 0 is primarily useful for multiple-GPUs so that copies of textures don't have to be pull from disk when needed 

As I read it it should be 0 with 1 GPU and 1 with multiple GPU's… ?

So why it has to be 1 with 1 GPU ?

 

Second question : 512 vs 1024 PR textures . Does it tax the CPU extra or just the GPU ?  

 

Regards, Gerard

 

33 minutes ago, GSalden said:

As I read it it should be 0 with 1 GPU and 1 with multiple GPU's… ?

So why it has to be 1 with 1 GPU ?

 

Second question : 512 vs 1024 PR textures . Does it tax the CPU extra or just the GPU ?  

 

Regards, Gerard

 

Hey Gerard, I run a 1080ti and have set TEXTURE_SIZE_EXP=10. So far, apart from longer loading times of scenarios, I have not seen any detrimental affect. I can see a noticeable difference in textures at distance and things look overall sharper. I am about to do a longer flight today, down to LOWI in the NGX so I will wait to see the outcome 😊

Edited December 1, 20187 yr by Rockliffe

I have tried these tweaks and the textures are sharper and go more into the distance. However, P3D loading is much slower now. I am going to try and isolate what is slowing this down so much.

45 minutes ago, Rockliffe said:

Hey Gerard, I run a 1080ti and have set TEXTURE_SIZE_EXP=10. So far, apart from longer loading times of scenarios, I have not seen any detrimental affect. I can see a noticeable difference in textures at distance and things look overall sharper. I am about to do a longer flight today, down to LOWI in the NGX so I will wait to see the outcome 😊

Perhaps you could try a short flight with 1024 textures and then 512 textures and check GPU and CPU load.. 

Or Anyone else.

At this moment I am replacing my monitors and have no running Fs..

Thanks in advance..🤗

Hey Rob, thanks for all the enlightening things I read in this thread. :)

Just want to confirm for myself (as a single GPU user):

"MaintainSystemCopyOfDeviceTextures=0" and "ENABLE_MEMORY_OPTIMIZATION=0" are only relevant for multiple GPU usage?

Thanks in advance!

Rob, please advise how shall I avoid those unrealistic missing autogen renderings black Airports and textures pop up late. because it still exist in p3d4.4 for me.

i7 6700k 4.2 ghz 1080ti 32 gb ram. Now I’m at 37000 ft in bad weather flying from Macedonia to Pula Airport  and have in VC 45-47 FPS.

external view goes to 55-60 FPS.

Vsync of tb off unlimited. No tweaks in p3d cfg file.

thank you George

Sorry for my English, hope you understand my issue

Edited December 1, 20187 yr by georgiosgiannoukos

58 minutes ago, GSalden said:

Perhaps you could try a short flight with 1024 textures and then 512 textures and check GPU and CPU load.. 

Or Anyone else.

At this moment I am replacing my monitors and have no running Fs..

Thanks in advance..🤗

While I have not yet tested between the two resolutions, I did check GPU and CPU load after installing TEXTURE_SIZE_EXP=10 and although it was only a short test, I tested for about 5 minutes in heavy load scenario, ie, 8/8 cloud with thunderstorm and neither the GPU or CPU load went above 50%. As I say, I really did not see any issues whatsoever, apart from it took about 4 minutes for the scenario to load. I may well report different finding after a longer flight in the NGX. Later today will tell.

Edited December 1, 20187 yr by Rockliffe

1 hour ago, Rockliffe said:

While I have not yet tested between the two resolutions, I did check GPU and CPU load after installing TEXTURE_SIZE_EXP=10 and although it was only a short test, I tested for about 5 minutes in heavy load scenario, ie, 8/8 cloud with thunderstorm and neither the GPU or CPU load went above 50%. As I say, I really did not see any issues whatsoever, apart from it took about 4 minutes for the scenario to load. I may well report different finding after a longer flight in the NGX. Later today will tell.

How was the load before ?

My cpu load on core 0 is always 90-99% ( 3 screens ) with V4.3..

54 minutes ago, GSalden said:

How was the load before ?

My cpu load on core 0 is always 90-99% ( 3 screens ) with V4.3..

Just this minute come in from my sim. Flying A2A out of KSFF in a thunderstorm, with no TEXTURE_SIZE_EXP=10 but with HI res textures on in control panel, both GPU and CPU load showing round about 45% with TEXTURE_SIZE_EXP=10 load on both seemed to be around 50% 😊 Seems to be very little difference. But as I say, loading up the flight is a bit of a yawn, but worth it I think.

2 hours ago, Rockliffe said:

Just this minute come in from my sim. Flying A2A out of KSFF in a thunderstorm, with no TEXTURE_SIZE_EXP=10 but with HI res textures on in control panel, both GPU and CPU load showing round about 45% with TEXTURE_SIZE_EXP=10 load on both seemed to be around 50% 😊 Seems to be very little difference. But as I say, loading up the flight is a bit of a yawn, but worth it I think.

Thanks for the testing ....