Developer Display FPS does not report GPU VRAM properly

Sim Update 15 Beta User Interface & Activities
1

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

Yes no change made

Brief description of the issue:

RivaTuners GPU VRAM vs MSFS GPU MEM does not match
Provide Screenshot(s)/video(s) of the issue encountered:

VRAM issue fixed
VRAM issue fixed1920×804 97 KB

Detailed steps to reproduce the issue encountered:

PC specs and peripheral set up:

5800X3D/32GB RAM / 3080Ti 12GB VRAM

Are you using DX11 or DX12?

DX11
Are you using DLSS?
TAA

:loudspeaker: For anyone who wants to contribute to this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

I was having major Mainthread limited error until I realized using MSI Afterburner and RivaTuner statistic that I was running out of VRAM.

Are you using DX11 or DX12?

DX11
Are you using DLSS?
No. TAA
If relevant, provide additional screenshots/video:

2

Isn’t this just the difference between total usage and what the game itself is using? Maybe you have something else running that’s also using VMem.

3

it’s possible but how am I supposed to managed my settings in MSFS if it doesn’t report the proper amount of VRAM that is being used right now.

4

Good question.

5

Makes sense like this, because it tells you that something other than MSFS is apparently using over 50% of your VRAM.

That said, it would be more helpful if the dev tool info showed all three values - MSFS use, total use, maximum available.

6

You could use Task Manager’s ‘Processes’ tab to show you that info.

7

it is not. It’s all GPU VRAM besides the OS uses VRAM. The issue is that we have been using this DIsplay FPS for years as a tool to help use change graphics settings nad monitor bottleneck. Turns out that maybe it’s GPU MEM allocated versus reserved that makes the difference here. Either way. I was hitting hard bottleneck and it was bogging down the mainthread until I switch tools and find out why