I switched from a 1920x1080 old lcd to a 4k hdr gaming monitor at 3840x2160
Now my ATR loads with all the displays dead and the throttle unresponsive.
The other aircraft are fine… at least the 4 or 5 i have tried so far
Very weird.
Any ideas?
I’d you downshift your resolution in the sim back to 1080 (sure, it’s non-native, but as a test), do the displays work again?
i just tried it, yeah… they work again
but what does this mean?
the atr doesnt work in 4k?
I use it in 4K.
What’s your RAM & VRAM?
1 Like
32 and 8 respectively
I think that’s your answer, i.e. 4K VRAM usage.
What does the in-game usage show when running in 4K?
i see
oh this is a bummer…
one of the main reasons for changing monitors was the ATR… i can’t read the displays because the text is so small… and it is one of my main go-to a/c…
im at worl now but i will report back with that number
1 Like
I should endeavor to ask about that when I recommend 4K to anyone.
I’m so used to having 24GB VRAM that I don’t even consider it. 
Yes, with the VRAM you have, it would seem you’re running into issues similar to what the Xbox experiences when it runs low on memory and the screens go black.
Are there some graphic options that you could turn down to try and reduce the load? I think some of the texture options may influence VRAM usage. I can’t remember which ones are the most influential.
Like @BegottenPoet228 I have 24GB of VRAM, as well. I specifically picked the video card I have due to what I’d learned about the sim’s voracious appetite for VRAM.
Different experiences for different people. I run the sim at 4K, almost all ultra settings, TLOD 300, OLOD 200, with a 10GB RTX 3080, Ryzen 7 3700X, 32GB RAM. For high VRAM usage I typically see 8 - 9 GB. I certainly have no issues flying the Inibuilds A320 V2 for instance: framerates typically around 30FPS-ish. Obviously drops in very intensive scenes but certainly not something that prevents the aircraft displaying.
As example: a five minute CapFrameX plot for approach and landing at Rotterdam:
While it sounds reasonable that lower VRAM is at least a contributory factor, I think one has to be careful to assume lower VRAM is the sole culprit. Given my experience, not having the aircraft display instruments seems like something more/different than just low VRAM. To the OP: could you perhaps provide a screenshot of your display settings as I suspect this MAY be part of the problem?
1 Like
Crazy as it may be, that 2GB difference between you and the OP could be making a difference.
Also, I’m definitely not arguing against your point that there may be other factors at play here.
Are you using DX11 or 12?
Using DX11: have not tried DX12 yet
1 Like
DX12 definitely uses more VRAM.
@TOLOWTERRAIN723 are you using DX11 or 12?
Never having had this issue I don’t know what is supposed to happen when you run out of VRAM. Isn’t it supposed to use “Shared GPU memory”? In my ignorance I assumed this would impact performance but would it cause display disruption like the OP is experiencing? If so: would avoiding things like live traffic etc help?
thanks all for the help, i believe in the attached captures is all the info requested. this is spawned at the runway at jfk with the a/c dead and the unresposive throttle (what’s up with that?)
the a320v2 works ok, although i haven’t done a long flight yet
You may be surprised at how little visible difference there is in setting these options lower.
Buildings
Trees
Grass
But it does seem weird that only the ATR is affected.
For sure. Although there are some pretty odd reports of ATR-specific issues (eg. frozen screens and controls) since its latest update.
I cannot help but think there is something with that aircraft that is partially responsible here.
what if i remove and reinstall the a/c? would that do something?
Not just the ATR anymore. I just had the Inibuilds A320 screens freeze just like the ATR does. I was doing KICT to KDEN and when I went into the MCDU to add the KIPPR IAF for the 17R approach, the whole plane froze up.
Maybe something is broken in the backend. some unhandled exception with the way the MCDUs are interacting with the base game. This is now 2 “default” planes suffering this bug.