OctaneRender™ Standalone 3.03.4 Tweet

[manalokos]

Saving a render in 16-bit png will write an image with a incorrect tonemap.

[coilbook]

we got constant rendering stops like it finished rendering and goes to the next frame and nothing happens with newest nvidia drivers 372.70 Not sure if drivers play role on octane reliability?

[eyeonestudio]

2016-09-09_10-50-48.png

VDB Volume - shadow problem still exist.

[enricocerica]

Hi,

I find very difficult to select and change an emitter setting in complex scenes as it is not always visible (behind the scene, small plane in a container, ...) and then not easily selectable.
It would be really useful to have a repository collecting all the emitting materials of a scene, isolating them from the other materials.
Thanks

[coilbook]

Can we get an option of Global samples for all lights and mesh emitters in the scene. Currently we have to go to each light and increase samples

[haze]

2016-09-09_10-50-48.png

VDB Volume - shadow problem still exist. :cry:

Try lowering your Volume Step Length for both volumes - this is a common problem when overlapping volumes that are very dense, and have a high step length. If this doesn't solve the problem, please send me a orbx so that I can try to figure out what's going on.

What's happening is this - the renderer ray marches into one volume, and then the intersection of the volumes, and then the other volume. If the step length (set at 1m in your scene) is too small, say, a little bigger than the volume, then the renderer will actually take 3 smaller steps through the overlapping regions of the volumes. This will actually cause the rendering of the overlapping region to be more accurate - in this case, more dense and therefore darker...

[manalokos]

Here is a demostration of the tonemap bug in the current version:

[bepeg4d]

Hi Philipe,
there is definitly an issue with the Save PNG 16bit command.
if you correct the Gamma in Photoshop to 2.2, the image should be the same as you see in Octane, but only with Linear response curve:

Screen Shot 2016-09-13 at 14.32.49.jpg

the workaround is to save the image with the next icon even if the render passes are not active:

Screen Shot 2016-09-13 at 14.43.40.jpg

ciao beppe

[eyeonestudio]

2016-09-09_10-50-48.png

VDB Volume - shadow problem still exist.

Try lowering your Volume Step Length for both volumes - this is a common problem when overlapping volumes that are very dense, and have a high step length. If this doesn't solve the problem, please send me a orbx so that I can try to figure out what's going on.

What's happening is this - the renderer ray marches into one volume, and then the intersection of the volumes, and then the other volume. If the step length (set at 1m in your scene) is too small, say, a little bigger than the volume, then the renderer will actually take 3 smaller steps through the overlapping regions of the volumes. This will actually cause the rendering of the overlapping region to be more accurate - in this case, more dense and therefore darker...

I did some tests.

Houdini (Use Instance - Packed primitive)

H.png

Arnold
I'm using Cloner(Off render-instance).
Arnold it does not support VDB-Render-Instance

A.png

Octane (Non Instancing)
Q: I'm using Cloner(Off render-instance). But Video Memory usage has not increased . Why?

O.png

So we need other solution !!

[haze]

eyeonestudio: are you able to share an orbx for me to take a look?