Hi Wener, On 28 March 2017 at 16:24, Werner Modenbach <[email protected]> wrote:
> I know it is actually not your duty giving help here but you are very > familiar with the driver calls and it would help a lot if you can provide > an idea what kind of setting might cause this issue. > I'm a very occasional Windows user so really don't have much experience with Windows drivers to be able help with driver settings. It's a long shot, but have your tried the OSG-3.4 branch or OSG master as these both contain a range of bug fixes/OSG improvements, there is chance that something has changed that might fix things. Whatever the cause is it seems to be some small OpenGL state difference between OSG-3.2 and OSG-3.4.0, I'm afraid I don't know what this might be. Perhaps using a 3rd party OpenGL debugging tool might help here - capture all the GL calls for 3.2.x and 3.4.x and see what the differences are. Robert.
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
