Renderman or Collada support yet?

[radiance]

btw, with the way things are going with our SDK, i don't think DAZ users have to worry too much about the future...

Radiance

[Nemo]

That's good to hear. Part of my problems were figuring out the right export settings in both Daz and Octane, though I think I have it figured out now. However, there are a few things I think the Daz obj exporter is responsible for that I find a little annoying. For example, transmaps aren't collected, and so I have to go assign those myself.

That said, the most reliable version of Octane for me is still 1.024 beta2.46b. I believe I have the right cuda drivers, but later versions like 1.025 beta2.52 don't always active the render when I select my mesh.

[teecee2107]

For example, transmaps aren't collected, and so I have to go assign those myself.

With the last version (2.52) the transparency maps are automatically transferred and correctly assigned.

That said, the most reliable version of Octane for me is still 1.024 beta2.46b. I believe I have the right cuda drivers, but later versions like 1.025 beta2.52 don't always active the render when I select my mesh.

Just an advice, maybe you should check that it's not a memory size problem, because you don't seem to have a lot of Vram and Daz scene can be ressource consuming (especially texture wise).
Being a daz/octane use myself, I encountered problems until I switched to Windows 7 x64 and added a decent amount of ram.

[Nemo]

For example, transmaps aren't collected, and so I have to go assign those myself.

With the last version (2.52) the transparency maps are automatically transferred and correctly assigned.

Yes, Octane does ask for them now, but I was referring to the Daz OBJ exporter which isn't collecting them into the folder with the other images. However, Octane does seem to assume that its going to be a TIF, even when the file with the right name is there as a jpg.

That said, the most reliable version of Octane for me is still 1.024 beta2.46b. I believe I have the right cuda drivers, but later versions like 1.025 beta2.52 don't always active the render when I select my mesh.

Just an advice, maybe you should check that it's not a memory size problem, because you don't seem to have a lot of Vram and Daz scene can be ressource consuming (especially texture wise).
Being a daz/octane use myself, I encountered problems until I switched to Windows 7 x64 and added a decent amount of ram.

Puzzling, I just tested all of my previous problem scenes to see if this was the case, and they all worked, except for the more ram intensive ones. Must have been a settings thing, but I would have liked to know why some of those smaller scenes failed the first time.

[teecee2107]

Yes, Octane does ask for them now, but I was referring to the Daz OBJ exporter which isn't collecting them into the folder with the other images. However, Octane does seem to assume that its going to be a TIF, even when the file with the right name is there as a jpg.

That's very strange. When I export my scene as an obj file, the jpg transparency maps are collected on the 'Maps' folder along with the other images ... and they work in octane on jpg format. Are you using the export parameters as shown on the manual ?

[Nemo]

Thanks for pointing that out to me, I remember those being posted somewhere but hadn't found it again. Will have to do some more tests, but I'm still re-exporting more often than I would like trying to get things to work. While my limited ram and the 40 texture limit in Cuda don't help me much, my biggest frustration is still the Daz OBJ exporter because it includes materials of hidden geometry in the list when I bring it into Octane. Whether or not this trips the 40 limit, I'm not sure, but not that many unique textures are being used, though many material zones refer to them.

*Edit*
I've been experimenting with processing the OBJs from Daz through MeshLab before bringing them into Octane. While it does eliminate most unused material zones (due to hidden geometry not exported), it has the unfortunate side effect of renaming all of them. Also, the transparency settings got lost during the conversion.

The OBJ exports from Daz Studio appear to include all material zones, regardless of whether or not they apply to hidden geometry. The original export of the OBJ in the picture had 43 material zones, which Octane choked on. After Meshlab cleaned up the MTL to just 14 material zones, however, Octane handled it just fine. This would seem to indicate that if the MTL asks for a texture, Octane will load it whether or not there is any geometry for it? At any rate, I've started a thread over at Daz's Forums to figure out whats up with their OBJ exporter and how it handles MTL creation.

[Tugpsx]

Here is the one click OctaneExporter script. Put it in your scripts folder and add a quicklink on the tool bar. That way you can export any scene.
The updated script will launch Octane after the export with the created file.

Export parameters are already set in this script so it will only prompt for file location to export to.

ObjExport.rar

[Nemo]

Thanks, Tugpsx, looking forward to using this script.

I've been reading about a Camera Transform material in the Octane manual, have you had much luck getting that to work with something from Daz Studio? I've tried a few times, though my test scenes of late had other problems with them such as having too many material zones.

[Kevin Sanderson]

Thank you,Tugpsx!

[Tugpsx]

Lots of improvement. Still beta testing. Coming soon

Daz 2 Octane

Dazoctane.jpg (24.48 KiB) Viewed 4137 times