X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=src%2Fmesa%2Fmain%2FKNOWN_BUGS;h=efbb0ca40fc465dd2cdee0af9382342093c37549;hb=263581bba4d61291c54313648063a30c47106f0b;hp=9c9076bfedc421db93871af8a93c59262a4fd8af;hpb=afb833d4e89c312460a4ab9ed6a7a8ca4ebbfe1c;p=mesa.git diff --git a/src/mesa/main/KNOWN_BUGS b/src/mesa/main/KNOWN_BUGS index 9c9076bfedc..efbb0ca40fc 100644 --- a/src/mesa/main/KNOWN_BUGS +++ b/src/mesa/main/KNOWN_BUGS @@ -1,20 +1,21 @@ -$Id: KNOWN_BUGS,v 1.1 1999/08/19 00:55:41 jtg Exp $ Performance issues with EXT_point_parameters & quake2 -Broken drivers: - --> After integration of the changes in kw3, only the X and FX -drivers are known to work. Windows and D3D are known to be broken, -and all others are suspected to be broken. Please test your driver -and update this entry when more is known. +Using glPolygonMode() where the front and back modes aren't the +same causes poor performance on 3Dfx. -Separate specular color interpolation isn't implemented for points and -lines. Also, will have to add specular color add to pb.c (pixel buffer -code). +Broken drivers: some of the Mesa device drivers (such as BeOS, D3D, +etc) haven't been updated for Mesa 3.3's device driver changes. + +glDrawRangeElements() should use vertex array locking to improve performance +but trying to do so causes a rendering error. Reported by Scott McMillan. +Fixed by disabling locking in glDrawRangeElements (varray.c) but that's +really just hiding a bug in array locking. +