Robert Osfield wrote:
On 8/30/06, *Chris Hanson* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Farshid Lashkari wrote:
> Hi Chris,
> I use the SharedStateManager to share textures amongst all my loaded
> models. So I create the manager like so:
Thanks for the succinct overview, it's exactly what I was looking
for.
Was this in a document somewhere that I missed?
No, but it would be a good starting place for a page on the wiki ;-)
When I knew what to look for, I found this:
http://openscenegraph.net/pipermail/osg-users/2004-January/037535.html
Which sort of implies I should just switch on the SharedStateManager that is already in
the osgDB::Registry singleton, and let it do its work.
Is this the case?
There were some hints in the thread about it not being fully functional in State
sharing mode:
Alberto Farre afarre at evalfa.com:
I still have some problem with sharing StateSets that makes some texture
swapping. Perhaps I am misundestanding something about StateSet comparision,
is it comparing all included textures?
Anyone know about this?
Also, I'm not clear on how it identifies the commonality of textures in order to share
them. I looked over the code, but didn't really see how it determined if two textures were
common and could be shared. I did see that they needed to be DataVariance ==
osg::Object::STATIC.
--
Chris 'Xenon' Hanson aka Eric Hammil | http://www.3DNature.com/ eric at logrus
"I set the wheels in motion, turn up all the machines, activate the programs,
and run behind the scenes. I set the clouds in motion, turn up light and
sound,
activate the window, and watch the world go 'round." -Prime Mover, Rush.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
