Oh ok, I'm sorry. I guess this is not a bug but a shortcoming of the exporter.
Hi Arjo : No , the Importer too . I have done a couple of test imports with textured .OBJ's _from_ 3D Exporation (very old) and they also import without any means to "browse" for those textures . .OBJ's imported into 3D Exploration-demo (except for RS .OBJ's) come in showing that they have textured mappings , and the user just needs to browse and add it . I think it would be very easy to have the RS .OBJ importer build the VSL Texture so that all a user would have to do is browse for the file too . (see attached .GIF)
I think the Obj exporter should export .mtl files to make it possible to export material definitions.
I'd settle for an .OBJ exporter that just simply exported texture information . I'm still confused as to why Vesa would create a tute that shows him exporting texture info , when the texture info is not actually exported . This makes no sense at all . You say it's not a bug , but I'd say that it is most definitely not working properly . Call it incomplete coding if you want , but it is simply not right . http://www.nic.fi/~vesamesk/texture_export.htm cheers garry
<<attachment: import_1.gif>>
