>> Might I suggest that a more general approach to this be implemented in >> osgconv? > > osgconv is a convenience tool that covers a few of the types of pre > processing that you might want to apply to database. It's not meant > to be an all encompassing tool for all types of pre processing on all > types of databases. If there is something specific you want to do > with processing your own databases then it may well be easiest to > just write a specific application to the do the exactly what you want.
I was just puzzled because the documentation to osgconv states (if the compressed switch is used) that the image data gets converted to a texture, then read back and saved. This would usually imply that also the the texture size is determined by OpenGL, which often is a power of 2 (depending on the capabilities of the hardware). It seemed unexpected that the saved textures still retained their original sizes, even though osgconv had printed to the console that they were resized (for upload to OpenGL). Fortunately hacking osgconv was rather easy, as my code snipped shows. So case closed. Christian _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
