https://bugs.freedesktop.org/show_bug.cgi?id=61412
--- Comment #21 from James Ogden <rexhunte...@gmail.com> --- (In reply to comment #20) > Well if it's really a fallback, you could set a breakpoint in > _mesa_meta_Bitmap and check what state is set which causes it right at the > beginning of the function. Ideally there wouldn't be any fallbacks there but > I guess it would be quite some work. I ran it with GL_FOG forced off, seems that did the trick, Intel is back to being faster than my discrete NVidia card. Haha, the irony. Well thanks to software side state checking, I managed to get this fixed so now we know it's a fallback of some kind related to fog with glBitmap, not sure if we should mark as resolved or if it should be left open until the issue is looked at? Anyway thanks for all the help guys! (or gals if any) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
