DX11 is forgiving if an application uses more VRAM as there is available on the GPU. It simpli swaps out to conventional RAM. Same for OPEN GL.DX12 gives an OOM error in the same situation.P3D V5 is on DX12. That's why it is important to have an eye on your VRAM occupation in V5. And that's why V5 shows that measure as an info for Shift-Z.Karl
Quote from: kaha on April 28, 2020, 08:58:22 AMDX11 is forgiving if an application uses more VRAM as there is available on the GPU. It simpli swaps out to conventional RAM. Same for OPEN GL.DX12 gives an OOM error in the same situation.P3D V5 is on DX12. That's why it is important to have an eye on your VRAM occupation in V5. And that's why V5 shows that measure as an info for Shift-Z.KarlLockheed is working on a very quick fix for the P3Dv5 VRAM OOM problem. This is, quite possibly, a do or die fix. The vast majority of P3Dv4 users have graphic boards with 8 GB VRAM or less. And, since you can't add VRAM to a graphics board, right now the only option is to buy a new board if you want more VRAM. One of the biggest draws of P3Dv5 is its much better frame rate which becomes very helpful in densely populated areas (e.g. London, Seattle) right up until you run out of VRAM and the sim crashes. Some customers are already asking for refunds while most are deciding to stay with V4 until Lockheed fixes the issue. I can't believe Lockheed released V5 with this glaring glitch. Rod