<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Distant geometry renders in front of closer geometry (depth test fail) in DarkRadiant / wxWidgets" href="https://bugs.freedesktop.org/show_bug.cgi?id=92286#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Distant geometry renders in front of closer geometry (depth test fail) in DarkRadiant / wxWidgets" href="https://bugs.freedesktop.org/show_bug.cgi?id=92286">bug 92286</a> from <a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> Roland Scheidegger</a> <pre>(In reply to MirceaKitsune from <a href="show_bug.cgi?id=92286#c1">comment #1</a>) > I guess the question of this bug report remains whether Mesa is doing > something wrong here. On the proprietary video drivers, it's ok to leave the > attribs parameter of wxGLCanvas empty... but for depth buffering to work on > Mesa, you must include WX_GL_DEPTH_SIZE and give it a buffer size. > > So if anyone here is familiar with wxWidgets, please take a look at this. If > you think Mesa is doing the right thing, this report can be closed. I don't > know enough to decide that, but to me it feels like depth testing being the > only thing that doesn't work in this scenario denotes a problem. I'm not familiar with wxWidgets, but this definitely doesn't sound like a mesa bug. If you don't explicitly request a visual with depth bits, then you may or may not get a depth buffer, and it looks like it just happens some proprietary drivers will give you a visual with it but mesa won't.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>