1.6 DR

[Dionysios.TS]

these differences in noise are by design and were always present - DR in Corona works "kinda like" bucket renderer to avoid constant big data transfers. The noise level should converge to uniform level in few more passes

Thanks for getting back Ondra.
I never saw till today such a big difference, specially with a noise level limit set to 3.

Do we have any tip to avoid this?

Thanks!

Dionysios -

[Dionysios.TS]

Build 06/03/17: Once the DR process is finished, many often an instance of 3ds Max process remains opened and for this reason the next job is not submitted to that DR server. I also noticed that if I close the DR window/process, that 3ds Max process still remains active in the OS.

Dionysios -

[ihabkal]

Build 06/03/17: Once the DR process is finished, many often an instance of 3ds Max process remains opened and for this reason the next job is not submitted to that DR server. I also noticed that if I close the DR window/process, that 3ds Max process still remains active in the OS.

Dionysios -

I second that, but I think if you give the render nodes a few minutes they will reset themselves and become ready that's what I noticed.

[Dionysios.TS]

Build 06/03/17: Once the DR process is finished, many often an instance of 3ds Max process remains opened and for this reason the next job is not submitted to that DR server. I also noticed that if I close the DR window/process, that 3ds Max process still remains active in the OS.

Dionysios -

I second that, but I think if you give the render nodes a few minutes they will reset themselves and become ready that's what I noticed.

Thanks for getting back.

As many often Backburner controls the render queue, I think the DR process should close 3ds Max almost immediately before the next render automatically gets sent to the servers...

Let's see what the dev team will tell us about it.

Thanks,

Dionysios -

[ihabkal]

I am more worried about the fact that all the builds after Dec 13th crash my 3dsmax at time of collection of extra passes at the end of the dr rendering phase, and the light mixer and post effects spinners have no effect midway of the dr rendering. so for 100 passes, at around 50 spinners don't have an effect, and as soon as the number hits 100 max crashes, this is still happening with the latest build and at work and at home. it doesn't happen when you render a couch alone, but if you render a real project it happens. I would say memory leakage or permissions to copy stuff over the network.
this whole problem goes away as soon as I reinstall 1.5.2 and copy the dec 13th update.

[Jens]

I can't even get DR working on latest build (08-03-2017). First a crash on the DR node:

(see attached)

I then restarted the node while the main PC kept rendering (had "search LAN during render enabled). The node picked up the DR signal nicely, but was stuck again just "waiting for render to start" through the whole night. No crash though.

max 2016, 6k img res and around 20mill poly interior scene.

[Dionysios.TS]

I confirm that 3ds Max process doesn't close itself properly when a DR is finished. The process remains opened and the next DR job for this reason doesn't start...

Thanks,

Dionysios -

[sevecek]

I confirm that 3ds Max process doesn't close itself properly when a DR is finished. The process remains opened and the next DR job for this reason doesn't start...

Thanks,

Dionysios -

3ds Max on slaves shouldn't close inbetween renders. When you stop the render, the status message on slaves should go back to "Waiting for render start" and it should start rendering immediately after starting new render. It's weird that the next render won't start; what does the log say?

[Dionysios.TS]

I confirm that 3ds Max process doesn't close itself properly when a DR is finished. The process remains opened and the next DR job for this reason doesn't start...

Thanks,

Dionysios -

3ds Max on slaves shouldn't close inbetween renders. When you stop the render, the status message on slaves should go back to "Waiting for render start" and it should start rendering immediately after starting new render. It's weird that the next render won't start; what does the log say?

Yes, this is correct, but I noticed this thing:

When the DR don't start with the next job is because they exist two 3ds Max processes created from the DR in the same time.
Basically, the first time DR starts it creates a 3ds Max session in standby mode which is the one used for the DR rendering. Then when the job is finished it may happen that DR doesn't closed up 3ds Max properly and remains open/active. In this case no new DR jobs can be loaded, everything is blocked.

Solution: Close manually DR and started again but today I saw that even doing so the 3ds Max session remained open and DR didn't loaded the new job as well....

[Dionysios.TS]

Sorry guys, what is this???

2017-03-09 11:38:49   Finished EXR dump after 0 s
2017-03-09 11:44:03   Received sampling focus mask
2017-03-09 12:03:51   Received sampling focus mask
2017-03-09 12:23:12   Received sampling focus mask

The DR servers don't do anything for about ten minutes after they received the sampling focus mask command... Is this normal?

[Dionysios.TS]

Today I am having a lot of problems with DR as you can see.... Now I get this:

2017-03-09 13:40:45   Sending file to remote side failed
2017-03-09 13:40:59   Sending file to remote side failed
2017-03-09 13:41:09   Sending file to remote side failed
2017-03-09 13:41:19   Sending file to remote side failed
2017-03-09 13:41:29   Sending file to remote side failed
2017-03-09 13:42:13   Sending file to remote side failed
2017-03-09 13:43:15   Sending file to remote side failed
2017-03-09 13:44:16   Sending file to remote side failed
2017-03-09 13:46:19   Sending file to remote side failed
2017-03-09 13:48:22   Sending file to remote side failed
2017-03-09 13:50:26   Sending file to remote side failed
2017-03-09 14:09:46   Sending file to remote side failed
2017-03-09 14:09:59   Sending file to remote side failed
2017-03-09 14:10:10   Sending file to remote side failed
2017-03-09 14:10:21   Sending file to remote side failed
2017-03-09 14:10:31   Sending file to remote side failed
2017-03-09 14:10:41   Sending file to remote side failed
2017-03-09 14:10:52   Sending file to remote side failed
2017-03-09 14:11:02   Sending file to remote side failed
2017-03-09 14:11:13   Sending file to remote side failed
2017-03-09 14:11:23   Sending file to remote side failed
2017-03-09 14:11:33   Sending file to remote side failed
2017-03-09 14:11:44   Sending file to remote side failed
2017-03-09 14:11:55   Sending file to remote side failed
2017-03-09 14:12:05   Sending file to remote side failed
2017-03-09 14:12:15   Sending file to remote side failed
2017-03-09 14:12:26   Sending file to remote side failed
2017-03-09 14:12:36   Sending file to remote side failed
2017-03-09 14:13:01   Sending file to remote side failed
2017-03-09 14:28:48   Sending file to remote side failed
2017-03-09 14:29:02   Sending file to remote side failed
2017-03-09 14:29:12   Sending file to remote side failed
2017-03-09 14:29:25   Sending file to remote side failed
2017-03-09 14:30:27   Sending file to remote side failed
2017-03-09 14:31:28   Sending file to remote side failed
2017-03-09 14:32:29   Sending file to remote side failed
2017-03-09 14:34:32   Sending file to remote side failed
2017-03-09 14:36:35   Sending file to remote side failed

Why this is happening? Network works perfectly!

[sevecek]

This means the connection is still open, but the master doesn't read messages from the slave. That's something that never happened to me ...
What do you see in DR tab on master? Can you please send me DR logs from the slave?

[Dionysios.TS]

This means the connection is still open, but the master doesn't read messages from the slave. That's something that never happened to me ...
What do you see in DR tab on master? Can you please send me DR logs from the slave?

Thanks for getting back...

Can I post them here?

[sevecek]

Sure.

[Dionysios.TS]

This means the connection is still open, but the master doesn't read messages from the slave. That's something that never happened to me ...
What do you see in DR tab on master? Can you please send me DR logs from the slave?

The problem is that the "master" is a server and not my main workstation and I have no DR tab to check as the work is submitted by Backburner and the render window is the 3ds Max's native one...  -.-

I posted today a question of how can I turn on Corona's VFB on the slaves as well cause usually I send the jobs via Backburner from my workstation to another server PC which uses DR to connect to the other slaves.

I'll send you now the DR logs from the slaves...