-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Harald JOHNSEN wrote: > Tim Moore wrote: > >> >> >>> To recap we have (or should have in the future) : >>> - one drawable per model / part of model >>> - one texture per texture loaded >>> - one state per static / animation material >>> - adding a 'model' will add a geode with a new state pointing to a >>> cached texture and to a cached drawable >>> >>> >> There's no reason not to share the geode too. >> Also, you really want to share StateSets if possible, because OSG will >> order all the drawables by StateSet to avoid state changes, but it >> doesn't look inside StateSets to minimize state changes. >> >> > Yes by states I was thinking of statesets. Anyway I looked again the > geode and drawable definitions and now > I'm confused, I thought the states were tied to the geodes but they are > tied to the drawable. I really don't > understand how we can have one drawable with several states. > StateSets can be put in any node in the scene graph. If you want to share drawables with different StateSets, the StateSets would go in the geodes above the drawables and the drawables wouldn't have StateSets.
Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGQK2qeDhWHdXrDRURAhYaAJsHipnQduWuIR3+ijgfYRaPOl2TTACfVIsk tpp4yP2toJCxYKVGtSy5HlI= =yMjv -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
