OTOY Forums

excellent. I will have to find something really large to render.

Please all be aware I've posted v0.93 as a replacement of 0.92. I noticed textures didn't get exported (I forgot to reverse a change while testing something).
Sorry for the inconvenience.

I seem to be having a silly problem.

I am trying to decal a model in Blender 2.56a using 0.90 for export to Octane. When I select the octane render plug-in as the rendering engine 75% of the options in the Blender texture panel disappear and I am unable to change from a repeating texture to a "clip" texture. Am I missing something?

You're not missing anything. At the moment Octane only supports 'repeat' textures, this is why I do not allow changing the type to 'clip' in the panel, with many other things not supported either. It would have no effect in Octane and would just confuse you a bit more...

yoyoz wrote:Please all be aware I've posted v0.93 as a replacement of 0.92. I noticed textures didn't get exported (I forgot to reverse a change while testing something).
Sorry for the inconvenience.

I thought that I must be doing something wrong earlier because I had this problem. Good to see that I wasn't going mad. 0.93 here I come.

Thanks for the quick reply Lionel.

Lionel I see you have posted to the Bf-commiters mailing list.
As a general comment - and I am not a coder but observer - I wish we could reach some stability in Python things soon. It seems like @ideasman is always changing or renaming things...sometimes seemingly on a whim or without much consultation to effects...
This makes it pretty hard for people to write or port and maintain scripts without having them get continually broken.
I wonder if there shouldnt be an accumulated API update only say on the 1st of every month, and these could be documented briefly somewhere for easy reference rather than have an endless trail of bits and pieces that need to be monitored or chased down? maybe it cant work like this? just mentioning it though...

Yep, it would be easier to maintain scripts and other stuff if there were less frequent commits, but I would even prefer that BF releases new beta every month for instance. This way we could focus on this one for users and the gap with svn wouldn't be too big. Regarding the actual trend it'll soon be hard to maintain a script that can work with the two versions...

Hi guyz,

Seems octane ignores blender's material setting upon export, co'z most of materials when exported are glossy in octane even if it was assigned as diffuse in blender.

Thankz..chow!!

As per recent info from Marcus, materials are now imported only first time they're seen by Octane. It means that once you've exported your scene, any subsequent change on already existing materials (same name) will not been taken in account, even if the mtl file is properly updated (which is the case). This is different behaviour from 23.5.

I would have prefered that nodes in the internal graph are considered managed by the mtl file while explicit graph nodes would stay untouched and only managed by Octane, but Refractive has made a different choice. We may have an option to (re)match this behaviour in the future but as Marcus said it won't happen immediately.

Cheers,
Yoyoz