Brian Paul wrote:
>
> Keith Whitwell wrote:
>
> > Size zero texcoords certainly sounds like a bug to me. The fact that
> > stride is 8 would indicate we're pulling data from a vertex array, so
> > yes this does narrow things down. Do you know if CVA is active at this
> > point? Can you try re-running the demo using a MESA_CONFIG which
> > disables the CVA extension, or a quake flag which does the same?
> >
> > If Q3 is like Q1 and Q2, there should be a console command something
> > like '_windowed_mouse 0', or a command line arg '+set _windowed_mouse
> > 0'... Invaluable for debugging.
>
> I tried disabling CVS. No change.
>
> I've tried with your update to cva.c. It stopped the segfault but
> now there's serious rendering errors to fix. Namely, all polygons
> appear in shades of gray. Perhaps texture coordinates are fouled
> up.
OK - I've committed a couple of small fixes & Q3 runs ok in cva mode.
Does anyone know what happened to the assembly code in the FX driver?
In particular the vertex-snapping code? It would be good to restore
this in the current version - two unnecessary divides per vertex is
pretty wasteful.
Keith
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
