Hi About optimizer - i would rather count this one as misusage. And for transparent stuff with depth write disabled by default - there are some cons for this (alpha masked geometry with alpha test f.e.). And if you want correct blending you should draw transparent objects after solid and sort them either back to front or front to back (depending on blending function), in case of back to front sorting there are no difference between depth write enabled or disabled anyway (as long as sorted objects not overlap). So disabling depth write would only help in cases when sorting are not an option for some reason, sorted objects overlaps(in depth), or objects are very transparent (as in latter case draw order often dont make big visual difference, at least you cant say that something completely wrong looking at picture :)
Cheers 26.01.2012, 20:19, "Sebastian Messerschmidt" <[email protected]>: > Anyone any hint regarding this? > > I'd really need an advice if I should fix the optimizer or where to > solve this. > > cheers > Sebastian > >> Hello, >> >> I've encountered a problem when using the OpenFlight plugin with >> preserveFace/preserveObject option not used. >> If the perserveFace options is not used, the importer uses the >> Optimizer with the following options: >> >> osgUtil::Optimizer::SHARE_DUPLICATE_STATE | >> osgUtil::Optimizer::MERGE_GEOMETRY | >> osgUtil::Optimizer::MERGE_GEODES | >> osgUtil::Optimizer::TESSELLATE_GEOMETRY | >> osgUtil::Optimizer::STATIC_OBJECT_DETECTION; >> >> This unfortunately breaks the sorting of transparent objects, as in my >> example all forests (represented by simple quads/polygons) are put >> into one geode. >> After digging into the optimizer, I realized, that it will not check >> if the statesets contain any transparency. >> Would you consider this rather a bug in the Optimizer or more a >> mis-usage in the OpenFlight importer? >> >> As the osgviewer doesn't disable depth writes for transparent objects, >> the problem is only visible if you use the transparent-bin with depth >> writes off, which leads me to another question: >> >> Would it be wise to turn off depth writes for the transparent bin by >> default ( or a least make it configurable for the osgviewer)? >> >> cheers >> Sebastian >> >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
