search

ValveSoftware / vogl

OpenGL capture / playback debugger.
MIT License
1.42k stars 126 forks source link

Invalid Enum in libvogltrace #39

Open fscan opened 10 years ago

fscan commented 10 years ago

GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_VERTEX_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_COLOR_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_INDEX_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_SECONDARY_COLOR_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_FOG_COORDINATE_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_NORMAL_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_EDGE_FLAG_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) (vogltrace) Error: vogl_context::peek_and_drop_gl_error (1549): GL error GL_INVALID_ENUM occurred internally while libvogltrace was making GL calls. This GL error will not be seen by the client app (THIS SHOULD NOT HAPPEN)

I'm using mesa git with 3.1 core profile, maybe mesa is more strict about this? Looking at the specs these values are indeed not allowed for glIsEnabled.

I dont know what the invalid operation is about. In the app i want to trace i use 1 unsupported extension (KHR_debug), could this be a problem?

richgel999 commented 10 years ago

Looks like we're calling some glIsEnabled() on some things that are compat profile only. I can check this out. Also, we have done basically zero testing on mesa yet and it's very likely there are some things we need to fix on our end.

BTW - I'm going to add KHR_debug (and 1 or 2 other debug related things) next, after I finish looking at Xonotic. Should have this done sometime this weekend.

-Rich

On Fri, Mar 21, 2014 at 2:27 PM, fscan notifications@github.com wrote:

GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_VERTEX_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_COLOR_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_INDEX_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_SECONDARY_COLOR_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_COORD_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_FOG_COORDINATE_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_NORMAL_ARRAY) GL_DEBUG: GL_INVALID_ENUM in glIsEnabled(GL_EDGE_FLAG_ARRAY) GL_DEBUG: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) (vogltrace) Error: vogl_context::peek_and_drop_gl_error (1549): GL error GL_INVALID_ENUM occurred internally while libvogltrace was making GL calls. This GL error will not be seen by the client app (THIS SHOULD NOT HAPPEN)

I'm using mesa git with 3.1 core profile, maybe mesa is more strict about this? Looking at the specs these values are indeed not allowed for glIsEnabled.

I dont know what the invalid operation is about. In the app i want to trace i use 1 unsupported extension (KHR_debug), could this be a problem?

Reply to this email directly or view it on GitHubhttps://github.com/ValveSoftware/vogl/issues/39 .

fscan commented 10 years ago

Thx for the quick reply. To follow up, there are problems when replaying too. Invalid glIsEnable's and glGetTexEnv's (deprecated in 3.1). It seem mesa is much stricter than the binary drivers.

fscan commented 10 years ago

Quick update .. with the newest version most of the errors are gone and i can inspect most of the state in vogleditor. One error i get is that the editor calls Get with GL_TEXTURE_BINDING_CUBE_MAP_ARRAY_ARB although i'm on gl 3.3 and don't have the texture_cube_map_array extension. Also, should i be able to inspect the layers of a texture array? i only see the layer at depth 0.

richgel999 commented 10 years ago

Hi fscan - I don't think Peter has layers in yet. The texture viewer is very much a work in progress right now. LunarG is providing us with some new code to convert the image formats, and Peter will be working more on the actual viewer code very soon.

On Fri, Apr 4, 2014 at 10:40 AM, fscan notifications@github.com wrote:

Quick update .. with the newest version most of the errors are gone and i can inspect most of the state in vogleditor. One error i get is that the editor calls Get with GL_TEXTURE_BINDING_CUBE_MAP_ARRAY_ARB although i'm on gl 3.3 and don't have the texture_cube_map_array extension. Also, should i be able to inspect the layers of a texture array? i only see the layer at depth 0.

Reply to this email directly or view it on GitHubhttps://github.com/ValveSoftware/vogl/issues/39#issuecomment-39591349 .