It seems to provision a large percentage for a cache, without actually needing it I've found. I normally fly on my 1440p monitor, where it hovers around 6GB Vram. Tried slapping it on my 4K monitor and under the same settings otherwise, same area etc. it stayed at around 6GB. 

5 hours ago, Sesquashtoo said:

I'm running with a GTX1070 8GB and only ***12*** GB's of System Ram.  That is all my M.B. will allow.  That being said, I have no problems running either P3D v4.5 (pretty well maxed out at 28-33 FPS and XP11.50b3 pretty well maxed out at 28-30 FPS. 

What aircraft are you flying in P3D 4.5? What scenery addons, and what weather engine if I may ask?  Would like a better understand to use as a base.  I have a GTX970 and 4GB Vram.  Held off upgrading my vidcard originally due to prices >$1,000, then later as I draw nearer and nearer to a new build.

Dear All,

I have been in contact with LM devs, here you have an official statement from Rob McCarthy:

Quote

Hi Raul,

This is at the top of our priorities on things we're currently working to improve and fix. We are planning to release a hotfix as soon as we can to fix the highest priority issues addressed by users. We currently cannot provide a firm date for this but we are hoping to have this out in the next couple weeks. 

Also one thing we've noticed in several cases is some add-ons tend to use 4k textures when it is not always necessary. Having users set their texture resolution to 2k instead and comparing memory usages around these add-ons is a good step to potentially reduce vram usage.

Regards,
Rob McCarthy
Prepar3D® Core Lead

Hope this helps, in the meantime if you follow my previous advise to tweak your settings and also Rob M. advise you should be able to avoid any CTD until the HF is available.

Regards,
Raul 

I kept getting CTD. This seemed to happen when I used more complex aircraft (e.g. F-35). My VRAM was nowhere near full (only about 4Gb used, my specs are in my signature below) and my CPU cores weren't unduly stressed either. I was getting >125 when it wasn't CTDing. I discovered the issue was unlimited FPS. When I limited to 30 FPS all by CTD went away. There seems to be something which allows the GPU to run away with itself without an FPS limit. Just my 2p/2c.

Andy

18 hours ago, Chapstick said:

I think something else is going on -- you shouldn't be crashing at 5.4GB on a 11GB card.

I'm getting crashes at 3.7GB on an 8GB card, and I don't get it either. The Alt+Z onscreen says 3.7 / 6.7 (usable) for VRAM and it freezes. And this is at 70 FPS running buttery smooth. So what gives? Can I be OOM when I am not OOM?

2 minutes ago, mtr75 said:

I'm getting crashes at 3.7GB on an 8GB card, and I don't get it either. The Alt+Z onscreen says 3.7 / 6.7 (usable) for VRAM and it freezes. And this is at 70 FPS running buttery smooth. So what gives? Can I be OOM when I am not OOM?

70 FPS limited, or ~70 FPS unlimited? For me this was the key (without a limit the GPU seemed to trip somehow).

Edited April 16, 20206 yr by Airtrooper

2 minutes ago, mtr75 said:

I'm getting crashes at 3.7GB on an 8GB card, and I don't get it either. The Alt+Z onscreen says 3.7 / 6.7 (usable) for VRAM and it freezes. And this is at 70 FPS running buttery smooth. So what gives? Can I be OOM when I am not OOM?

That is a different problem. look at the event viewer and report to LM what you were doing at that time.. this is not related to VRAM CTD.

S.

On 4/15/2020 at 12:06 PM, G-RFRY said:

Did you notice the settle test for MSFS was using 2080Ti in the PC`s, so if you want to wait for that OK.

One of the developers said his testing PC was running a 1060 and it ran fine at 1080p.

Also it's still in Alpha, it hasn't gone through optimization yet.

3 hours ago, Chapstick said:

Is that scenario with TruSky on or off?

Off

6 minutes ago, simbol said:

That is a different problem. look at the event viewer and report to LM what you were doing at that time.. this is not related to VRAM CTD.

S.

Will do. And mind you, this was with A 1080 and 8700k non-OC'd, literallY every slider to the right, and getting 70+ FPS unlimited. It was showing 3.7/6.7, and running like absolute butter. People are having issues but I'm loving the sim. To me the potential is just massive once we get it tweaked right.

And thanks Simbol. Appreciate the knowledge my friend. 

TrueSky seems to eat 1GB of VRAM, turning that off should help with some people, or at least lowering the cloud resolution.

Edited April 16, 20206 yr by Tuskin38

2 hours ago, simbol said:

Dear All,

I have been in contact with LM devs, here you have an official statement from Rob McCarthy:

Hope this helps, in the meantime if you follow my previous advise to tweak your settings and also Rob M. advise you should be able to avoid any CTD until the HF is available.

Regards,
Raul 

Raul, I think I speak for many when I say thank you for your continued efforts here to help us address issues with both past versions of P3D and v5! 👍

I appreciate you sharing the update from Rob @ LM. As I mentioned in a previous exchange with you, I've started a couple of threads over on the Prepar3d forum related to issues I was seeing.  One was the CTD on VRAM OOM (which we are discussing here) and the other is the incompatibility of P3Dv5 with the newest AMD GPUs, specifically the 5600 and 5700 series cards.  There are now a couple pages of people all with the same GPUs and all having the same problem - namely, changing the view in P3Dv5 causes a CTD.  This is the more severe problem as those of us with the latest AMD GPUs really can't run v5 at all.  It would be really great if we could get a response or update from LM on that issue; they've been silent on it since Tuesday when Beau made a few settings suggestions.  To be clear, this issue is not resolved by changing any of the suggested settings; even when I set all graphics/world/lighting settings to the lowest possible value and turn off everything that can be turned off (atmospherics, shadows, reflections, dynamic lighting, anti-aliasing, HDR, high resolution terrain, speedtrees), the issue persists - changing the view to any cockpit view causes a CTD. Part of the reason for the concern is that many of us with incompatible (and brand new) AMD GPUs will likely want to request a refund before the window closes if there's no definitive response and timeline for a resolution. I know they're slammed with work right now, so I haven't made a 'stink' because I know from experience that doesn't help - and clearly AMD GPUs are in the minority in the P3D world. That said, if you happen to have an opportunity to inquire with Rob/LM/on the beta forums about this open issue (https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=136854) I'm sure those of us with these GPUs would be greatly appreciative. Beau mentioned that there were 'AMD users' among the beta testers; it would also be super helpful if one of those testers could possibly comment or shed some light on what GPU they were using, what driver version and what windows version worked for them, so those of us with the cards might try to match that setup.  Per your previous suggestion, I have offered to Beau, both in the forum and via PM, to assist with any testing they need as I built a totally new and clean environment with just Win10+P3Dv5 to test out various configuration changes.

Again, thanks so much for your contributions, they are appreciated!

Edited April 16, 20206 yr by cwburnett

Simbol is a national treasure 🙂

23 minutes ago, cwburnett said:

Again, thanks so much for your contributions, they are appreciated!

You are welcome. The steps I posted here is for people with VRAM problems.

I am aware of the issue with AMD but I don't want to mix issues of that here.

I saw Beau responded to you and others and I am sure he is on the case.

As Rob McCarthy said they are working on a HF. What they need is as much reporting as possible as this will help them to narrow down the issues.

Regards,

Simbol 

3 hours ago, kurtb said:

ctd is comming from cards that are not dx12 capable

No. If a given card is not DX12 capable, the sim would not load at all. The problem is that DX12 will crash if VRAM required in a particular scenario exceeds the installed amount of VRAM on the GPU. That is the nature of DX12, no matter what game is being used.