Ive been wandering why imported .obj files from Daz3d don't transfer transparency and it appears that daz3d .mtl entries for these textures are referenced as map_D which octane doesnt recognise only map_d.
Any chance of that being tweaked?
Additionally in the import options is there anychance of a overide value for Bump power?
And a question what determines if something is imported as a diffuse or glossy material?
Import from DAZ3d
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Those requests have been noted so that they don't get lost. They are certainly doable, but take time and time is limited -> I can't say when they will be done. Sorry for being so unspecific, but we really have a lot on our platesIsotemod wrote:Ive been wandering why imported .obj files from Daz3d don't transfer transparency and it appears that daz3d .mtl entries for these textures are referenced as map_D which octane doesnt recognise only map_d.
Any chance of that being tweaked?

Well, let's have a look. The logic goes like this:Additionally in the import options is there anychance of a overide value for Bump power?
And a question what determines if something is imported as a diffuse or glossy material?
If the illumination model is 1 and the reflectivity (Ks / map_Ks) is 0 or the specular exponent (Ns) is less than 1, we choose diffuse.
Otherwise: If an optical density (Ni, i.e. an IOR) is given and > 1, we choose specular.
In all other cases: We choose glossy.
I hope that helps,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra