V5 - Anyone else seeing high VRAM usage?

[chapstick 2,757]

I just got the latest installer for the Lear off Sim Market. I haven't flown it in a long time, but I don't remember VRAM usage being so high. At the default Randolph AFB in V5, it's about 5.7GB and at a heavy add-on airport like LVFR's FLL that has full PBR it's closer to 6.5 and will CTD on my 8GB card. This is without TruSky turned on, which is especially concerning. The Falcon has similarly high VRAM usage. 

[rickjake 243]

1 hour ago, Chapstick said:

I just got the latest installer for the Lear off Sim Market. I haven't flown it in a long time, but I don't remember VRAM usage being so high. At the default Randolph AFB in V5, it's about 5.7GB and at a heavy add-on airport like LVFR's FLL that has full PBR it's closer to 6.5 and will CTD on my 8GB card. This is without TruSky turned on, which is especially concerning. The Falcon has similarly high VRAM usage. 

Its a result of using Direct X 12 that P3Dv5 is now using vers Direct X 11 with the previous version.  I am no expert, on this, but using Direct X12 uses VRAM differently, and takes more advantage of VRAM, making the sim faster. Unfortuntaly, it has no check for when you hit the limit of your VRAM and will OOM. 

I believe LM are looking into this for a solution.  

[chapstick 2,757]

31 minutes ago, rickjake said:

Its a result of using Direct X 12 that P3Dv5 is now using vers Direct X 11 with the previous version.  I am no expert, on this, but using Direct X12 uses VRAM differently, and takes more advantage of VRAM, making the sim faster. Unfortuntaly, it has no check for when you hit the limit of your VRAM and will OOM. 

I believe LM are looking into this for a solution.  

Yeah I'm up to speed on the VRAM situation with V5 but I guess I just didn't realize how VRAM-hungry FSW's add-ons are until I tried them in DX12 which has a hard limit. I don't think LM can do much except put in a warning that gives users a chance to lower their settings. I think third party devs are, unfortunately, going to have to find ways to make their add-ons more efficient. 

[JRBarrett 3,076]

What is your default texture size? (I use 2048). At a default airport (KDTW) in the default Commander 114, with True Sky enabled, VRAM is 3.6. With the FSW Lear it’s 4.0, or 400MB higher. A bit more than default, but not excessively so.

[chapstick 2,757]

22 minutes ago, JRBarrett said:

What is your default texture size? (I use 2048). At a default airport (KDTW) in the default Commander 114, with True Sky enabled, VRAM is 3.6. With the FSW Lear it’s 4.0, or 400MB higher. A bit more than default, but not excessively so.

I use 2048 as well. I just followed your example and I'm getting the same results. I guess scenery is the real culprit. I keep using LVFR's FLL uses 6.0/6.7 VRAM. 

[ark 1,290]

52 minutes ago, JRBarrett said:

What is your default texture size? (I use 2048). At a default airport (KDTW) in the default Commander 114, with True Sky enabled, VRAM is 3.6. With the FSW Lear it’s 4.0, or 400MB higher. A bit more than default, but not excessively so.

Thanks Jim, that is useful information to have especially considering how much more complex the L35A is than the default Commander 114.

Al

[JRBarrett 3,076]

2 hours ago, Chapstick said:

I use 2048 as well. I just followed your example and I'm getting the same results. I guess scenery is the real culprit. I keep using LVFR's FLL uses 6.0/6.7 VRAM. 

I have a GTX1080Ti with 9.2GB available in P3D. I haven’t come close to an OOM yet... not because my system is anything special, but only because I have not yet loaded up an über complex airport like LVFR KMIA. I do have Orbx textures and OpenLC, but I’m going to hold off installing any of my 3rd party airports until after the hotfix is released sometime next week, because I suspect it’s going to require a new client, content and scenery reinstall.

Unfortunately, I just had my very first “invisible wall” crash, on a short flight from KTEB to KTEB. In the Falcon 50. I had set up to do the ILS 6, circle to land on runway 01. (The MetLife Stadium, which is an important landmark used when hand flying this procedure is present in the default scenery, which was nice to see.) Everything was going perfectly - made the initial turn at TORBY, set up a 500 FPM descent, made the turn to final south of the stadium and rolled out on the runway centerline with good speed and descent rate, and then... at 500 feet AGL... BAM! on the ground instantly. Arghh...

Since I had crash detection turned off, I was able to taxi through the buildings of the industrial park where I found myself, through the perimeter fence of the airport, onto a taxiway, and parked at the Jet Aviation FBO 😎

Edited April 23, 2020 by JRBarrett

[chapstick 2,757]

13 minutes ago, JRBarrett said:

Since I had crash detection turned off, I was able to taxi through the buildings of the industrial park where I found myself, through the perimeter fence of the airport, onto a taxiway, and parked at the Jet Aviation FBO 😎

Pretty sure that's in the QRH under Off-Site Landing...

[ark 1,290]

35 minutes ago, JRBarrett said:

Since I had crash detection turned off, I was able to taxi through the buildings of the industrial park where I found myself, through the perimeter fence of the airport, onto a taxiway, and parked at the Jet Aviation FBO 😎

😮😉