I forgot to mention that I also had Orbx Trees HD & Orbx Buildings - I never had any issues with those in the past - infact those were always better fps for me.  

59 minutes ago, captain420 said:

As long as I can get at least 30fps with heavy add-ons running at 4k then I'm happy. We're almost there. By heavy add-ons I mean the essentials and more:

1. OrbX Global Base
2. OrbX Buildings HD
3. OrbX Trees HD
4. OrbX TerraFlora v2
5. OrbX OpenLC
6. OrbX Full Regions
7. OrbX True Earth
8. OrbX CityScapes
9. Drzewiecki Design City X
10. Global Ship Traffic v2
11. FSReborn AI Lights Pro
12. AIG-OCI
13. Fs2Crew RAAS Pro
14. Fs2Crew PMDG/FSLabs Voice/Button Control
15. GSX Level 2
16. 3rd Party Airport Scenery
17. Pro-ATC
18. Aivlasoft EFB
19. PMDG/FSLabs Planes
20. Active Sky P3D
21. FSUIPC

Now if anyone here can run with all of the above in 4K with everything enabled, and sliders all the way to the right consistently at 30fps and up. Then we're talking.

I'm sure Rob can. 

16 minutes ago, Rob_Ainscough said:

RE: MAX_TEXTURE_REQUEST_DISTANCE

Yeah, there is some confusion on this value as it seems to indicate "distance", but my understanding from Beau at LM is that it represents memory allocation limits.  So I did experiment with several values (default is 1000) and my best results happened at 320000 (three hundred and twenty thousand) not 32000 (thirty two thousand).  Your mileage may vary, but that's what I use.

Here is the exact information from Beau Hollis (LM) regarding this value:

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)

I would link you to the thread but it's in a protected forum.  As you can see, Beau referenced a value as high as 1 Million (1000000).  But pay attention to item 1) above, very important to make this value "effective".

Cheers, Rob.

Hey Rob - this time even with value of 1000 which is default - I did not see black textures with autogen away from the airport.  Only thing is with PMDG 747 - going from external view to VC - the VC is black and textures have to load.  Before it was the things far away in p3dv4.5 and now in v5 it is external view to internal view or sometimes when you jump from VC to external the plane is black and all other scenery around the plane is fine.  Are you having any issues like that?

Edited May 11, 20206 yr by Skywolf

I'm having similiar issues, but it varies, sometimes when I jump from ext to VC and VC to ext, it doesn't have to reload and is instant, but other times it does reload. I guess it depends on the amount of add-ons you're using. FOr example at Flightbeam KSFO, with AI and all, I will get the texture reloading occasionally when switching between ext to VC and vice versa, but once I take off and am at a far distance away from the airport, then the issue goes away. But as soon as my destination airport is in sight, the problem with reloading happens again. It's very annoying and takes the immersion away. I wish there was a fix for this so that this doesn't happen.

Be aware that Win 10 v2004 currently breaks the Garmin Trainer required by Flight1 and RXP

11 hours ago, suchw said:

Hey

 

Im getting that in 4K almost fully loaded with all addons only difference I fly in Australia and im sure its not as taxing as some of those big world airports

Yeah. I fly mostly around the Caribbean. 

10 hours ago, Rob_Ainscough said:

But pay attention to item 1) above, very important to make this value "effective".

Cheers, Rob.

Thanks Rob,

Do you set a value for the “FarClipOverride” in meters to assure it becomes effective and therefore the Max Texture Distance is used? Also what about the 2) item? 
 

Sorry to trouble you with these detailed questions but I’m wired to understand the tweaks I make.

Thanks in advance, stay well!

Joe

Edited May 11, 20206 yr by joepoway

Quote

TextureMaxLoad=9 

Using this made all of my buildings go blurry. Back to 1024

Quote

Hey Rob - this time even with value of 1000 which is default - I did not see black textures with autogen away from the airport.  Only thing is with PMDG 747 - going from external view to VC - the VC is black and textures have to load.  Before it was the things far away in p3dv4.5 and now in v5 it is external view to internal view or sometimes when you jump from VC to external the plane is black and all other scenery around the plane is fine.  Are you having any issues like that?

I wonder if this is one of the factor that has been causing the CTD with Radeon 57xx, VII and Vega cards?

Edited May 11, 20206 yr by Snowfalcon
spelling

13 hours ago, Rob_Ainscough said:

RE: MAX_TEXTURE_REQUEST_DISTANCE

Yeah, there is some confusion on this value as it seems to indicate "distance", but my understanding from Beau at LM is that it represents memory allocation limits.  So I did experiment with several values (default is 1000) and my best results happened at 320000 (three hundred and twenty thousand) not 32000 (thirty two thousand).  Your mileage may vary, but that's what I use.

Here is the exact information from Beau Hollis (LM) regarding this value:

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)

I would link you to the thread but it's in a protected forum.  As you can see, Beau referenced a value as high as 1 Million (1000000).  But pay attention to item 1) above, very important to make this value "effective".

Cheers, Rob.

Hey Rob - 

I actually did just play with this value only - it technically solved my black texture swap that I was seeing when panning external fast and hard - followed by going in to the VC.  

I just went from 1000 to 10000

Now here is the interesting part - it seems like it is temporary allocating that much VRAM to contain some textures

For Example: 100,000 = 100MB as I did see almost the exact jump in VRAM in P3Dv5 for a bit when panning external/jumping into vc/slewing the aircraft (Other readers - For illsutration purposes the comma is used in this post to explain - do not this in your P3Dv5 Prepar3d.cfg)

But then I decided to do 500,000 as the value and guess what the VRAM jumped to additional 500Mb from the last setting of 100,000 which was 100MB.  In Total 400MB more, I used the same location, same plane, same everything.  But after that spike. VRAM came down - gpu/windows are doing their thing.  It jumps up that much and then it comes down.  I am just going to do 10000 or 50000 as all my textures from VC show up and there is no lag.

Now from my original post - I have only manual 2 tweaks for my Prepar3d.

 

My P3Dv5 Manual 2-3 Configs 

1) RS_MIN_OBJECT_PIXEL_RADIUS=1.000000 (Default is 2)  - Update 6:54pm - see Rob's Answer below - this is better left alone to default

2) TextureMaxLoad=9   - can you help on this - I went to 9 as I was getting black textures when I went panning outside the VC and then back to VC in PMDG 747.  Weird I never had to do anything like this before.  This setting helped on the black VC textures reload etc I dunno what the frak is going on.  This setting has to be in on [DISPLAY] section.  See P3Dv5 Documentation it is listed in Advanced Config Section. 

Update: You DO NOT need TextureMaxLoad=9 (Remove the entire line) - the slight increase on MAX_TEXTURE_REQUEST_DISTANCE solved all my problems so far

 

3) UseGlobalTerrainView=True - Default is False.  YMMV.  True does take some VRAM but I have always enabled it (from p3dv4).  Again Rob can chime in on this one.

 

4) Affinity Mask is set to 4092 for my cpu

  

TL/DR

1) Change value of MAX_TEXTURE_REQUEST_DISTANCE in [GRAPHICS] to higher amount than the default.  The default value is 1000.  Increase this

2) UseGlobalTerrainView=True - Default is False.  YMMV.  True, it does take some VRAM but I have always enabled it (from p3dv4).  

3) Affinity Mask - Only if you want.  I have mine set to 4092 (6 Core CPU with HT - all Cores are running Except Core 0 and its logical core)

 

Time to go fly....yay

 

 

Edited May 11, 20206 yr by Skywolf

12 hours ago, TonyD said:

Be aware that Win 10 v2004 currently breaks the Garmin Trainer required by Flight1 and RXP

I hope that will be fixed soon by Garmin. I had Win2004 already running on my system but rolled back just because of this incompatibility. F1 GTN 750 for A2A C172 was not usable.

UseGlobalTerrainView=True

The default falue is False.

Performance Tuning Tip:

By default, every camera has its own terrain view which requests texture and dem tiles near the camera to ensure that all cameras get a quality view of terrain. When tessellation is enabled, it is possible for cameras to share data and avoid the extra work required to manage multiple terrain views. For multi-view scenarios in which all views are near each other, it may be desirable to have views simply render the terrain tiles loaded by the default view. Setting this option to True will prevent all camera from creating a terrain view except for the default 3d view. This can help avoid texture flashing and terrain spikes that occur on some systems with multiple views and/or multiple video cards. This value can be overridden by the UseGlobalTerrainView entry in a given CameraDefinition allowing each camera to determine whether or not to create a terrain view. This setting will be engorged if Tessellation is not enabled.

Edited May 11, 20206 yr by captain420

4 hours ago, Nemo said:

I hope that will be fixed soon by Garmin. I had Win2004 already running on my system but rolled back just because of this incompatibility. F1 GTN 750 for A2A C172 was not usable.

You can still use the F1 GTNs with an older version of the trainer, version 2.3.1.0. That one works fine on Win 10 - 2004. Just info in case you will update later again and the Garmin Trainer has not been updated yet.

Does anyone know when is the new Windows update supposed to be released? (I am not a Windows insider)

may 28th is last estimate.