What are the biggest VRAM killers?

[avi8tir 25]

I run a 2080ti, but am encountering VRAM issues. 

What settings or add ons kill VRAM the most? 

[snapshot21 254]

Start with Texture Resolution 🙂

[DaveCT2003 1,820]

24 minutes ago, avi8tir said:

I run a 2080ti, but am encountering VRAM issues. 

What settings or add ons kill VRAM the most? 

I'm guessing your using P3Dv5?  If so, then:

1. Not having the Windows 10 2004 update.

2. Aircraft with older versions of TrueLight and RealGlass (there is a Beta update for this, get more info from the aircraft developer).

3. Using scenery that was not created specifically for the P3Dv4 and/or v5.

4. Using Photoreal scenery textures (as they are loaded regardless of how far away your aircraft is away from the scenery.

 

 

[chapstick 2,757]

The biggest VRAM killer is Prepar3d V5

[JoeFackel 760]

1 hour ago, avi8tir said:

I run a 2080ti, but am encountering VRAM issues. 

What settings or add ons kill VRAM the most? 

Settings: Shadow quality, high AA settings on 4K, Cloud resolution.

[Chock 17,769]

1 hour ago, Chapstick said:

The biggest VRAM killer is Prepar3d V5

If you really think that is true, wait while you try putting the sliders up in MS2020. 🤣

[avi8tir 25]

Just for reference, here is my system - running V5:

• I9-9900k
• 2080ti
• 32GB DDR4 3200
• 2 GB m.2
• 49" CRG9

I use all ORBX products, PMDG, Captain Sim, QW 787. Most add on airports from the big creators, FlyTampa, FSDT, ORBX, etc. ENVSHADE, ENVTEX, ASP3D. No live traffic. I tend to fly with most settings at high or ultra. CPU usually runs below 60 degrees max. 

[chapstick 2,757]

29 minutes ago, Chock said:

If you really think that is true, wait while you try putting the sliders up in MS2020. 🤣

I guess that's a fair comparison since both MSFS and V5 are in Alpha states, basically...

17 minutes ago, avi8tir said:

Just for reference, here is my system - running V5:

• I9-9900k
• 2080ti
• 32GB DDR4 3200
• 2 GB m.2
• 49" CRG9

I use all ORBX products, PMDG, Captain Sim, QW 787. Most add on airports from the big creators, FlyTampa, FSDT, ORBX, etc. ENVSHADE, ENVTEX, ASP3D. No live traffic. I tend to fly with most settings at high or ultra. CPU usually runs below 60 degrees max. 

With a 2080ti you should be fine at most airports at 2048 textures. The biggest VRAM issues arise when you are using 2048+ textures at full PBR airports (LFVR MIA/FLL/MAD or FSDT ORD for example). 

[Bert Pieke 7,585]

10 minutes ago, Chapstick said:

I guess that's a fair comparison since both MSFS and V5 are in Alpha states, basically...

 

Pardon me, but that is just nonsense.. 😉

[chapstick 2,757]

20 minutes ago, Bert Pieke said:

Pardon me, but that is just nonsense.. 😉

Oh my bad, I thought we were entering the nonsensical phase of the discussion since he compared a product in an alpha state to a product that's been released.

[cyyzrwy24 127]

3 hours ago, DaveCT2003 said:

1. Not having the Windows 10 2004 update.

I gained vRam with that....and it widely reported that works better.....I don't have 2080Ti but that's my case at least....

[cyyzrwy24 127]

4 minutes ago, Rob_Ainscough said:

In a default P3D V5 HF2

Is that "around" the corner or strill few months aaway...? Nobody is mentioning this anymore and all major updates are waiting for this. Asking because while I have no issue with V5 I can't even use it since all fleet is grounded and nothing to fly......

[cyyzrwy24 127]

Just now, Rob_Ainscough said:

Around the corner.

Cheers, Rob.

Thanks Rob....everyone went dark suddenly...and I got tired refreshing pages and waiting to take a one normal flight.....

[DaveCT2003 1,820]

9 minutes ago, Rob_Ainscough said:

Around the corner.

Cheers, Rob.

More like "down on the corner".

 

Edited June 6, 2020 by DaveCT2003

[Michael Moe 495]

Hi, a couple of Q for the VRAM gurus. 

Why is it that with 5,4gb VRAM/9.2GB used i get the CTD and mostly a G2D.DLL error switching to outside view .Mostly with Maddog X at EHAM FT and ORBX TE.

2. Does the terrainview =false make any differens switching this to True like we did it before v5?

Its like the limit is way lower than 9,2 GB in my case

Thanks Michael Moe