octane doesnt understand RGB channel from texture ?

[masterzh]

Hi everyone, as title say i am looking for very simple way to extract RGB channels from texture. "Colorizer *input* " show in the small texture preview picture correctly however in preview its ignored ? Made a video explaining the problem: https://youtu.be/qCdmD6HLmdg

Cinema4D R19

Octane 3.07

Obviously looking for a way to display this in "octane" as it works nicely in cinema4D default renderers. So far i was using "clamping" and "RGB spectrum from black to Xcolor" done 3 times however results using this are very inaccurate and i assume very wrong.

Thanks ahead for any tips !

[aoktar]

Octane is using very limited amount of some C4D textures with partial support. You should go with native Octane nodes for accurate results. We have OSL nodes in 3.08 and it's perfect for what you are trying.

[dylan.mc]

Hey aoktar - I'm looking to achieve something very similar to masterzh, but within C4D.

The goal is to use the individual RGB channels of a texture to control the opacity of various shaders.

I've got 3.08 running, but I'm not well versed in OSL. Any chance you can point me in the direction of how to split out the RGB channels?

Cheers!

[bepeg4d]

Hi,
please, have a look at this other discussion with octane nodes or with OSL solution:
viewtopic.php?f=23&t=64061&p=326390&hil ... or#p326390
ciao Beppe

[dylan.mc]

Amazing. Thanks, bepeg4d. That OSL script works a treat.

On a side note, if you change the values in the square brackets to anything other than [0], [1] or [2] it causes C4D to crash. Not sure if that is expected behaviour with a bad script.

Cheers!

Dylan

[aoktar]

Amazing. Thanks, bepeg4d. That OSL script works a treat.

On a side note, if you change the values in the square brackets to anything other than [0], [1] or [2] it causes C4D to crash. Not sure if that is expected behaviour with a bad script.

Cheers!

Dylan

As i know that some core syntax errors could give crashes at level of osl-core. It should be avodiable by users.