Hi J-S,
No, we use the ViewBounds type. and I forgot to mention in my arguments to
reproducing the results in the osgshadow example that I also used
ViewBounds. Sorry about that, seems even with my very long post I was
still missing some specifics :-)
Command line for osgshadow was not indicating this. Default is DrawBounds
and I assumed you use this.
One problem unfortunately is that some textures could not be included in
the atlases (because they are set to REPEAT), and sometimes not only
textures change, but also some render state such as cull face (some fences
made with a single polygon set to render both sides, for example). I'll
have to get our artist to model these kinds of things as boxes, and
replace the textures set to REPEAT.
Yeah, but if we can remove texture state attributes we may usually get rid
of majority of StateSets and end up with really small number of unique
StateSets created by combinations of remaining attributes. Textures cannot
be always put into Texture atlasses thats why we finally built
Texture2DArray. Btw I just noticed you mentioned that you can send your DB
for others to check. If you want you may send it to me, I may try to run the
same tool on your DB and report what I got.
Cheers,
Wojtek
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
