OctaneRender™ Standalone 2.03

[Tugpsx]

Thanks for the update

[gabrielefx]

thanks!

I want side by side render in Max!

[Rikk The Gaijin]

We are working on displacement. It is no so easy to make as in CPU renders.

Indeed it is! Thank you for your work! Noone blames you, I think. We're just reporting the issues.

Exactly! Karba always reacts like we are attacking him personally... Relax man, you're doing a great job!

[manalokos]

Hello

When I deactivate a network render node or a GPU on my machine during render I loose all the samples made by that node or GPU, why??
This is complete maddness!
This behaviour has been happening since 1.xx and it is not logical nor useful, could you correct this in future versions?

Example, I have a render using 1 master machine and 1 network machine, if have 1000 samples of render and deactivate the network machine or have a problem with the network itself I get to loose 500 that go to oblivion just like that.

Kind regards
Filipe Alves

[abstrax]

Hello

When I deactivate a network render node or a GPU on my machine during render I loose all the samples made by that node or GPU, why??
This is complete maddness!
This behaviour has been happening since 1.xx and it is not logical nor useful, could you correct this in future versions?

Example, I have a render using 1 master machine and 1 network machine, if have 1000 samples of render and deactivate the network machine or have a problem with the network itself I get to loose 500 that go to oblivion just like that.

Kind regards
Filipe Alves

It's on our to-do list, but not as easy as it sounds.

[gordonrobb]

Rikk: Is this a displacement that has mid grey as the zero point (like form ZBrush) and therefore you have to use a negative shift amount. I've not downloaded the update yet, but am fairly sure this tearing is happening when you have to use a negative shift to give you a negative displacement. Displacement is superb for straight displacement stuff (ie black is zero), but Zbrush is a real problem.

It's like whatever calculation is being done to displace, is not being done the same way in reverse when using shift. Frustrating, but I have confidence you guys will figure it out. As long as you are working on it?

[prodviz]

.exr output darker than .png issue:

http://render.otoy.com/forum/viewtopic. ... 17#p194017

[Rikk The Gaijin]

Rikk: Is this a displacement that has mid grey as the zero point (like form ZBrush) and therefore you have to use a negative shift amount. I've not downloaded the update yet, but am fairly sure this tearing is happening when you have to use a negative shift to give you a negative displacement. Displacement is superb for straight displacement stuff (ie black is zero), but Zbrush is a real problem.

It's like whatever calculation is being done to displace, is not being done the same way in reverse when using shift.

Precisely.
Also, I need to mention that, even if it still not perfect, the displacement now is way faster than before, so keep it up!

[gordonrobb]

Will take a look then. Hopefully the LW will update to this SDK soon too.

[aufwind]

For me it's the opposite way.
Displacement in the following scene is 30% slower than in Version 2.02!

Both Images are rendered with the same settings.
Mesh Import via Obj-Format. The Scene has about 800k Tris.
Displacement is used with the Sofa which has most of the Poly-Count.
Scene is lit by Octane Sun. Direct lighting Kernel. Windows 7. 2x Titan.

I had to lower the Ray-Epsilon Value to 0.001 to get rid of black artifacts
on the sofa, which results in something like a translucency effect on the part that
is hit directly by the sun light. This effect is in Version 2.03 much more subtle now.

First One rendered with 2.03.
General appearance of Displacement looks quite different compared to 2.02.

2.03.jpg

Personally I do like the look of Displacement in Version 2.02 more (besides the glowing thing).

2.02.jpg