Bug 789

Summary:	Require entry points GL4.glDrawArraysIndirect(int, long) and GL4.glDrawElementsIndirect(int, int, long)
Product:	[JogAmp] Jogl	Reporter:	Julien <julien.carlos>
Component:	opengl	Assignee:	Sven Gothel <sgothel>
Status:	RESOLVED FIXED
Severity:	major
Priority:	---
Version:	2
Hardware:	All
OS:	all
Type:	---	SCM Refs:	1259693f21734b0ebe1b5c95688ad91956c2629c
Workaround:	---
Bug Depends on:
Bug Blocks:	852

Description Julien 2013-07-26 10:43:00 CEST

glDrawArraysIndirect and glDrawElementsIndirect have been designed to read parameter data from the buffer currently bound to GL_DRAW_INDIRECT_BUFFER. In OpenGL 4 core profile it is the only way to use these methods. 
Only the compatibility profile allows passing parameter data from client memory buffers. 
Therefore jogamp must provide entry points for glDrawArraysIndirect and glDrawElementsIndirect where the last argument is an offset in the buffer currently bound to GL_DRAW_INDIRECT_BUFFER.

Since that's not the first time I file a bug for jogamp, if I can contribute I would be glad to :-)!

Comment 1 Sven Gothel 2013-08-03 19:03:07 CEST

(In reply to comment #0)
> glDrawArraysIndirect and glDrawElementsIndirect have been designed to read
> parameter data from the buffer currently bound to GL_DRAW_INDIRECT_BUFFER.
> In OpenGL 4 core profile it is the only way to use these methods. 
> Only the compatibility profile allows passing parameter data from client
> memory buffers. 
> Therefore jogamp must provide entry points for glDrawArraysIndirect and
> glDrawElementsIndirect where the last argument is an offset in the buffer
> currently bound to GL_DRAW_INDIRECT_BUFFER.
> 
> Since that's not the first time I file a bug for jogamp, if I can contribute
> I would be glad to :-)!

Of course - you are more than welcome to contrib.

Simply send me an email w/ your git patch (git am'endable),
some git repo to fetch your branch and to pull from
- or - a git pull request using github.

Since this seems similar to the prev. reported issues, I guess we can simply
use the last git patch and doing same for this one (pls add bug reference .. etc).

Thank you!

Comment 2 Sven Gothel 2013-10-06 15:57:34 CEST

fixed, see commit 1259693f21734b0ebe1b5c95688ad91956c2629c