Hi Garry, > >> I think the Obj exporter should export .mtl files to make it > possible to > >> export material definitions. > > > Basically VSL is out of the scope, V3 materials are pretty close to > optimal. > > Some subset of VSL might be doable though, as in textures/constants > > [edit] > > Sorry , but you 2 nit-wits must be having hammer-fights for breakfast .
LOL > > First of all , the RS .OBJ Import/Exp module does not work . Simple . I've used the OBJ import/export many,many times. Both in Cinema 4D and Realsoft I have to redefine the "dummy" materials. I never found it a big deal to drop a new texture object in the material editor. For all the other possibilities to create materials I can't imagine how you could exchange them. Building materials is so very different in various applications. Each one has its own possibilities. So how would you want to exchange material features from a certain application to Realsoft when it doesn't support those features? > > If it did work , then we could easily export material definitions > via the 'UV-Image' Tool's ability to 'Evaluate' and create .bmp's. What's the problem? The bmp is created. So why don't you load the bmp in the material editor of your application you move the object to? > > This is what Vesa's Flash Video is trying to say ... how can > you guys not understand that ? (oh ya , the hammer fights) I did create trees, exported them the same way Vesa suggests and had no trouble at all to use those trees in Cinema 4D. Apart from the fact that the way Vesa suggests you get a very hi poly object. I did it in a slightly different way. I left out the twigs and individual leaves, but used larger polygons with some twigs and a bunch of leaves as a single texture. In that case the trees inside C4D contain much less polygons. Another handy tool is Polytrans to reduce the polygons even more. Arjo.
