Version 1.52.1 (Octane Render 1.52) *** 10.04.2014 ***

[momade]

hi aoktar…
i just add something i noticed here :

if you use the octane imagetexture nodes for textures, they are missing in the texture manager !
thats a bit sad because the (great!) functionality of the texture manager is broken…
does it make a difference for octane if you use the internal texture node?

cheers!

I agree on that. It would be great if these textures would show up in the texture manager.
And I'm also curious about the answer on the octane vs. internal texture node difference.

br.
mo

[momade]

Hi,
I'm planning a new release for SDK 1.53 soon, maybe tomorrow. Just a info before that. If anyone to see some progress about features of coming 2.0, let me know

Cheers,
Ahmet

1.53 ... 2.0 what ever you have, let us take a peek!!!!
cant wait for all these new features!!!

br.
mo

[aoktar]

hi aoktar…
i just add something i noticed here :

if you use the octane imagetexture nodes for textures, they are missing in the texture manager !
thats a bit sad because the (great!) functionality of the texture manager is broken…
does it make a difference for octane if you use the internal texture node?

cheers!

I agree on that. It would be great if these textures would show up in the texture manager.

br.
mo

if i remember correctly, i have asked for that to Maxon. It's not supporting custom types except xbitmaps.

And I'm also curious about the answer on the octane vs. internal texture node difference.

Do you mean bitmaps vs. imageTexture?
in the end, both is accounting as octane images. But imagetexture has all parameters of octane images. Like, power, gamma, invert, modes, uv and transform inputs. This is only way to use this options

[momade]

thanks for the info. i got it now.

[miroof]

hello i do have some issue with octane, i do have a render faillure when i am using render queue but no error with the octane live viewer

i send to u file with report, if u can take a look, it can pretty cool