Module: Mesa Branch: master Commit: 728240b64d1263bfe2f6d52c3643f70b5719ccbc URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=728240b64d1263bfe2f6d52c3643f70b5719ccbc
Author: Brian Paul <bri...@vmware.com> Date: Fri Mar 8 10:32:39 2013 -0700 docs: document another Viewperf bug --- docs/viewperf.html | 29 +++++++++++++++++++++++++++++ 1 files changed, 29 insertions(+), 0 deletions(-) diff --git a/docs/viewperf.html b/docs/viewperf.html index ab2fd67..3bbe197 100644 --- a/docs/viewperf.html +++ b/docs/viewperf.html @@ -203,6 +203,35 @@ This causes the object in question to be drawn in a strange orientation and with a semi-random color (between white and black) since GL_FOG is enabled. </p> + +<h2>Proe-05 test 1</h2> + +<p> +This uses depth testing but there's two problems: +<ol> +<li>The glXChooseFBConfig() call doesn't request a depth buffer +<li>The test never calls glClear(GL_DEPTH_BUFFER_BIT) to initialize the depth buffer +</ol> +<p> +If the chosen visual does not have a depth buffer, you'll see the wireframe +car model but it won't be rendered correctly. +</p> +If (by luck) the chosen visual has a depth buffer, its initial contents +will be undefined so you may or may not see parts of the model. +<p> +Interestingly, with NVIDIA's driver most visuals happen to have a depth buffer +and apparently the contents are initialized to 1.0 by default so this test +just happens to work with their drivers. +</p> + +<p> +Finally, even if a depth buffer was requested and the glClear(GL_COLOR_BUFFER_BIT) +calls were changed to glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT) +the problem still wouldn't be fixed because GL_DEPTH_WRITEMASK=GL_FALSE when +glClear is called so clearing the depth buffer would be a no-op anyway. +</p> + + </div> </body> </html> _______________________________________________ mesa-commit mailing list mesa-commit@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-commit
