...I hate it when I do this... What about PROTECTED states? Could the nodes that aren't being "correctly" affected by your material have a PROTECTED state, which prevents your material from being applied?
See the thread "Override of an Override" for more information. Good luck... D.J. On Wed, Nov 2, 2011 at 4:43 PM, D.J. Caldwell <[email protected]>wrote: > Hi, again, Gianni... > > I think our design approach is largely due to the fact that we only wanted > to apply our material to very specific parts of the scene graph, and > applying a material at a group node in our scene might cause unwanted > material changes in other areas of the scene graph. > > So, I don't think it will actually help you in your case (but I could be > wrong; it happens often enough). > > Still, the approach has some merit if you want that fine tuned control > (and if it worked the way you wanted it to work). > > Sorry I couldn't help more... > > D.J. > > On Wed, Nov 2, 2011 at 1:13 PM, D.J. Caldwell <[email protected]>wrote: > >> Hi Gianni, >> >> In addition to the combined flag, I just noticed we are also applying the >> material as close to the geometry as possible. >> >> Let's say you have a top level group node that is your root. The >> children of that group can either be geometry nodes or other groups. In >> our project, when applying the new material, we essentially traverse each >> group node in search of geometry, and then only apply the material to the >> geometry nodes. >> >> I would warn you that this approach probably will not work very well for >> level of detail nodes, since the geometry is dynamically loaded/unloaded as >> needed as a function of viewing distance. In that case, you should >> probably apply the material to the top level node returned from the >> geometry loader, since that node is probably the only persistent node for >> that geometry. This is the approach we have taken, and we just accept >> whatever results we get. >> >> I would have expected your original approach to work, but, since it >> appears that does not work, you might try something like the above >> approach. I would hope this would get you closer to the results you're >> looking for, but I can't make any guarantees. How you would implement that >> approach will have to be up to you, since you know your goals and your >> system best. >> >> I hope this helps... >> >> D.J. >> >> On Wed, Nov 2, 2011 at 6:38 AM, Gianni Ambrosio <[email protected]>wrote: >> >>> Hi D.J. >>> unfortunately even with "OVERRIDE | ON" it doesn't work. >>> >>> Regards >>> Gianni >>> >>> ------------------ >>> Read this topic online here: >>> http://forum.openscenegraph.org/viewtopic.php?p=43684#43684 >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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
