BionicBytes
03-10-2009, 06:25 AM
Can any one help - or has anyone seen the same problem?
I have developed a deferred rendering engine with nVidia Geforce 8 hardware which uses a very flexible MRT format - thanks to the support of EXTX_FRAMEBUFFER_MIXED_FORMATS.
When running on the Radeon with Cat 9.2 OpenGL3.0 drivers (still using the 2.1 context), the ARB_FrameBuffer_Objects is detected and used (proved that with a debugger). However, the ARB_FBO does not seem to support mixed formats in the way the spec suggests or in the way that the EXTX_FBO works.
Basically, the ARB_FBO supports mixed dimensions OK, but not mixed formats. By mixed formats I mean RGBA16F and RGBA8 colour attachments in the FBO. I can get ARB_FBO to accept a different number of channels (RGBA8 and RGB8), but not mixing floating point with 8-bit attachments.
Whist this is better than EXT_FBO, it's not as I would expect from the GL3.0 implementation.
Can any one else confirm this with Radeon or nVidia h/w ?
I have developed a deferred rendering engine with nVidia Geforce 8 hardware which uses a very flexible MRT format - thanks to the support of EXTX_FRAMEBUFFER_MIXED_FORMATS.
When running on the Radeon with Cat 9.2 OpenGL3.0 drivers (still using the 2.1 context), the ARB_FrameBuffer_Objects is detected and used (proved that with a debugger). However, the ARB_FBO does not seem to support mixed formats in the way the spec suggests or in the way that the EXTX_FBO works.
Basically, the ARB_FBO supports mixed dimensions OK, but not mixed formats. By mixed formats I mean RGBA16F and RGBA8 colour attachments in the FBO. I can get ARB_FBO to accept a different number of channels (RGBA8 and RGB8), but not mixing floating point with 8-bit attachments.
Whist this is better than EXT_FBO, it's not as I would expect from the GL3.0 implementation.
Can any one else confirm this with Radeon or nVidia h/w ?