Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Querying fragment varying out variable names

  1. #11
    Junior Member Regular Contributor
    Join Date
    Dec 2009
    Posts
    211
    Quote Originally Posted by aqnuep View Post
    You can't really drop the GL client/server model as it is needed for remote rendering which, even though it's surprising, is still used.
    This is getting a bit off-topic, but the ARB stopped extending the GLX protocol somewhere before OpenGL 3.0., so you're restricted to pretty ancient functionality if you use remote rendering.

  2. #12
    Member Regular Contributor
    Join Date
    Apr 2004
    Posts
    251
    menzel, what do you mean by "fragment varying out variable"? 'Varying' was used for the interpolators that link vertex/geometry with fragment shaders, but now the term is dropped altogether.
    If you mean just the fragment shader outputs, then i'm for it. If vertex attribs and uniforms can be queried then fragment outputs should too, at least for consistency.
    There are APIs (BindFragDataLocation, GetFragDataLocation) that accept those names as arguments but there is no way to find what the names are (except by parsing the shader text by hand).
    I think this inconsistency should be addressed.

  3. #13
    Member Regular Contributor
    Join Date
    Jan 2012
    Location
    Germany
    Posts
    325
    I_belev : Yes, I mean the fragment shader outputs.

  4. #14
    Member Regular Contributor
    Join Date
    Apr 2004
    Posts
    251
    As for it's usefulness, it sure is useful. For example you can think of some wrapper library that stays between the application and the OpenGL. That wrapper does not know the names of the fragment output variables in the shaders that the application gives (its a separate piece of software) but it still may want to do something with them (depending on what is the purpose of the wrapper).

  5. #15
    Member Regular Contributor DmitryM's Avatar
    Join Date
    Mar 2009
    Location
    Toronto
    Posts
    435
    I'm disappointed that my words were misinterpreted and ignored. Here is the whole article explaining why I need that:
    http://claymore-dev.blogspot.com/201...ification.html

  6. #16
    Member Regular Contributor
    Join Date
    Mar 2001
    Posts
    469
    Have you looked into this GL 4.3 feature, especially issue (2)?

    http://www.opengl.org/registry/specs...face_query.txt

  7. #17
    Senior Member OpenGL Guru
    Join Date
    May 2009
    Posts
    4,948
    I'm disappointed that my words were misinterpreted and ignored.
    Welcome to three months ago; glad you could make it. I even made a convenient OpenGL Wiki article on the topic.

  8. #18
    Member Regular Contributor DmitryM's Avatar
    Join Date
    Mar 2009
    Location
    Toronto
    Posts
    435
    Thanks ScottManDepth and Alfonse!

    My knowledge of cutting-edge GL is not up to date, and looking for fragment output queries got me only to this thread.

    That's nice to finally have this functionality in GL4.3! I'm still a bit sad that it's not possible to query fragment outputs on my R700.

  9. #19

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •