Comments on: Plugins: Check the OpenGL Error (in Debug Mode Only) https:/2012/03/plugins-check-the-opengl-error-in-debug-mode-only/ Developer resources for the X-Plane flight simulator Tue, 20 Mar 2012 15:12:56 +0000 hourly 1 https://wordpress.org/?v=6.6.1 By: Ben Supnik https:/2012/03/plugins-check-the-opengl-error-in-debug-mode-only/#comment-4638 Tue, 20 Mar 2012 15:12:56 +0000 http://xplanedev.wpengine.com/?p=4213#comment-4638 In reply to Philipp Münzel.

There are only two true debug methods: divide and conquer and printf. 🙂

]]> By: Philipp Münzel https:/2012/03/plugins-check-the-opengl-error-in-debug-mode-only/#comment-4634 Tue, 20 Mar 2012 15:01:29 +0000 http://xplanedev.wpengine.com/?p=4213#comment-4634 Good advise. Unfortunately you can’t backtrace a gl error more easily than “bisecting” your code with glGetError until you find the line where you induced it. We once had to chase one of those infamous error “1282” in code we hadn’t written and apparently no one had read in the last 5 years.
Fortunately, bisection always converges, despite it is slow 🙂

]]>