Hi Jan, > -----Original Message----- > From: Jan Ciger > Sent: Saturday, August 19, 2006 1:37 PM > > > That... makes no sense at all. The material already has > > the texture loaded. Blender renders it fine, and all the > > other exporters will export it textured. Only the > > 'osgexport' seems to want it to be loaded in the > > UV view too. > > Actually, it does make sense. The material editor in Blender > is used only by the raytracer.
It's not just the raytracer, the texture is also correctly used by all the other exporters (as it should, it is how the model and material is defined.) 'osgexport' is the only one that has the bug to fail to output the texture in this case. > It is not really an exporter problem. You need to explicitly > define the UV mapping using the UV editor for this to work, > the exporter does not know how to deal with the textures > without UV coordinates defined. I do wish you were right :) I am of course defining explicit UVs. See http://vterrain.org/Implementation/ArtPath/blender-osg.html for the whole story. My simple test model has two objects. Object 1 has a texture. Object 2 does not. If the texture is not shown in the UV editor, then neither object is exported textured. If the texture _is_ shown, then _both_ objects are exported textured. That a giant bug. > Be careful not to map two (or more) textures to the same mesh. I am definitely not doing that. In fact, osgexport's minimal documentation states it does nothing with materials mapped to meshes. It only respected materials maps to objects. > I am able to use the OSG exporter with Blender without major hassle. I am very curious, can you get the simple texture test model i created, to export correctly? Thanks, Ben _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
