OTOY Forums

I've just been browsing the threads that came up in search for "DAZ Studio".

I can see that people are bringing their DAZ figures into Octane, complete with their texture maps assigned and attached.
It begs the question; how the hell are you all doing it?

I'm exporting the figure from DAZ Studio in .obj format, I've tried various export options, but nothing I've tried has allowed me to import the figure into Octane, complete with textures. To make it easy, would someone be good enough to post two screenshots; one showing the export settings used in DAZ Studio, and the other showing the import settings used in Octane?

I feel like an absolute idiot for having to ask this, but it's just not working for me

There are export settings for daz 3d in the manual, page 53.
I don´t use daz but may it helps.

Cheers mib

I have the same problem with the last version (it worked with the previous ones, using the export setting from the manual) but the team is working on it and I'm sure they will come with a solution pretty soon.

Btw, happy to see another Daz Studio user

mib2berlin wrote:There are export settings for daz 3d in the manual, page 53.
I don´t use daz but may it helps.

Cheers mib

That's the thing, I was doing that but I just couldn't get it to work.
I started to wonder if I was making a mistake with the import options or something

teecee2107 wrote:I have the same problem with the last version (it worked with the previous ones, using the export setting from the manual) but the team is working on it and I'm sure they will come with a solution pretty soon.

Btw, happy to see another Daz Studio user

Well that's a relief to here, thanks for the heads-up!

I think DAZ Studio is an excellent partner product to Octane. I'm quite shocked though, that despite the totally immense size of the DAZ Studio userbase, the Refractive guys don't have anyone working on a plugin for DAZ Studio. I think a DAZ Studio plugin would sell more copies of Octane than a plugin for any other app' out there.

Everyone uses figures, many like content, and most of all the app' is a very intuitive animation studio.
I think Refractive would make an absolute killing if they had such a plugin for DAZ Studio.

But yup, same here, nice to see another DAZ Studio user

pumeco wrote:

mib2berlin wrote:There are export settings for daz 3d in the manual, page 53.
I don´t use daz but may it helps.

Cheers mib

That's the thing, I was doing that but I just couldn't get it to work.
I started to wonder if I was making a mistake with the import options or something

teecee2107 wrote:I have the same problem with the last version (it worked with the previous ones, using the export setting from the manual) but the team is working on it and I'm sure they will come with a solution pretty soon.

Btw, happy to see another Daz Studio user

Well that's a relief to here, thanks for the heads-up!

I think DAZ Studio is an excellent partner product to Octane. I'm quite shocked though, that despite the totally immense size of the DAZ Studio userbase, the Refractive guys don't have anyone working on a plugin for DAZ Studio. I think a DAZ Studio plugin would sell more copies of Octane than a plugin for any other app' out there.

Everyone uses figures, many like content, and most of all the app' is a very intuitive animation studio.
I think Refractive would make an absolute killing if they had such a plugin for DAZ Studio.

But yup, same here, nice to see another DAZ Studio user

Hi,

We have not been able to find anyone who can write the plugin...

Radiance

@ pumeco : It seems that there is a problem with the path in the .mtl file.

After export from Daz Studio, the path in the .mtl file should look similar this.

map_Kd /Maps/2_V4Tanith.jpg
map_Bump /Maps/2_V4TanithB.jpg

Marcus found this solution : try to remove the leading / in all the path, it should work (it works perfectly for me ...).

I found another workaround : I changed the actual path in the mtl file with the complete location of the texture file (something like map_Kd C:\3D\tests\TestTextures\Maps\2_V4Tanith.jpg). This also works for me.

Hope this helps

Hi, I'll jump in here boots an' all.
I've been using DAZ3.1.2.32 advanced to do all of my obj exports as it was working really well. (I tried to use Carrara 8 pro but there were issues with the way multi diffuse shaders were being handled.. in the mtl file, so went back to DS3A)
I have heaps of obj and mtl files for a lot of my Daz runtime stuff and normally it has been working fine, that is importing into Octane and rendering with tex mapped materials correctly (as best as they are...)
If I use Octane pre 2.43 it works fine, that is, it loads the obj and mlt with all material names and texture maps assigned correctly.
If I use Octane 1.022b x84 it also works fine. (as above)
If I use Octane 1.024 cuda32 it does not.... that is, it loads all the material names but they are rgb shaders, NOT the diffuse texture maps previously referenced.
Now the mtl file HAS NOT changed, go figure!
Obviously something in Octane has changed and it does not read the previous ok obj/mtl file the same.

ps. this is all on Win7 Home prem 64 bit sys.

I will also add modo 501 and Vue 9 read the same obj/mtl's fine and import correctly.
Basically, I've gone back to using Octane pre 2.43 for all my octane renders.
Bit of a bummer, but if you are using the latest Octane 1.0.244, try going back a version, see if that works for you.

Ok, I had a look at the DAZ problem and I changed the way texture file names are resolved. It's now similar flexible as in beta 2.43, but still correct. It got changed in 2.44 while making many areas more Unicode-proof. -> The next release will load your DAZ OBJ files as previous releases.

Cheers,
Marcus

Thank you, Marcus.

Damn, why couldn't I have visited this thread earlier today. I just bought Reality for DAZ Studio, thought I'd give it a try because I got annoyed with Octane screwing-up the texture imports. I usually get notifications but they seem to haver stopped since my last reply so I had no idea there were more replies here!

Anyway ...


@Radiance
Not to point out the obvious, but with a userbase as large as DAZ's, should you really be waiting for someone else to do it? I actually meant for you guys to do it because you know better than anyone how best to interface with Octane. DAZ Studio has readily available development kits and information, all free, just like the app' itself, so I think you're doing yourself a disservice by not allocating time to it.

Even if it means you employ someone especially for it, I reckon the return on investment would make it worthwhile. I can't imagine a single DAZ Studio user turning their noses up to being able to render at Octane's break-neck speeds, so providing the importer actually works as it should and supports animation, I think you'd get a serious amount of the userbase jumping on the Octane bandwagon.

You've no doubt seen those newsletters DAZ email out regarding stuff on the DAZ store, well that could be Octane.

Here's a sure-fire way to gaining masses of extra Octane users:

1 - Finish-up the beta.
2 - Have a DAZ Studio exporter made available.
3 - Do a limited run of selling Octane on DAZ complete with the exporter.
4 - Promote Octane on the DAZ forum showing videos of DAZ Studio scenes getting rendered in seconds instead of days.

Watch every CUDA-capable DAZ user buy a copy.

And just in case you think DAZ is not the place for selling some Octane, have you asked yourself ... why not? Even Pixologic finally caved-in to temptation and have started doing the occasional DAZ promotion with ZBrush. The reason they did of course is because just like Octane, ZBrush is an awesome tool for their content

Anyway, I know you guys are busy, but please consider it as an "in-house" thing when you have Octane closer to release, because seriously, to not cater for DAZ Studio is to rid yourselves of the largest 3D userbase out there. If I were you, it'd be the biggest priority of any exporter - no kidding.


@teecee2107
Thanks for that, I really appreciate it, I'll give that a go until the next Octane release arrives


@teknofreek
That's a real bummer, I hope you got it sorted!


@Marcus
Thanks for the fix, it's a major relief to hear that, cheers!
So do you have any idea when we can expect the next release?