<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - glClear requires GL_DEPTH_TEST enabled to clear depth buffer"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111008">111008</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>glClear requires GL_DEPTH_TEST enabled to clear depth buffer
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>18.3
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>GLX
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>nathan@acmeaom.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>AFAICT with a 3.3 core profile context, glClear should clear the depth buffer
regardless of the state of the depth test.
>From <a href="http://docs.gl/gl4/glClear">http://docs.gl/gl4/glClear</a>:
"The pixel ownership test, the scissor test, dithering, and the buffer
writemasks affect the operation of glClear. The scissor box bounds the cleared
region. Alpha function, blend function, logical operation, stenciling, texture
mapping, and depth-buffering are ignored by glClear."
I see no mention of the depth test affecting glClear. And, according to Alfonse
Reinhart in this discussion thread, the depth test should not affect clear:
<a href="https://community.khronos.org/t/glclear/73899/4">https://community.khronos.org/t/glclear/73899/4</a>
Maybe I'm confused though, and disabling the depth test is somehow equivalent
to disabling the depth write mask?
Mesa 18.3.6 DRM 3.27.0 Radeon RX Vega</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>