Display all textures? Support GL_KHR_debug object labels? #26

Closed
ahuillet opened this Issue Jun 16, 2011 · 4 comments

Projects

None yet

3 participants

@ahuillet

Hello,

I realize this may be slightly out of scope for apitrace, but I find myself often wondering what is the texture ID for a given texture I have in mind.

Would it be technically possible for apitrace to dump all existing textures, and display them? This is somewhat part of the state after all.

Thanks

@jrfonseca jrfonseca was assigned Feb 29, 2012
@jrfonseca
apitrace member

I actually think that even better would be for apitrace to support http://www.opengl.org/registry/specs/KHR/debug.txt and use human-legible labels provided by the application via glObjectLabel()/glObjectPtrLabel() , completely eliminating the bypassing the need of thinking in terms of ids or pointers.

@Amadiro

I agree that it be incredibly helpful if apitrace could help visualize the primitives from KHR_debug. Should I open a new, separate bugreport for this?

Examples:

  • when an object (buffer, texture, ...) is given a string-name, apitrace could refer to that object in the future with that string, and the integer ID (what opengl formally refers to as "name") in parens.
  • when the application places a debug message in the stream itself (glDebugMessageInsert(GL_DEBUG_SOURCE_APPLICATION, ...)) apitrace could highlight that in the command-stream, or maybe only show the message itself in a visually distinct style.
@jrfonseca
apitrace member

when an object (buffer, texture, ...) is given a string-name, apitrace could refer to that object in the future with that string, and the integer ID (what opengl formally refers to as "name") in parens.

See if the fix for issue #251 meets your needs.

I plan eventually to have objects like textures/FBOs etc to be highligthed and cross-referenced in the call list, but that is a major feature and it will take quite some time to get it done.

when the application places a debug message in the stream itself (glDebugMessageInsert(GL_DEBUG_SOURCE_APPLICATION, ...)) apitrace could highlight that in the command-stream, or maybe only show the message itself in a visually distinct style.

Fixed with issue #199 and ef8e1c9.

@jrfonseca
apitrace member

GL_KHR_debug has been fully supported for a while.

There is no plan to enable apitrace dump all textures. That would be too much data and make the UI inefficient.

So closing this one now.

@jrfonseca jrfonseca closed this Oct 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment