The posterize effect is basically crushing the levels. Export it in 16bit png and it gives a good color/luminance latitude to fiddle with. But yeah Im usually do some simple post color correction, unsharp mask and grain in some cases.

Yeah Im kinda enjoying the speed bump octane provides. Still have a quite a bit to learn specially when seeing some of the great outputs people are getting around here in terms of render/light calculation quality. At the end of the day its a tool that should help you do whatever you want. So for me ...

Hi guys,

I've recently got octane to help me out on some motion graphics work. Been having great fun with it so far.

Slowly learning how to take advantage of it, so far as been a great to learn a fiddle with.

Here's some gif's and images i've been doing:

https://36.media.tumblr.com ...

Found the problem! Was in the search path of the image sequence. Was copying by default the first image to another directory.

Thanks for the help!

And sorry for the inconvenience.

Check out the other materials in scene. And the one it says with imagetexture. The preview slows speed as if its processing something but nothing show. refreshed it various times.

EDIT:

Got it working with a regular c4d material in the octane preview. But not as a octane material. I need it to ...

I tried it and still nothing. Also tried putting my animation on the imagetexture. Nothing happend.

Here's some visual details of that scene:

http://gyazo.com/212cd5fbae3cf3c484833b3c0cc52340

http://gyazo.com/9e8d53d5156154f89a3ba2bcdf67a89a

That's how it appear to me on the node editor. I ...

Hi guys. Hope someone can help me out. I'm doing this projector simulation onto a transparent net cloth and I wanted to project an animation on to it. I've went to the node edito r > imagetexture > shader > tried putting (jpeg) mov. file and a image sequence like it says in the user data > animation ...

The same is happening to me but on a licensed version. How can I fix this?

Same problem is happened to me. Changed DL kernel settings (rayepsilon and path term power) and it went back to render normally. I'm currently with a tight deadline so I had no time to search for the the issue. If it was actually kernel settings.