I just noticed that alienarena fails to create an FBO for depth rendering
because on st_validate_framebuffer, the depth attachment contains a pt
in the stObj with format XR8G8B8_UNORM, which nv50 (contrary to sp)
reports as not supported in screen-is_format_supported if usage is ZS.
This happens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Bumiller wrote:
I just noticed that alienarena fails to create an FBO for depth rendering
because on st_validate_framebuffer, the depth attachment contains a pt
in the stObj with format XR8G8B8_UNORM, which nv50 (contrary to sp)
reports
Christoph Bumiller wrote:
I just noticed that alienarena fails to create an FBO for depth rendering
because on st_validate_framebuffer, the depth attachment contains a pt
in the stObj with format XR8G8B8_UNORM, which nv50 (contrary to sp)
reports as not supported in screen-is_format_supported if
On 01.02.2010 21:44, Brian Paul wrote:
Christoph Bumiller wrote:
I just noticed that alienarena fails to create an FBO for depth
rendering
because on st_validate_framebuffer, the depth attachment contains a pt
in the stObj with format XR8G8B8_UNORM, which nv50 (contrary to sp)
reports as not
Christoph Bumiller wrote:
On 01.02.2010 21:44, Brian Paul wrote:
Christoph Bumiller wrote:
I just noticed that alienarena fails to create an FBO for depth
rendering
because on st_validate_framebuffer, the depth attachment contains a pt
in the stObj with format XR8G8B8_UNORM, which nv50