![]() ![]() ![]() There are several OpenGL ES 1.1/2.0 debugging tools from GPU vendors. GDEBugger, previously the answer to this sort of question on Stack Overflow, is now at version 5.8 - it's gone free, which is nice, but no longer supports OpenGL ES 2 (under Windows, no ES2-renderable config is available through EGL under OSX, there is no way to attach the debugger to an app running either in the simulator or on the real device) - which is not as nice.Īm I missing something obvious? What are my options? How do others debug their scenes? ![]() In particular, they do not capture vertex/index buffer or texture data (OSX instruments doesn't capture shader source either). Neither PVRTrace nor the OSX instruments appear to capture enough state for debugging this kind of problem. What I'm after at this point is a Pix / GPAD - like tool that will let me step through the scene and review state I cannot directly query from OpenGL at the point of the draw call in question (e.g. In said app, I have one particular draw call that results in no pixels written to the target, even though all the state I can query looks sensible (viewport, depth test/stencil test/cull/blend off, framebuffer complete etc), and AFAICT I am submitting sensible vertex data. It compiles and runs in the iPhone/iPad simulators, on a real iPhone/iPad, and under Windows using Imgtec's emulator libraries (i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |