OTOY Forums

bloodyriton wrote:

aoktar wrote:

bloodyriton wrote:
Hummm very strange, I used exactly the same scene, and also rebuild one, cuda is up to date...
But still the same

Any clues ?

This is my result and scene.

Ok, but I add a camera with an aperture of 5.

Look with the 2.21.1 it works, but not with the 2.23.2 r5

with aperture 2.21.1.PNG

with aperture 2.23.2 r5.PNG

Right but i didn't posted for this DOF issue. It was for illumination problem on shadows. Btw i hope that you don't think that it's a plugin issue.

Sorry... But I think it is

bloodyriton wrote:Sorry... But I think it is

So wrong idea. We can't change that how renderer calculates the images.

Dammit !

bloodyriton wrote:Dammit !

i'll talk to Marcus about this issue.

Thanks Aoktar !

I always get an outline when alpha is enabled. Don't know if this a problem or i do something wrong. But in the old version 2.22.2 i got a clean picture without any outlines.
In 2.32.2R5 i can't get a clean picture without the outline. Did i miss something?

Pixelkingdom wrote:I always get an outline when alpha is enabled. Don't know if this a problem or i do something wrong. But in the old version 2.22.2 i got a clean picture without any outlines.
In 2.32.2R5 i can't get a clean picture without the outline. Did i miss something?

If you take a look to "Keep Environment", it keeps background color in (alpha=0) pixels. In LV mixing of pixels that's generating this outline if you have a bright background. That's very logical result. Can you see where is the problem? Also always test that mixing of output with background on a compositing software. It can calculate this edges better than LV output.

Freezing C4D when Octane Live Windows Active + Viewport (C4D Standard Renderer + Interactive Render Region).

OctanC4D 2.23.2 R5 (GTX Titan, Windows 8.1) + C4D R16.050

eyeonestudio wrote:Freezing C4D when Octane Live Windows Active + Viewport (C4D Standard Renderer + Interactive Render Region).

OctanC4D 2.23.2 R5 (GTX Titan, Windows 8.1) + C4D R16.050

It never have been supported. Interactive render regions's system is not fitting to our workflow.