On Jan 10, 2008 3:16 PM, Jean-Sébastien Guay <[EMAIL PROTECTED]> wrote: > Yep, seems so. osgdem still running... I probably should have chosen a > smaller dataset as a first test. :-)
If its a dataset with DEM's try adding --terrain to the command line, it builds much, much faster using osgTerrain::Terrain to store the GeightFields rather than creating osg::Geometry meshes from the DEM's and then simplifying these (its the simplification which is slow). The --terrain functionality is very early days though (checked in yesterday) so there are still a few loose ends, but its certainly enough to have a first pass look. > > Once I've completed some more work on > > VPB I'll do a write up on all the new functionality and then strike up > > a discussion on osg-users about how to tackle distributed builds under > > Windows/mixed networks, I'll need suggestions from the community on > > this part though, the best I can do is say how things work under unix > > and trust in windows experts for a similar solution under Windows. > > Looking forward to it. I imagine if distributed builds work, it should > be possible to use multiprocessor/multicore machines in the same way, > by just specifying the same machine multiple times? Right now osgdem > is taking only 25% of my spiffy quad-core CPU! :-( Yep, you can use multiple cores, and multiple machines, or multiple cores on one machine, all managed via the new vpbmaster app. osgdem itself has some preliminary multi-threaded support to, but not yet to the level afforded by running multiple osgdem's in parallel. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
