Paul Martz wrote: > So it looks like if you "osgconv -O OutputTextureFiles in.ive out.osg" > that should do the trick.
Thanks for that tip. "It would have worked too, if it weren't for you meddling kids!" Oh, sorry, wrong script. I beat my forehead a bit on this because it wasn't working, and finally put some breakpoints in the .OSG Texture2D saver, only to find the OutputTextureFiles option code in Texture2D was never hit. Turns out, some dissection of the OSGDEM-created .osg scene file shows it does not use a Texture2D object, it uses something known as ImageLayer. The .osg output code for ImageLayer (in osgPlugins/osgTerrain/ImageLayer.cpp, ImageLayer_writeLocalData() ) does not support the OutputTextureFiles option. I confess I'm not really familiar with why ImageLayer is unrelated to Texture2D (it seems like one would be a subclass of the other). My goal at this point is to try to migrate the OutputTextureFiles support from Texture2D to ImageLayer, if that's something Robert feels is appropriate? So, apparently no one has ever tried using the OutputTextureFiles on OSGDEM/VPB terrain databases or they'd have noticed it was unimplemented. ;) > Paul Martz > Skew Matrix Software LLC > _http://www.skew-matrix.com_ <http://www.skew-matrix.com/> > +1 303 859 9466 -- Chris 'Xenon' Hanson, omo sanza lettere Xenon AlphaPixel.com PixelSense Landsat processing now available! http://www.alphapixel.com/demos/ "There is no Truth. There is only Perception. To Perceive is to Exist." - Xen _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
