Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Dionysios.TS

Pages: 1 ... 49 50 [51] 52
751
[Max] Daily Builds / Re: Daily Builds
« on: 2016-05-03, 15:51:07 »
Thanks for testing as now I can't.

So you used DR + Adaptivity + Denoiser as well?

Dionysio -

752
[Max] Daily Builds / Re: Daily Builds
« on: 2016-05-03, 14:09:11 »
Sorry for asking you guys but what's the situation now with RC2 about DR + Denoise + Adaptivity? Does the DR Server work perfectly with all these?

Thanks,

Dionysios -

753
[Max] General Discussion / Re: Resolution for GEAR VR
« on: 2016-05-03, 13:55:27 »
I made some tests and it seems that 8192x8192 is the best limit res.

Thanks,

Dionysios -

754
[Max] Resolved Bugs / DR Servers - Initial Pass
« on: 2016-05-03, 11:27:29 »
Hi guys, is about a week now I am seeing a strange behaviour with DR.

When I sent a job with Backburner to a Master PC which then has to use DR with another server, the server task always shows Rendering Initial Pass and not the effective passes is calculating, if it really does. How is possibile after 3hrs and 49mins we are still in the Initial Pass process? Is this ok or something is wring with DR?

I attach an image to show you what's going on...

Thanks in advance.

Dionysios -

755
[Max] General Discussion / Resolution for GEAR VR
« on: 2016-05-02, 17:02:20 »
Hi guys, a simple question here, what's should be the final resolution to render the Spherical images to use in Gear VR? I guess 4096x4096 is the minimum but for a real great experience and clarity what do you suggest? I don't want to render a 12000x12000 for nothing.... -.-

I search the forum but didn't found an official info about it.

Thanks in advance,

Dionysios -

756
[Max] Daily Builds / Re: Daily Builds
« on: 2016-04-12, 09:30:11 »
Hi guys! These DR Denoise and Adaptivity issues are still here unfortunately. Are the same problems I had weeks ago. Let's hope the team will find a good solution soon.

Cheers!

Dionysios -

757
[Max] Daily Builds / Re: Daily Builds
« on: 2016-03-29, 16:32:41 »
Ok, I turned off adaptivity and I had no issues!
I confirm that all the PCs have the same version.

So this is what is happening:

 - Adaptivity ON

Single PC works fine
DR stops working after 10 passes.

- Adaptivity OFF

Single PC works fine
DR works fine.

Dionysios -

758
[Max] Daily Builds / Re: Daily Builds
« on: 2016-03-29, 16:20:26 »
Let me check!

759
[Max] Daily Builds / Re: Daily Builds
« on: 2016-03-29, 14:38:09 »
Hi all! I am having a lot of issues lately with DR and the latest daily versions. I also opened a ticket some days ago.

Anyway, this morning I installed the 28/03/2016 and something weird is happening ONLY when I use DR.

I start the rendering process with a pass limit of 100 using my main workstation + 2 servers.
Once the engine arrives to 10 passes, stops! Like if I pressed the cancel rendering button and of course I didn't! :)

Denoise is off.
Adaptive is on as by default.
Time limit is everywhere set to 0 but even if I change any number the behavior is the same.

Can you guys check if you have the same problem?

Thanks in advance,

Dionysios -

760
Ok, ticket submitted!

Dionysios -

761
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 -


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

Typo error!!! -.-

763
[Max] Resolved Bugs / Hi Res images and strange DR behaviour
« on: 2016-03-22, 12:50:41 »
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 -

764
[Max] Resolved Bugs / Re: DR doesn't work - Build 06/03/16
« on: 2016-03-07, 14:33:43 »
Can you try with adaptivity and denoising disabled? Maybe they don't like DR? Or maybe there is some bug/unfinished feature in the daily build.

I already tried, same problem.

Thanks,

Dionysio -

765
[Max] Resolved Bugs / DR doesn't work - Build 06/03/16
« on: 2016-03-07, 11:49:45 »
Hi all!

Is it me doing anything wrong or there is a problem with DR and the latest 06/03/16 build?

So this is what happens:

When I start rendering with my main workstation everything seems going fine and the first passes are calculated. Once the DR server machines start to work, my VFB deletes automatically the image calculated at that point, and seems to start all over again. At that point when the DR image information arrive to the main workstation the final result seems always the same! At the end, the image is grainy and I guess the DR doesn't work perfectly. There is a kind of bad synchronization of the passes I think.

Actually, the same image calculated with my workstation is way better and cleaner than the DR one.

Can you confirm this?

Thanks in advance,

Dionysio -

Pages: 1 ... 49 50 [51] 52