Re: .OBJ IMPORT/EXPORT - Buggy ?
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 . First of all , the RS .OBJ Import/Exp module does not work . Simple . If it did work , then we could easily export material definitions via the 'UV-Image' Tool's ability to 'Evaluate' and create .bmp's. This is what Vesa's Flash Video is trying to say ... how can you guys not understand that ? (oh ya , the hammer fights) Just back-tracked to some old Icarus (freeware) experiments with .OBJ export , and those objects import perfectly into 3D-Exploration . So , it's not broken in RS ... it just doesn't work . Kill Me ! studio
RE: .OBJ IMPORT/EXPORT - Buggy ?
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.
Re: .OBJ IMPORT/EXPORT - Buggy ?
Arjo : I have to redefine the dummy materials. I never found it a big deal to drop a new texture object in the material editor. The purpose of this thread was to determine if the .OBJ module was possibly not working at 100% . I think we both agree it isn't , so maybe it could be mentioned on the beta-list . The code appears to be there - not executing . I think the Obj exporter should export .mtl files to make it possible to export material definitions. As far as the interchanging of material definitions between programs go , Timo already answered your question and also provided links to exactly how that is being accomplished in other S/W's through the .MTL format (COL/SPEC/TRANS/BUMP via .TGA/BMP is also an option) . garry 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? Arjo
RE: .OBJ IMPORT/EXPORT - Buggy ?
Hi Garry, The Obj. Exporter is not broken. But you must set UV coords to per face uv cords. I don't understand why this is not the default setting though Arjo. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:owner- [EMAIL PROTECTED] Namens studio Verzonden: maandag 7 april 2008 7:54 Aan: user-list@light.realsoft3d.com Onderwerp: .OBJ IMPORT/EXPORT - Buggy ? Bernie : Is the .OBJ Import/Export broken for SDS Objects with Per Face textures ? (for instance , created by UV-Image) I tried the same settings Vesa uses in his tree-export Flash tutorial , but with a simple object it will import geometry , but no texture file included . (see .GIF) http://www.nic.fi/~vesamesk/texture_export.htm Here's the original simple SDS Sphere (50KB link below) , http://www.studiodynamics.net/uv/UV_image_tut_proj.zip Attached are the Exported .OBJ object/texture after the SDS object has been Face-Mapped via UV-Image . Not even a shred of info in the Manual about how-to import/export _Anything . No info about the .OBJ loader . Seems odd to me that Vesa would create a tutorial about exporting SDS Face-Mapped trees , when the .OBJ Loader or Exporter is broken . Maybe I'm doing something wrong ? Also , the imported .OBJ will not show up in the UV Editor . Thanks In Advance studio
Re: .OBJ IMPORT/EXPORT - Buggy ?
Hi Garry, The Obj. Exporter is not broken. But you must set UV coords to per face uv cords. I don't understand why this is not the default setting though Arjo. Hi Arjo : I did ! I followed the example in this (very nice!) Flash Video . http://www.nic.fi/~vesamesk/texture_export.htm Just look at the .gif attached to previous mail and you will see how RS does not have the proper VSL shader coding . I circled the missing part in red . Maybe the .OBJ Importer is the culprit ? The Exporter does create a folder 'root/textures' , but the texture residing in that folder does not get applied via VSL when imported . Import the .OBJ I attached and you will see what I mean . Seriously , something is broken there , I think . Perhaps Vesa used the much-sought-after V6 Demo for his tutorial ? garry Bernie : Is the .OBJ Import/Export broken for SDS Objects with Per Face textures ? (for instance , created by UV-Image) I tried the same settings Vesa uses in his tree-export Flash tutorial , but with a simple object it will import geometry , but no texture file included . (see .GIF) http://www.nic.fi/~vesamesk/texture_export.htm Here's the original simple SDS Sphere (50KB link below) , http://www.studiodynamics.net/uv/UV_image_tut_proj.zip Attached are the Exported .OBJ object/texture after the SDS object has been Face-Mapped via UV-Image . Not even a shred of info in the Manual about how-to import/export _Anything . No info about the .OBJ loader . Seems odd to me that Vesa would create a tutorial about exporting SDS Face-Mapped trees , when the .OBJ Loader or Exporter is broken . Maybe I'm doing something wrong ? Also , the imported .OBJ will not show up in the UV Editor . Thanks In Advance studio
RE: .OBJ IMPORT/EXPORT - Buggy ?
Oh ok, I'm sorry. I guess this is not a bug but a shortcoming of the exporter. I think the Obj exporter should export .mtl files to make it possible to export material definitions. Yesterday I saw the same complaint on another forum. Photoshop CS3 needs the mtl files to be able to show textured objects. I've no idea what's supported by mtl files, or if it's possible to create them with VSL code as a source. Arjo. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:owner- [EMAIL PROTECTED] Namens studio Verzonden: maandag 7 april 2008 9:28 Aan: user-list@light.realsoft3d.com Onderwerp: Re: .OBJ IMPORT/EXPORT - Buggy ? Hi Garry, The Obj. Exporter is not broken. But you must set UV coords to per face uv cords. I don't understand why this is not the default setting though Arjo. Hi Arjo : I did ! I followed the example in this (very nice!) Flash Video . http://www.nic.fi/~vesamesk/texture_export.htm Just look at the .gif attached to previous mail and you will see how RS does not have the proper VSL shader coding . I circled the missing part in red . Maybe the .OBJ Importer is the culprit ? The Exporter does create a folder 'root/textures' , but the texture residing in that folder does not get applied via VSL when imported . Import the .OBJ I attached and you will see what I mean . Seriously , something is broken there , I think . Perhaps Vesa used the much-sought-after V6 Demo for his tutorial ? garry Bernie : Is the .OBJ Import/Export broken for SDS Objects with Per Face textures ? (for instance , created by UV-Image) I tried the same settings Vesa uses in his tree-export Flash tutorial , but with a simple object it will import geometry , but no texture file included . (see .GIF) http://www.nic.fi/~vesamesk/texture_export.htm Here's the original simple SDS Sphere (50KB link below) , http://www.studiodynamics.net/uv/UV_image_tut_proj.zip Attached are the Exported .OBJ object/texture after the SDS object has been Face-Mapped via UV-Image . Not even a shred of info in the Manual about how-to import/export _Anything . No info about the .OBJ loader . Seems odd to me that Vesa would create a tutorial about exporting SDS Face-Mapped trees , when the .OBJ Loader or Exporter is broken . Maybe I'm doing something wrong ? Also , the imported .OBJ will not show up in the UV Editor . Thanks In Advance studio
Re: .OBJ IMPORT/EXPORT - Buggy ?
See http://people.scs.fsu.edu/~burkardt/data/mtl/mtl.html and http://local.wasp.uwa.edu.au/~pbourke/dataformats/mtl/ 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 mapped to color, illumination, specular sharpness/brightness, transparency, bump and optical thickness. Reflection maps are supported as well, but there's no set way to do them in RS. MTL does have some support for procedural textures as well, but I doubt if it'd be of any use to implement them. On 07/04/2008, Arjo Rozendaal [EMAIL PROTECTED] wrote: Oh ok, I'm sorry. I guess this is not a bug but a shortcoming of the exporter. I think the Obj exporter should export .mtl files to make it possible to export material definitions. Yesterday I saw the same complaint on another forum. Photoshop CS3 needs the mtl files to be able to show textured objects. I've no idea what's supported by mtl files, or if it's possible to create them with VSL code as a source. Arjo. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:owner- [EMAIL PROTECTED] Namens studio Verzonden: maandag 7 april 2008 9:28 Aan: user-list@light.realsoft3d.com Onderwerp: Re: .OBJ IMPORT/EXPORT - Buggy ? Hi Garry, The Obj. Exporter is not broken. But you must set UV coords to per face uv cords. I don't understand why this is not the default setting though Arjo. Hi Arjo : I did ! I followed the example in this (very nice!) Flash Video . http://www.nic.fi/~vesamesk/texture_export.htm Just look at the .gif attached to previous mail and you will see how RS does not have the proper VSL shader coding . I circled the missing part in red . Maybe the .OBJ Importer is the culprit ? The Exporter does create a folder 'root/textures' , but the texture residing in that folder does not get applied via VSL when imported . Import the .OBJ I attached and you will see what I mean . Seriously , something is broken there , I think . Perhaps Vesa used the much-sought-after V6 Demo for his tutorial ? garry Bernie : Is the .OBJ Import/Export broken for SDS Objects with Per Face textures ? (for instance , created by UV-Image) I tried the same settings Vesa uses in his tree-export Flash tutorial , but with a simple object it will import geometry , but no texture file included . (see .GIF) http://www.nic.fi/~vesamesk/texture_export.htm Here's the original simple SDS Sphere (50KB link below) , http://www.studiodynamics.net/uv/UV_image_tut_proj.zip Attached are the Exported .OBJ object/texture after the SDS object has been Face-Mapped via UV-Image . Not even a shred of info in the Manual about how-to import/export _Anything . No info about the .OBJ loader . Seems odd to me that Vesa would create a tutorial about exporting SDS Face-Mapped trees , when the .OBJ Loader or Exporter is broken . Maybe I'm doing something wrong ? Also , the imported .OBJ will not show up in the UV Editor . Thanks In Advance studio
Re: .OBJ IMPORT/EXPORT - Buggy ?
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
