OTOY Forums

steveps3 wrote:Lionel, are you still around (he shouts into the air). I know that the official blender integration is coming but for now it really would be good if the exporter could be patched.

Sorry Steve, I've been too busy during the last 12 months and my new responsibilities don't let me enough free time for contributing to the plugin... I was expecting to be able to put my hands on the SDK during the holidays season but once again it turned out I've too busy with my job.

I agree the plugin needs severe overhaul, which I've been delaying long time waiting for new file format to come, but it's now too late for me to catch up and I hope the integrated plugin will meet the needs of the community. I'll be happy to contribute again but it's not my priority at the moment considering the tiny amount of free time I have.

On a side note, I might also no be able to use Octane in the near future as I'll probably stop using NVidia products in retaliation to changes made in their drivers that have affected my ability to do my job, despite the community already warned them about the nasty side effects (I had non-graphical but comparable annoyance due to changes in the linux kernel but this is open source and I could reverse myself the changes to make it workable again).

Lionel

Hi Lionel,

I clearly understand your lack of time, that's a sad news for us, but i'm glad to hear that u've got a big time interesting job... anyway ... i can't thank u enough for the amazing job yu've done so far...
i really hope someone else will have the time and knowledge, to update your work. or hoping that the integrated plugin will come out soon ..

Ok Blender 2.66 is now out and as suspected the problem with materials her returned. I guess the blender code is no longer compatible with the exporter code. Do we have any budding Python programmers who could take a look?

Regarding the material panel problem with Blender 2.66,
I think this should work, at least it works for me.

Forget my previous post, duno what I found there but it doesn't seem to be the solution, so here is another attempt :

Just edit the ui_material.py file in octanerender folder and around line 78 replace :

row.template_list(ob, "material_slots", ob, "active_material_index", rows=2)

by

row.template_list("MATERIAL_UL_matslots", "", ob, "material_slots", ob, "active_material_index", rows=2)

Hope this helps

I noticed this error with 2.66 as well. I just set a material in blender internal or cycles first and switch to the octane render setting. - My lazy way without coding.

Well, it seems that my previous solution wasn't the good one :/
I changed my previous post, look a bit higher ...

I love it when a plan comes together.

Works like a charm.

THANKS

Has 2.67 killed this again

steveps3 wrote:Has 2.67 killed this again

Nope... v.1.20 works for me... right now. Blender r56535. But I'm not using instances currently.

Odd, I have no material selector again. The same as I got when 2.66 came out.