Re: [osg-users] Qt OpenGL Warning opengl

HI Auke-Dirke, On 25 April 2016 at 14:07, Auke-Dirk Pietersma wrote: > I have the following issue. Whenever i choose to render a scene with > opengl greater than 2.1 i get the following messages. > > Warning: detected OpenGL error 'invalid enumerant' after applying GLMode > 0xb50 > Warning: dete

[osg-users] compositeviewer with mutliple windowmanager

What is the normal approach to create multiple windows, each filled with widgets and/or 3d models? In my opinion i only need to merge the code in osg examples for osgwidgetwindow and osgcompositeviewer. So i created two windowmanager and stuff for each view and added them to the compositeviewe

Re: [osg-users] osgVolume::MultipassTechnique use

Hi Alex, A stack trace with debugging info would be far more useful and should be able to pinpoint the cause of the crash, or at least give some clues of where to look. Also, does the osgvolume example crash when you use the MultiPassTechnique? Robert. On 26 April 2016 at 21:35, Alex Taylor wr

Re: [osg-users] OpenSceneGraph 3.4.0, latest git master: build of ffmpeg plugin fails after upgrade to ffmpeg 3.0+

I have created a pull request to commit this ffmpeg3 patch against the master OpenSceneGraph repository on GitHub: https://github.com/openscenegraph/OpenSceneGraph/pull/70 Regards, Ben -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=66984#66984

Re: [osg-users] OpenSceneGraph 3.4.0, latest git master: build of ffmpeg plugin fails after upgrade to ffmpeg 3.0+

Hi Ben, On 27 April 2016 at 10:22, Ben Woods wrote: > I have created a pull request to commit this ffmpeg3 patch against the > master OpenSceneGraph repository on GitHub: > https://github.com/openscenegraph/OpenSceneGraph/pull/70 > For now the official route for submissions to send whole modifi

Re: [osg-users] ShaderComposer::releaseGLObjects warning

Hi Andy, On 26 April 2016 at 20:31, Andy Skinner wrote: > Thanks for that fix. There is a remaining issue, and I'm not sure if you > would see it as a bug or a dodgy compiler warning. :) > > > > We get a similar message about osgUtil::CullVisitor::clone(). > > > > NodeVisitor uses META_Object,

[osg-users] Use cases of MultipassTechnique?

All, I've posted recently with a debugging question related to my exploration of MultipassTechnique. Robert has provided guidance on how to proceed with my debugging problem, but I have a conceptual question about what the practical use cases are when a person would choose to use MultipassTechniqu

Re: [osg-users] ShaderComposer::releaseGLObjects warning

Yes, the "using" statement does quiet the warning. Does that mean this is the solution, or that this just shows that there isn't a problem? The reason I ask is that we've discussed the "using" statement for things like this before, and I don't believe you were in favor of it. But using it wou

Re: [osg-users] Use cases of MultipassTechnique?

HI Alex, MultiPassTechnique will be able to handle rendering of 3D elements that intersect the volume, this includes arbitrary slice geometry like in the example. Simply create the slice geometries yourself with the appropriate texture mapping and then place them in the scene. When the MiltiPass

Re: [osg-users] ShaderComposer::releaseGLObjects warning

Hi Andy, On 27 April 2016 at 19:09, Andy Skinner wrote: > Yes, the "using" statement does quiet the warning. > Good to hear. > > > Does that mean this is the solution, or that this just shows that there > isn't a problem? The reason I ask is that we've discussed the "using" > statement for t

Re: [osg-users] ShaderComposer::releaseGLObjects warning

So, to be clear, we'll leave it as is? thanks andy Needing to put a using in lots of places across the OSG to just quieten inappropriate warnings is pretty crappy. The more superfluous code you have in your code base the less easy it is to read, the easier it to break. This makes me very wa