Am Donnerstag, den 30.11.2006, 08:36 +0000 schrieb Robert Osfield: > Hi Michael, > > The current osg::HeightField's purpose is primarily as a primtiive to > be used for collision detection/pyhsics modelling rather than > visualization. The osg::ShapeDrawable is just a convenience class > rather than a flexible, high performing way to visualize heighfields. > > osgTerrain/osgdem exist for terrain visualization and it supports > multi-texturing. Next year I'll add some specific high performance > paths for height fields to osgTerrain, but right now you'll need to > use the off line database capabilities of osgTerrain. > > Alternatively you can use TexGen and StateSet inheritance for a second > texture that you wish overlay. See osgmultexture for an example of > this. This will work with any subgraph, be one containing a > ShapeDrawable or a whole paged database generated by > osgTerrain/osgdem. > > Robert.
Hi Robert, I've looked into osgTerrain already, but it looked quite complicate to me. I also haven't found an example for Heightfield node etc. Maybe I think to strange and it's easier as it looks like. Here is a quick description of our project. (Maybe you can give us a hint how to approach the multi texture problem.) At the moment we use a Heightfield with one texture. On the Heightfield stands a excavator which digs in the Heightfield. The Heightfield of course changes its height. Now we want to show the different materials by using different textures. Maybe you can describe how to use osgterrain/(heightfieldnode???) to realize that ? thnx again Michael _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
