GL 4.6: GL_PARAMETER_BUFFER and memory barriers #17
Assignees
Comments
ghost
assigned 
|
This only affects the drawcount. COMMAND_BUFFER_BARRIER_BIT should be extended to mention MultiDraw*IndirectCount. While we're at it, the type of the maxdrawcount of MultiDrawArraysIndirectCount should be sizei (like MultiDrawElementsIndirectCount). |
|
I assume you mean |
|
Yeah, obviously :) |
|
Discussed in the WG meeting today. We agree with Nicolai's suggestion. @nhaehnle can you make a proposed spec change here for Jon to incorporate? Thanks. |
nhaehnle
added a commit
to nhaehnle/OpenGL-Registry
that referenced
this issue
Oct 23, 2017
Otherwise, there is no way to reliably write to a PARAMETER_BUFFER_ARB from a shader. Issue: KhronosGroup/OpenGL-API#17
|
Also sent a pull request for the spec internally. Not sure if that's the best procedure, but it's only a handful of words that change... |
|
This will be fixed in the next public spec update. |
|
(Coming soon). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ARB_indirect_parameters (and the equivalent GL 4.6 specification) does not define a
glMemoryBarrierbit that allows writes from image load/store and SSBOs to be visible to parameter buffer reads. And none of the existing barriers are stated to provide this functionality.So at present, it seems impossible to use image load/store or SSBOs to write indirect parameters. Only atomic counters can write to them from shaders, assuming that is the intent of the atomic counter feature.
The text was updated successfully, but these errors were encountered: