On Fri, Jan 10, 2003 at 04:25:47PM +0000, Keith Whitwell wrote: > > > > > Oh, my bad. Too many people to keep track of. :) It seems that Keith has > > already extended the isosurf demo to trigger the failure condition, though, > > so hopefully I can stop pretending to be someone who has any idea what's > > going on with this. :) > > Hmm, actually it was just my screwup in isosurf that I generated. In that app > at least, GL_COMPILE_AND_EXECUTE plus glArrayElement() works just fine.
Huh. Maybe there's something else going on, then... my engine does a lot of things which could be seen as weird. Is there a simple way to dump all of the OpenGL context state? Also, how large were the vertex arrays you were using in the isosurf modification? In the code I posted, w and h are often around 60 or so (meaning 60 triangle strips each with 120 vertices in the displaylist), at least for all of the objects which ever show any of these problems. Might it be a buffer size issue? -- http://trikuare.cx ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
