Forums - glDebugMessageInsert call messes up Resources window data

1 post / 0 new
or Register
glDebugMessageInsert call messes up Resources window data
alexpete
Join Date: 2 Dec 20
Posts: 1
Posted: Wed, 2020-12-02 13:41
Top

TLDR if your Resource window is showing incorrect data, try removing any glDebugMessageInsert calls.

In my Pixel 3 capture the Resources window was showing the data for the next draw call, instead of the selected one.  For example if I had two draw calls in my program:

glDrawElements()
  .. various gl calls ...
  glUseProgram ( program = 112)
  .. more gl calls ...

glDrawArrays(...)
   ... bunch of gl calls...
   glUseProgram ( program = 115 )
   .. more gl calls ...
 

If I select the first draw call (glDrawElements ) in the Data Explorer window, it shows the resources for the second draw call (glDrawArrays) in the Resources window.  

Turns out I had a glDebugMessageInsert call earlier on, all the resource data before that was OK, but after that call it was off by one.  After I removed the glDebugMessageInsert call the Resources window showed the correct data.

  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.