OTOY Forums

It might be textures are nested in a non standard material OR the gw obj export dialouge is configured so it doesnt export the material file and or the textures.

I think it might have to do with the spaces in the file names or filepaths of the textures, I've just tested this with a scene exported with kilad's and imported the mesh in octane 1.22 RC3, the textures with no spaces were imported right, the ones with spaces were left out at import. Later if you add them manually there is no problem whatsoever, it's just at import time.

oh yeah thats needed. I think we wrote that down somewhere if im not mistaken, else it is in the video tutorial I made for the tool.

However if you think its unclear, Ill redo the tutorial that sits in the post with the scripts.

Infact ive picked up a few posts that have had this issue with space in names. I will redo the main video tutorial and implement the bits I just took for granted people knew/know.

-mads

well, I don't think it has anything to do with either your exporter or your tutorial (I mean they are both solid and clear), it seems more a limitation with the mlt files or octane at import, not sure, especially cause if you add the material inside octane it doesn't matter if it has spaces in name or path

ah so, c:\textures\my texture is nice.jpg breaks you say.
well this could be, i understand now. Will check up on this myself when I get home.
If thats the case, it might be like you say, a thing that needs to be fixed in octane.

Ill get back on this when its verified. but sounds weird that you can manually do it when i octane..ill look it up and reply later today.

mads