Bytes a render target of this size occupies, for the two attachments the
renderer always allocates together: a depth24plus depth buffer and an
rgba8uint object-id buffer, both one sample and one mip.
depth24plus is implementation-defined -- a driver may store 24 or 32 bits
-- so the wider layout is charged. The result is therefore an upper bound on
the attachment pair, not a driver-exact figure, and any record that reports
it has to say so.
Bytes a render target of this size occupies, for the two attachments the renderer always allocates together: a
depth24plusdepth buffer and anrgba8uintobject-id buffer, both one sample and one mip.depth24plusis implementation-defined -- a driver may store 24 or 32 bits -- so the wider layout is charged. The result is therefore an upper bound on the attachment pair, not a driver-exact figure, and any record that reports it has to say so.