search for: rgba16f

Hello, I attempted doing this a while back, before I really understood what was going on. I got some advice that went totally over my head, and I dropped the issue. I think I'm much better-prepared to tackle the issue this time around. To recap, nv30 (and nv40) hw can't handle certain color/depth format combinations. Specifically, a 16-bit color format must be paired with a 16-bit depth

...raw seems > _really_ wasteful... anything I can do about that? You can do that in set_framebuffer_state. When binding, blit to a depth buffer which matches the colorbuffer format. When unbinding, blit back. You can also drop support for 16-bit formats. What about rendering to R16F, RG16F, and RGBA16F? Does R16F have to be coupled with a 16-bit depth buffer too? Marek

...wihle rendering? > > You can also drop support for 16-bit formats. I assumed that these were required by some GL version... I also presume that it's faster to use these. BTW, when I say 16-bit, I mean like B5G6R5 or B5G5R5X1, not R16*. > > What about rendering to R16F, RG16F, and RGBA16F? Does R16F have to be > coupled with a 16-bit depth buffer too? Gooood question. I assume they want a 32-bit depth buffer. Although I believe those are actually disabled for now (aka forever, unless someone cares enough to turn them on), even though it does look like there's HW support for...