OctaneRender™ Standalone 1.25

[Area D]

Hi,
there is a problem with object layer..I use it to overlap parts of the scene in post production (Photoshop) in order to avoid clipping on a completely rendered image. The pieces that make up the final image but never correspond to the same fully rendered. These parties have in fact along the edges of the dark pixels that really should not be there. Here is a imagine to understand better ..

Orgininal image completely rendered

Union of the parts separately rendered

I hope I have explained the problem .. if you have any questions I'm here ..

Thanks

Ps: it isn't a post production problem.

[manalokos]

Could you give users some instructions about how to normally manipulate an environment texture?
Now it has the same options as a regular texture, including spherical and box mapping, but controls don't works as expected and spherical mapping makes GPUs fail.


Thanks
Best regards
Filipe

[ROUBAL]

Hi guys, I have been far away from Octane and 3D stuff in general for a long time, due to big family troubles. So the last version I used was the 1.20a stable, and I haven't even used yet the so expected Blender plugin...

So, I just discover the 1.25 release (with some worries because of LUA as I have always been totally hopeless at programming).

But my main trouble at first glance is that the Daylight system doesn't work. Is it normal for this release or a problem on my side ?

Thanks in advance.

[roeland]

Hi,
there is a problem with object layer..I use it to overlap parts of the scene in post production (Photoshop) in order to avoid clipping on a completely rendered image. The pieces that make up the final image but never correspond to the same fully rendered. These parties have in fact along the edges of the dark pixels that really should not be there. Here is a imagine to understand better ..

I hope I have explained the problem .. if you have any questions I'm here ..

Thanks

Ps: it isn't a post production problem.

This is a normal artifact from antialiasing. You can decrease it by setting filter size to the minimum and rendering at a higher resolution but it will is always there.

What happens at the edges is that you get pixels contain a mix between two objects. If you render both object every sample has either one of the objects and you get a normal fully opaque pixel. If you render separately you get something like 50% transparency in the image of the first object, and 50% transparency in the image of the second object. If you composite these image the result is a pixel with 25% transparency.

Or instead of transparency a part of one of the objects which is shadowed by the other object may show through, causing a dark edge.

--
Roeland

[roeland]

Hi guys, I have been far away from Octane and 3D stuff in general for a long time, due to big family troubles. So the last version I used was the 1.20a stable, and I haven't even used yet the so expected Blender plugin...

So, I just discover the 1.25 release (with some worries because of LUA as I have always been totally hopeless at programming).

But my main trouble at first glance is that the Daylight system doesn't work. Is it normal for this release or a problem on my side ?

Thanks in advance.

If you are hopeless at programming, that's not a problem. You still don't need to write scripts to render something in Octane.

What do you mean by the Daylight system doesn't work? Does it not render correctly or are there some inputs which don't work? Or do you get a GPU crash? I tested the daylight and texture environments with spherical mapping and didn't see any issues.

--
Roeland

[PhilBo]

Don't know if this has been reported yet, but when I render with a large bloom / glare with Alpha background enabled, with or without a background image, the glare lines show up over the model but not over the background. When I then go to composite in Photoshop, the glare lines are only over where the model is.

Does that make sense?

Is that how it's supposed to be?

[ROUBAL]

Thanks Roeland :

If you are hopeless at programming, that's not a problem. You still don't need to write scripts to render something in Octane.

Good news!

What do you mean by the Daylight system doesn't work? Does it not render correctly or are there some inputs which don't work? Or do you get a GPU crash? I tested the daylight and texture environments with spherical mapping and didn't see any issues.

When selecting the daylight system, the render still displays the default grey background like the basic texture environment. I stopped and started again the render, switched from daylight to texture and back to daylight... nothing, no procedural sky and sun (tried old and new sky system).

I tried with creating a new scene in 1.25 as well as opening ocs made with 1.20a ... with same result : no procedural sky and sun.

In 1.20a it works perfectly.

EDIT : I have deleted the default Environment node and created a new one from scratch, and the Daylight system now works fine !

By the way : negative scaling is still not available in transform ?

[Area D]

If you render both object every sample has either one of the objects and you get a normal fully opaque pixel. If you render separately you get something like 50% transparency in the image of the first object, and 50% transparency in the image of the second object. If you composite these image the result is a pixel with 25% transparency.
--
Roeland

Why this?
I thought that by stacking two images 50% trasparency obtained one 100% opaque..

[roeland]

No, that's wrong. The bottom layer has 50% opacity, so you see 50% bottom layer and 50% background. If you add the top layer, also 50% transparency, then you see 50% top layer, and 50% of what's below, i.e. 25% bottom layer and 25% background.

--
Roeland