-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric Anholt wrote:
| We haven't touched the texsubimage path, having not found it in a | profile yet. It'll probably be doing map/write/unmap, which (as noted | elsewhere in the thread) is pretty much the worst thing you can do. If | you have a relevant application where texsubimage is showing up in the | profile, I'd enjoy playing with it. Anything that uses shadow maps (or any other render-to-texture type effect) without framebuffer objects will hit this path. Since iD only uses stencil volume shadows, it's not surprising that you haven't hit it yet. And I don't think glTexSubImage is the problem, I think glCopyTexSubImage is the problem. There are also some Nvidia demos that use pixel buffer objects to do async. glReadPixels. I suspect that path will have the same potential problems. Unless I've completely missed the point... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFINGt/X1gOwKyEAw8RAg+dAJ9tmaxx2hV+J3JQXgiMVRiO3fqsIwCfYvdY ZMxDXteA/mj67W08cjgCgHc= =SH10 -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
