Keith Whitwell pisze: > On Fri, 2009-10-09 at 06:19 -0700, michal wrote: > >> Keith Whitwell pisze: >> >>> Michal, >>> >>> Sorry, this isn't a great way to do this. This can usually be caught >>> much earlier in the pipeline and with much less overhead by validating >>> the incoming index list. >>> >>> >>> >> OK, so we scan the whole element array beforehand, and if any element is >> out of range, we kill the while primitive, right? >> >> >>> We normally do that in Mesa or the state tracker, if that helps. >>> >>> >>> >> Does this mean we actually don't want to check that in the draw module >> and we should deal with it on the state tracker level? >> > > The argument *against* doing it at the state-tracker level is that if > the vertices are in VBOs, then a lot of hardware doesn't need any > assistance from the CPU to cope with out-of-bounds indices. > > So maybe what that means is that the draw module should do the scan, or > perhaps that the code-generated vertex shader within the draw module > should validate each index as it's being processed. > > I am having problems trying to imagine that, unless we do clipping inside vertex shaders. I would think once the vertex shader is hit, the vertex data has already been fetched, and if the element had been out of range, we are dead.
------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
