Hi Res images and strange DR behaviour

[Dionysios.TS]

Hi guys, I am using the final daily build 13/02/2016 and every time I use Backburner & DR with high resolution images (over 5.000px) I notice some issues.

Here what happens:

- The scene (around 10.000.000 polys and rendered at 6.000px) is sent to a server here in the office via Backburner and DR turned on.
- The server starts to loading the scene and do all the necessary tasks.

And here start some strange problems:

- The main server starts the rendering process and the initial pass I think takes too long.
- In the meantime, the DR server starts the process too and even there, the initial pass is a bit long to be processed.
- When the passes finally start to go on, the DR server seems always to be stuck at the 2nd pass. The rendering process bar goes on and when it finishes the second pass, instead of going to the next one, the information shows to start the second all over again.
- The main machine seems to go on with all the passes without any issues. Only the DR one has a strange behavior.

Here is the log:

21/03/2016 23:25:14;  Max is ready
21/03/2016 23:25:15;  Frame 39 assigned
21/03/2016 23:25:16;  BEGIN FRAME 39; TASK 1 OF 1; (C:\Users\DTSAGKAROPOULOS\AppData\Local\CoronaRenderer\DrData\dr_out.png);
21/03/2016 23:26:50;  CORONA : Parsing the scene
21/03/2016 23:27:39;  CORONA : Calculating displacement
21/03/2016 23:27:39;  CORONA : Building acc. structure
21/03/2016 23:27:43;  CORONA : Computing light distr.
21/03/2016 23:27:43;  CORONA : Computing secondary GI
21/03/2016 23:28:08;  CORONA : Rendering
21/03/2016 23:28:09;  CORONA : Rendering initial pass
21/03/2016 23:45:52;  CORONA : Rendering pass 2
22/03/2016 04:27:31;  CORONA : Saving + Cleaning up
22/03/2016 04:27:41;  END FRAME 39; TASK 1 OF 1; (C:\Users\DT\AppData\Local\CoronaRenderer\DrData\dr_out.png); 1.81e+004s; 0 faces; MEM 12489 MB;
22/03/2016 04:27:41;  Frame 39 completed; Elapsed time 05:02:26
22/03/2016 04:27:41;  Job Complete - Results in C:\Users\DT\AppData\Local\CoronaRenderer\DrData\
22/03/2016 04:27:41;  Send End of Job command to Max
22/03/2016 04:27:47;  Job Completed with Warning(s) - see above
22/03/2016 04:27:47;  Total elapsed time 05:02:33
22/03/2016 04:27:47;  Scene C:\Users\DT\AppData\Local\CoronaRenderer\DrData\received_scene_1842463640.max completed.

This was a 5 hrs rendering.....

What do you think, is this a bug???

Thanks in advance.

Dionysios -

[maru]

Note: I am not sure if it's a typo or not, but the newest daily build is 12.03.2016.
I should soon get back to you with some ideas what might be wrong.

[Dionysios.TS]

God, I am sorry, the build is 12/03/2016.

Typo error!!! -.-

[maru]

"22/03/2016 04:27:47;  Job Completed with Warning(s) - see above"
But there is no warning above, right?

Can you submit this as a ticket here? https://coronarenderer.freshdesk.com/support/tickets/new

[Dionysios.TS]

I took a closer look, I paste here all the Maxlog text of that session:

Max install location: C:\Program Files\Autodesk\3ds Max 2016\
21/03/2016 23:24:21;  Max file being rendered: C:\Users\DT\AppData\Local\CoronaRenderer\DrData\received_scene_1842463640.max
21/03/2016 23:24:21;  Renderer: Corona 1.4 DailyBuild Mar 12 2016
21/03/2016 23:25:00;  ***WARNING*** Missing dll: vrender2016.dlr - VRayShadow
21/03/2016 23:25:00;  CORONA: Corona is up and running. Corona version: 1.4 DailyBuild Mar 12 2016, netrender mode: on, slave mode: on, quiet mode: on, Max gamma (display/input/output): 2.2/2.2/2.2
21/03/2016 23:25:00;  MENTAL RAY LOG: MI   0.0      8 MB progr: reading startup file "rayrc"

21/03/2016 23:25:00;  MENTAL RAY LOG: MI   0.0      8 MB progr: parsing file rayrc

21/03/2016 23:25:00;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library base.dll (.\shaders_standard\mentalray\shaders/base.dll)

21/03/2016 23:25:00;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library contour.dll (.\shaders_standard\mentalray\shaders/contour.dll)

21/03/2016 23:25:00;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library physics.dll (.\shaders_standard\mentalray\shaders/physics.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library lume.dll (.\shaders_standard\mentalray\shaders/lume.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library subsurface.dll (.\shaders_standard\mentalray\shaders/subsurface.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library 3dsmaxshaders.dll (.\shaders_standard\mentalray\shaders/3dsmaxshaders.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library 3dsmaxhair.dll (.\shaders_standard\mentalray\shaders/3dsmaxhair.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library paint.dll (.\shaders_standard\mentalray\shaders/paint.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library architectural.dll (.\shaders_standard\mentalray\shaders/architectural.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library production.dll (.\shaders_standard\mentalray\shaders/production.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library adskshaders.dll (.\shaders_standard\mentalray\shaders/adskshaders.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library SubstanceShader.dll (.\shaders_standard\mentalray\shaders/SubstanceShader.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0      8 MB progr: loaded shader library VectorMapShader.dll (.\shaders_standard\mentalray\shaders/VectorMapShader.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0     11 MB progr: loaded shader library FShader3.dll (./FShader3.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: LINK 0.0     11 MB progr: loaded shader library PointCloudShader.dll (./PointCloudShader.dll)

21/03/2016 23:25:01;  MENTAL RAY LOG: MI   0.0     11 MB progr: parsing file autodeskBase.mi

21/03/2016 23:25:01;  MENTAL RAY LOG: MI   0.0     11 MB progr: parsing file autodeskPointCloudBaseShader.mi

21/03/2016 23:25:01;  MENTAL RAY LOG: MI   0.0     11 MB progr: parsing file autodeskPointCloudShader.mi

21/03/2016 23:25:01;  MENTAL RAY LOG: MI   0.0     11 MB progr: parsing file FShader3.mi

21/03/2016 23:25:14;  Max is ready
21/03/2016 23:25:15;  Frame 39 assigned
21/03/2016 23:25:16;  BEGIN FRAME 39; TASK 1 OF 1; (C:\Users\DT\AppData\Local\CoronaRenderer\DrData\dr_out.png);
21/03/2016 23:26:50;  CORONA : Parsing the scene
21/03/2016 23:27:39;  CORONA : Calculating displacement
21/03/2016 23:27:39;  CORONA : Building acc. structure
21/03/2016 23:27:43;  CORONA : Computing light distr.
21/03/2016 23:27:43;  CORONA : Computing secondary GI
21/03/2016 23:28:08;  CORONA : Rendering
21/03/2016 23:28:09;  CORONA : Rendering initial pass
21/03/2016 23:45:52;  CORONA : Rendering pass 2
22/03/2016 04:27:31;  CORONA : Saving + Cleaning up
22/03/2016 04:27:41;  END FRAME 39; TASK 1 OF 1; (C:\Users\DT\AppData\Local\CoronaRenderer\DrData\dr_out.png); 1.81e+004s; 0 faces; MEM 12489 MB;
22/03/2016 04:27:41;  Frame 39 completed; Elapsed time 05:02:26
22/03/2016 04:27:41;  Job Complete - Results in C:\Users\DT\AppData\Local\CoronaRenderer\DrData\
22/03/2016 04:27:41;  Send End of Job command to Max
22/03/2016 04:27:47;  Job Completed with Warning(s) - see above
22/03/2016 04:27:47;  Total elapsed time 05:02:33
22/03/2016 04:27:47;  Scene C:\Users\DT\AppData\Local\CoronaRenderer\DrData\received_scene_1842463640.max completed.

As you can see the only warning is: 21/03/2016 23:25:00;  ***WARNING*** Missing dll: vrender2016.dlr - VRayShadow

But they're no Vray elements or materials in the scene. On my main workstation I installed the Vray trial just to be able to open Vray scenes and convert materials. The servers don't have this trial installed so probably there is something in the scene that produces this error at the server side.

You want me to open a ticket in any case?

Thanks for your support.

Dionysios -

[Dionysios.TS]

Ok, ticket submitted!

Dionysios -

[Ondra]

Do you experience speedup compared to not using DR? It is possible this is again the issue with the pass count resetting when progress is sent to the master

[Dionysios.TS]

I think that using DR for now doesn't give a boost to the overall process. After 7 hours the image is a bit grainy and in my opinion only the master does the job at the end.
Last week I opened the DR folder and I got the DR files from the slave, I was surprised to see only a stripe (portion of image) and not the full image itself. I guess is not a correct behavior...

Dionysios -

[Ondra]

that is actually correct behavior, we send the image broken down to stripes to avoid memory and network usage spikes. Can you try doing comparison - for example 1 hour rendering with and without DR, and comparing noise level and passes reached?

[Dionysios.TS]

Ok, no problem, I can do this but I'll answer on Friday morning as I am out of office tomorrow.


Dionysio -

[Dionysios.TS]

Hi Ondra, I made as promised some tests today and I used the last RC4 version. Everything seems fine.

Same image in hi res calculated for 1 hour with and without DR.

With DR: 13 Passes
Without DR: 7 Passes

The results are correct, with DR image is cleaner as expected!

Don't see any strange issues for now, probably is the RC4? Something you guys fixed?

Thanks,

Dionysio -

[Ondra]

it was probably random or just oversight, we did not do any specific fixes in RC4. I am closing this down, let us know if you find any problem in the future