Re: [osg-users] OpenGL capture/logging in OSG

2010-01-06 Thread Michael Weiblen
Hi Paul I'm also interested in the ogldump route, specifically because of the automated wrapper generation. cheers -- mew On Mon, Dec 14, 2009 at 2:06 PM, Paul Martz pma...@skew-matrix.com wrote: ... I don't know if this might help, but Don Burns wrote a parser of the gl.h to

Re: [osg-users] OpenGL capture/logging in OSG

2009-12-14 Thread Robert Osfield
Hi Paul, I'm still open to suggestions on the make up of what your are looking, but I don't yet think you have the right design combination to avoid pitfalls of it's own. Though discussion perhaps we can arrive at a better solution, be it OSG intrusive or done externally. On Fri, Dec 11, 2009

Re: [osg-users] OpenGL capture/logging in OSG

2009-12-14 Thread Paul Martz
Hi Robert -- Robert Osfield wrote: Having a single class is not extensible by end users - something which is essential for authors of external NodeKits. It's not a requirement that external source use the new interface for calling OpenGL. If they don't use it, code will still function

Re: [osg-users] OpenGL capture/logging in OSG

2009-12-11 Thread Alberto Luaces
Another program worth for considering would be Bugle (http://www.opengl.org/sdk/tools/BuGLe/). Just my 2 cents. -- Alberto ___ osg-users mailing list osg-users@lists.openscenegraph.org

Re: [osg-users] OpenGL capture/logging in OSG

2009-12-11 Thread Robert Osfield
Hi Paul, My instinct would be to be not recommend trying to add some extra level of indirection in OpenGL calls to the OSG, from a maintenance and performance perspective. Considering most of us can get by without it it's sure note a cost that I ever want to push out to everyone. Cost of

Re: [osg-users] OpenGL capture/logging in OSG

2009-12-11 Thread Paul Martz
Responding to all three posts at once... Chris 'Xenon' Hanson wrote: I think I've used glIntercept before and dfound it pretty useful. What was the motivation in not building on it? Lack of support for multiple threads, and no obvious way to add that support, was one reason for abandoning

Re: [osg-users] OpenGL capture/logging in OSG

2009-12-11 Thread Chris 'Xenon' Hanson
On 12/11/2009 9:46 AM, Paul Martz wrote: Lack of support for multiple threads, and no obvious way to add that support, was one reason for abandoning it. Also, when I attempted to use GLIntercept with (single threaded) OSG, I encountered problems as described recently in the discussion thread

[osg-users] OpenGL capture/logging in OSG

2009-12-10 Thread Paul Martz
Hi all -- I have some funding to capture OSG's OpenGL calls. This is required for development, debugging, and performance analysis work that I am currently contracted for. I have already ruled out updating GLIntercept for this purpose. Purchasing gDEBugger is a possibility. However, the