4K and framebuffers

[Arphenyte]

So I know true 4K is (4096 x 2160) meaning 8847360 pixels. What I would like to know is, how large should a framebuffer be to support true 4K at 60 FPS. I know the Titan X (with a 12GB framebuffer) does it, but how much of it does it consume?

[Lolzious]

I'm going to guess, varying by game, 4-8gb of VRAM.

[Prastupok]

Other than Shadow of Mordor, most games are still just at the 4GB. That depends on AA and texture quality.

[Glenwing]

Frame buffering is only one of the things the VRAM is used for, and it doesn't take a particularly large capacity, it's the bandwidth that matters for that, for continual exchange of large amounts of information to and from the buffer. You need to take into account things like textures and other game information stored in the VRAM, that will fill up a lot of VRAM depending on the game (and mods, if applicable).

[Arphenyte]

There has to be a correlation between the number of pixels, and the size of the framebuffer right? Like how many pixels is 1MB, or how many pixels make 1GB. Does anyone know?

[MegaDave91]

Shadow of Mordor utilizes ~6GB w/ ultra texture pack

Evolve utilizes 6+GB w/ 'very high' settings

BF4 utilizes ~4GB (ultra w/ 4XMSAA...redundant amount at 4K)

[m_tieu]

Most games I play use 2gb or less on 4k with very high or ultra settings. I always turn AA off or 2x at very most to reduce the performance hit.

[sgloux3470]

I haven't updated this in awhile, but it has a fair amount of data in it that should help answer your question.

 

Download it for the best viewing experience

https://drive.google.com/file/d/0B4HpnFBkAjlIUGdpNEpBcm9MOFE/view?usp=sharing

 

It's worth noting that most engines will use significantly more VRAM than they actually need if it's available.  The only real way to properly test this would be to slap a card that doesn't have enough VRAM in it and then see how much it uses.

 

Anti-aliasing will add about 500-800 MB with 4x.

[Texhnlyze]

Shadow of Modor consumed 6-6.5GB of VRAM using Titan X and that game is VRAM hungry.