OctaneRender™ Standalone 3.06 TEST 3

[coilbook]

any eta when will be adaptive sampling available for 3ds max users?

[kavorka]

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the filename.

[rrbarb]

Sometimes we use exposures below 1.0

Yes- same here.

./rrb

[vijay]

vijay_thirukonda, I made a mistake. This bug is associated with the value expected exposure. I initially put a high value and during rendering it reduce. After that, it turns out this bug. I do it to adaptive sampling worked as good as the previous version. If I save the scene and open again there is no this error. Expected exposure a very strange option,

When we bump up the exposure, dark areas now becomes brighter and the noise will be slightly visible more when compared to low exposure. So we render those areas with some more samples.

now even if I put the noise threshold 1.0 adaptive sampling with long time does not work, and the result is obtained as before without adaptive sampling, the light areas without any noise, in dark areas noisy.

Due to artifacts, we wait for some additionals samples to complete before starting adaptive sampling in the dark areas

[vijay]

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the filename.

This is fixed. will not happen in next release

Vijay

[vijay]

Is there a reason the adaptive sampling expected exposure can't be set below 1.0? Or is this just an oversight?

Expected exposure: This should be set to the approximate exposure you plan to use in the imager.

Sometimes we use exposures below 1.0

It's now changed. From next build, you can set the expected exposure value below 1.

Vijay

[nrygpu]

Hello,

I was getting advice on the best method to render a large animation from C4D here: viewtopic.php?f=30&t=60308

I figure it makes sense to post this here as well as I am currently running Octane 3.06 downloaded from this thread:

I have setup C4D on a Windows 10 based system that has Quadro GPU's. The Windows "master" computer is running C4D R18 with latest update, Octane C4D plugin 3.06 and standalone 3.06. Next I have a GPU server with 8 GPU's that is running Ubuntu 16.04 LTS and also Octane standalone 3.06. I have run the daemon script in Linux and it successfully generates the run_octane_daemon.sh

Next I run the run_octane_daemon.sh and everything seems to be working as it should. However, the problem I am having now is that no matter what I try I can't see the render slave on the master. It simply does not show up in either C4D or octane standalone on the master. As you can see in the screenshot below, it is all running correctly except no slave is detected by the master.

https://www.screencast.com/t/YdEooXxqMxcT

I have spent hours checking the network settings. I made sure I can ping to the private IP of both the Windows master and the Linux slave and vice versa. I also opened up firewall settings to make sure that nothing is blocked. There is no virus software running in this testing environment. This is all running inside of an HPC grade data center with 10Gbps networking between the machines.

I am really stuck here because I need to start rendering this animation, but the only way to get it done is if I can use all 20 GPU's via netrender.

Help is very much appreciated!

[bepeg4d]

Hi,
I have already answered you via PM, let's see if updating the master and the enabling of the logging will giving more info on what is going on.
ciao beppe

[kavorka]

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the filename.

This is fixed. will not happen in next release

Vijay

Thanks!

[kavorka]

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the filename.

This is fixed. will not happen in next release

Vijay

On the same note, if you save your render passes and use %p in your file name when using the batch script (Only tried this with the old script, not the new render jobs) it wont skip existing. It will just restart from frame 1 even if you have some frames rendered out in that folder.