Bug 12410

Summary:	Incomplete primitive rendering with GL_LINE_LOOP over a surface on 945GM
Product:	Mesa	Reporter:	David Henry <tfc.duke>
Component:	Drivers/DRI/i915	Assignee:	haihao <haihao.xiang>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	xorg.log test case test case screenshot, showing the bug screenshot of the test case with Option NoAccel

Description David Henry 2007-09-13 10:01:47 UTC

Drawing an object with GL_LINE_LOOP on top of an already drawn surface (in 2D) results in incomplete rendering of the lines. It works if the bottom surface isn't drawn, or if we draw the same object with GL_LINES.

The problem doesn't appear if Option NoAccel is set to true (so not a Mesa bug). It also works on Nvidia with proprietary driver.

OpenGL renderer string: Mesa DRI Intel(R) 945GM 20061017 x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 7.0

Comment 1 David Henry 2007-09-13 10:02:24 UTC

Created attachment 11537 [details]
xorg.log

Comment 2 David Henry 2007-09-13 10:03:45 UTC

Created attachment 11538 [details]
test case

The test case draws two triangles with GL_LINE_LOOP on top of a blue surface (in 2D mode). The left triangle is drawn using GL_LINE_LOOP, the right triangle is drawn using GL_LINES.

Comment 3 David Henry 2007-09-13 10:04:21 UTC

Created attachment 11539 [details]
test case screenshot, showing the bug

Left triangle is incomplete

Comment 4 David Henry 2007-09-13 10:04:59 UTC

Created attachment 11540 [details]
screenshot of the test case with Option NoAccel

It shows that it works in software mode, without DRI.

Comment 5 Roland Scheidegger 2007-12-22 09:58:42 UTC

This should be fixed in master and mesa_7_0_branch, though I didn't test with this chipset. Reopen if not.

Comment 6 Adam Jackson 2009-08-24 12:28:01 UTC

Mass version move, cvs -> git

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.