OTOY Forums

Apophis wrote:Hello,
how can I export Material too.
"Add Export Material" is activated but I get only the mesh in octane with an other name "undefined" as the exported and without the material.

Regards
Michael

Same here, I only get mesh without materials
Regards

Luca

Thanks Tugspx. Following the directions you gave me for all my questions, but I think it might have something to do with the OCS file. Should this be created by your plugin? I tried BLANK.OCS and it gives the following error.

There was an error parsing the command-line arguments:

Couldn't read argument value from string 'NaN' Argument: (--cam-fov)

I've just tried with "updated" version. Now the .obj is correct, but still no textures exported.

rcallicotte wrote:Thanks Tugspx. Following the directions you gave me for all my questions, but I think it might have something to do with the OCS file. Should this be created by your plugin? I tried BLANK.OCS and it gives the following error.

There was an error parsing the command-line arguments:

Couldn't read argument value from string 'NaN' Argument: (--cam-fov)

Blank.ocs is created by user. It is a donor ocs file. You can use another ocs file also but that would take up more video memory.
The demo version has some parts disabled you will have to set the FOV option on the camera tab since it is no longer automated.

Jadawyn2011 wrote:I've just tried with "updated" version. Now the .obj is correct, but still no textures exported.

Material export button is disabled in demo version. Previous version had all materials mapped to a single image and I was called a few names for that, so we decided to not map any material and allow the user to do so themself.

The full version does map the materials and include bump and normal maps.

Tugpsx wrote:

Jadawyn2011 wrote:I've just tried with "updated" version. Now the .obj is correct, but still no textures exported.

Material export button is disabled in demo version. Previous version had all materials mapped to a single image and I was called a few names for that, so we decided to not map any material and allow the user to do so themself.

The full version does map the materials and include bump and normal maps.

Well, I was interested in this plugin mostly to ease material export; geometries, lights and cameras are the least of my problems. So, if I can't test this function, I really don't know if I'll buy the final version

I'm sorry to tell you my experience with is that this just isn't working. The file sent to Octane is not the correct file and does not include the necessary maps, etc. I've tried both DS3 and DS4. If you think it does work, would you give us step-by-step instructions from something simple in the DS like a chair or a simple prop, so we can follow along? I'm not sure it's working and have no other way to see it render.

I tried further to see if I could understand what is happening. This is one thing I've discovered - if I have multiple objects (four, in this case), then the first object is asked by Octane about saving it and that object is put in whatever texture I choose (each object requests which material) and then this object's texture material covers over all of the other objects' texture materials. This means no objects underneath this highest branch [the object that is the only one asked about on Export] can display their textures, even though these objects have distinctly different textures than this highest object in the Octane tree. It's like in Photoshop - the top object is coloring everything under it.

rcallicotte wrote:I tried further to see if I could understand what is happening. This is one thing I've discovered - if I have multiple objects (four, in this case), then the first object is asked by Octane about saving it and that object is put in whatever texture I choose (each object requests which material) and then this object's texture material covers over all of the other objects' texture materials. This means no objects underneath this highest branch [the object that is the only one asked about on Export] can display their textures, even though these objects have distinctly different textures than this highest object in the Octane tree. It's like in Photoshop - the top object is coloring everything under it.

You have the older version without material zone support, please download the newer version from first page.
The Demo version creates the material zones but do not export materials, does not have control of daz light setting, proper IBL support.
It is ment to simply show users how to transfer the scene to Octane for rendering as a sample. Materials, Cameras and Lights are fully supported in the full version (coming soon).

Thanks for taking the time and thanks for the explanation. This does help. I found if I setup my lighting and ALPHA in the BLANK.ocs file, it helps. Here's an example, after I replaced all of the textures with the original DAZ textures. I also used a GLASS texture from Octane.

Tugpsx wrote:

rcallicotte wrote:I tried further to see if I could understand what is happening. This is one thing I've discovered - if I have multiple objects (four, in this case), then the first object is asked by Octane about saving it and that object is put in whatever texture I choose (each object requests which material) and then this object's texture material covers over all of the other objects' texture materials. This means no objects underneath this highest branch [the object that is the only one asked about on Export] can display their textures, even though these objects have distinctly different textures than this highest object in the Octane tree. It's like in Photoshop - the top object is coloring everything under it.

You have the older version without material zone support, please download the newer version from first page.
The Demo version creates the material zones but do not export materials, does not have control of daz light setting, proper IBL support.
It is ment to simply show users how to transfer the scene to Octane for rendering as a sample. Materials, Cameras and Lights are fully supported in the full version (coming soon).