OTOY Forums

face_off wrote:

those who are playing with instancing with Geometry and CVS,
I managed to make it work, except the external .obj comes
without materials. There finds a .mtl file in the same folder,
and there was X in the "export material definitions" box.
How must I do the exporting .obj from rhino to make sure the
materials do follow?

Just to confirm - the MTL file must be in the same folder as the OBJ file in order for Octane to be able to pick up the material definitions.

Paul

Hi Paul,

I got it to work, i went to my old machine (W7) and made the .obj there,
exactly the same way I did with my new machine (W8), and it worked with
my W8 machine where I have my Octane/Rhino plugin installed. This is no
problem since my machines are on the same table and networked, but makes me
wonder what might be the problem with new machine? W8? Some security software
behaviour (Comodo)? Any thoughts?

Thanks!

-V-

I got it to work, i went to my old machine (W7) and made the .obj there,
exactly the same way I did with my new machine (W8), and it worked with
my W8 machine where I have my Octane/Rhino plugin installed. This is no
problem since my machines are on the same table and networked, but makes me
wonder what might be the problem with new machine? W8? Some security software
behaviour (Comodo)? Any thoughts?

You could try running W8 Rhino in W7 compatibility mode. Is the MTL file being created on W8, or is it missing?

Paul

I tried using compability mode,
no chance in behaviour.

MTL file is created, is in the same folder,
as are textures.


-V-

MTL file is created, is in the same folder,
as are textures.

Not sure I'm fully understanding your issue. Is it a problem with the plugin, or with the Rhino obj exporter?

EDIT: What happens if you import an erroneous OBJ into Octane Standalone - do the materials get picked up then?

EDIT2: Are you able to post one of the MTL files? Might give some clues.

Paul

Well,

it is a problem that surfaced with plugin (geometry instancing),
but now I am sure it is not related to plugin.

For some reason, rhino writes inferior .obj in my W8 machine,
and that manifests by materials not appearing after import (neither of my machines).
If I do the same in my w7 machine (same rhino version, same settings as far as I can tell),
exported .obj works fine in both, my W7 and in my W8 machine.

So it is not your/plugin problem, and not a big problem for me since
I have workaround, so I think I must stop bothering you right now with it.

Thank you and keep up the good work!


-V-

Yes,

it occurs the same in the Stand alone,
and yes, I can send .MTL by mail,
where do I send it?


-V-

Ok,

somehow it seems that rhino fails to write textures in the material
definition when exporting .obj in my W8 machine:

# Rhino
newmtl New material 001
Ka 0.0000 0.0000 0.0000
Kd 1.0000 1.0000 1.0000
Ks 1.0000 1.0000 1.0000
Tf 0.0000 0.0000 0.0000
d 1.0000
Ns 0

newmtl New material 002
Ka 0.0000 0.0000 0.0000
Kd 1.0000 1.0000 1.0000
Ks 1.0000 1.0000 1.0000
Tf 0.0000 0.0000 0.0000
d 1.0000
Ns 0

This is from W7 machine and works perfectly:


# Rhino
newmtl mantyrunko1
Ka 0.0000 0.0000 0.0000
Kd 1.0000 1.0000 1.0000
Ks 1.0000 1.0000 1.0000
Tf 0.0000 0.0000 0.0000
d 1.0000
Ns 0
map_Kd CG18Y3~L.JPG
map_Bump CLBQ4D~K.JPG

newmtl neulaset1
Ka 0.0000 0.0000 0.0000
Kd 1.0000 1.0000 1.0000
Ks 1.0000 1.0000 1.0000
Tf 0.0000 0.0000 0.0000
d 1.0000
Ns 0
map_Kd CG18Y3~M.JPG
map_D CO4A1G~0.JPG



-V-

Found the problem,

something in the Comodo security system is messing the
.mtl export, it works fine when it is disabled.
I would guess it is the "sandbox" feature,
I will try to narrow it down later when I have time.


-V-

Good to hear you are getting a handle on the problem. I recently upgraded to W8, so I feel your pain.

Paul

Paul,

Regarding materials in the rhino plugin:
1. Will we be able to tweak materials once they are imported from the mtl file?
2. Do you intend on letting us assign materials for referenced obj's like in standalone?
3. Will we be able to import material macros from standalone?