[osg-users] disabled lighting after migration

Robert Osfield robert.osfield at gmail.com
Wed Jan 17 06:06:37 PST 2018

Hi Sebastian,

It's not possible to determine what is wrong from the details given.
The best I can do is provide some general pointers.

What can happen when upgrading is that more recent version contain
fixes/tighten up ambiguities such that things that worked by fluke in
older releases now behave differently because the OSG is now doing
exactly what the scene graph is telling it to do.

Another possibility to look is what is happening in any custom code
you have - could it be leaking state?


On 17 January 2018 at 12:54, Sebastian Schmidt <herrdersuppen at gmail.com> wrote:
> My scene contains a node, a RTT drawable with custom camera like in the osgprerender example.
> The drawable is initialized and rendered after i set up the compositeviewer/mastercamera during runtime via a osgDB::ReaderWriter plugin.
> In the drawable's drawImplementation() function i do lot of glEnable/glDisable calls.
> After migration from osg 3.0.1 to 3.4.1 my whole scene is rendered with disabled lighting
> and when i try to reactivate lighting with pressing "L" only a very small part of my scene is affected.
> I have already fixed culling problem by calling setGlobalDefaults() for my custom cameras, but i don't how to fix this. Maybe it has something to do with changes in render states/orders.
> ------------------------
> OSG Version: 3.0.1
> OS: OpenSuse Leap 42.1
> ------------------
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=72769#72769
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

More information about the osg-users mailing list