6 minutes ago, mpo910 said:

try turn off "HD ground airport (clutter) objects" (this has huge impact) within the scenery cfg app.

Marcus

Thanks Marcus will give it a try

 

14 hours ago, rdyer said:

LVFR blames LM on all VRAM issues, they are not interested in optimizing the scenery.

Yet one can fly into Flightbeams KSFO with high settings, everything on in the scenery cfg and hover around 5GB. LatinVFR is either to lazy or incompetent to have their scenery optimized. They've left P3D in the rearview mirror anyways so it no longer matters. 

14 hours ago, rdyer said:

LVFR blames LM on all VRAM issues, they are not interested in optimizing the scenery.

Yet one can fly into Flightbeams KSFO with high settings, everything on in the scenery cfg and hover around 5GB. LatinVFR is either too lazy or incompetent to have their scenery optimized. They've left P3D in the rearview mirror anyways so it no longer matters. 

No, they have simply completet everything with pbr and that is really heavy on vram. If other major hubs where done completely with pbr than it would be almost equal. Especially all the clutter. 

good point @mpo910  Maybe not as high as some of the ones listed above.  But I find KORD FSDT can be somewhat high on vram.  not a complaint though

8 hours ago, mpo910 said:

No, they have simply completet everything with pbr and that is really heavy on vram. If other major hubs where done completely with pbr than it would be almost equal. Especially all the clutter. 

That is indeed precisely the point. You'll see that any scenery that uses all PBR textures will have high VRAM consumption. OrbX KBUR and, as was mentioned, FSDT KORD can also be high on VRAM because of the use of PBR textures. That said, LatinVFR is still higher than some of those other airports, and it's regardless of size. KMIA and LEMD are bad, but so is KFLL, and SCEL is also quite high on VRAM - higher than FSDT KORD, in my experience. So I definitely think that one element comes down to effective optimization, but it's not the entire story.

Since KSFO was mentioned though, I do think FB is the absolute king of optimization. Their KSFO behaves incredibly well even with OrbX TE Northern California!

LEMD is the only place I ever got the dreaded OOM. (At least I had landed.) But I just flew into the non-PBR version with some pretty challenging settings with no problem (see my sig for specs). That’s without traffic, BTW. It is some nice scenery.

Just did a test in LEMD (non-PBR version) which is the worst in regards to VRAM usage with sliders mostly to the right with EA on, 2xSSAA, 2048 textures - 

Did this test to understand the constraints and when I'll have to give up on eye candy 

Out of 9.9 avail VRAM for a 1080Ti - 

PMDG 737 NGXu - ~7.7 VRAM usage

FSLabs Airbus/ Feelthere E-jets/Aerosoft CRJ - ~8.4 VRAM usage

TFDI 717 - ~8.9 VRAM usage

KMIA & SCEL were significantly better - ~1 GB less in VRAM usage

Reducing textures to 1024 reduced VRAM usage significantly by ~2GB!!

Shadows and traffic had negligible impact on VRAM

 

Bottom line - reduce textures to 1024 when flying into these airports until (hopefully) they are optimized otherwise any spike caused by bad weather or GSX services will in a good scenario downgrade the sim to non-EA mode and worst case scenario bring you to a CTD/DXGI error.