DR problem.............

[Frood]

So if i understand i have to use \\NAS\Données\........... and not "Z:\dossier ARCHI\.... ?

Well, "have to" is not quite what I meant. It´s more a general advice. You never know how your scene gets rendered tomorrow :) When it comes to Backburner for example, there may be no "Z:\" available because BB-Server is running as a different user account or service  who has no "Z:\". If you are using and running DrServer interactively as a user who has Z:\ mapped you are of course fine. But using UNC paths does not hurt and you avoid most of the standard issues when rendering with multiple nodes.

As for your scene: I didn´t found any errors, I was just stating that your scene renders fine here on dr-slaves with vray installed :)

Good Luck!

[aurelarchi]

Ok !

Thanks a lot for your time ! :)

[Frood]

If you are still interested to resolve your issue, please do as you were advised in reply #1 and reply #3 and check the results from the slaves directly using the "retain EXRs" feature. You somehow refused to give us any result until now.

Good luck

[aurelarchi]

Of course i'm interested i use only DR rendering for all my commercial project so i have to found where is this error.
Please find here the EXR's files :

https://www.wetransfer.com/downloads/b323042ce2af5990ab9615d20635990420150309140148/8df2fcf4e85bb60d0f04a19f4ccbd88e20150309140148/545718

Thanks

[maru]

Are these EXRs from a rendering that uses the floor texture? Because the floor is clearly solid grey. This would mean that the texture cannot be reached by the render nodes. Now the question is why and how to fix it...

[aurelarchi]

Yes Maru, EXR's by the 2 slaves from the scene with the floor texture.
I tried with UNC in z:\ and \\NAS\ same issu...............
The main machine work with the NAS too and no problem with the link..................

[Frood]

As maru wrote, the slave cannot (or does not) access the texture. Aurelarchi, you haven´t started drserver as Administrator or any other user than the one who is currently interactively logged in by accident, have you? If so, that would be the cause.

[aurelarchi]

Drserver always started as administrator.
Corona fully activated on the slaves.

[aurelarchi]

Ok solved !
At first i used UNC path like this : \\NAS\Données\................
or like this : z:\Données\...............
But DR is only ok when i use : \\my nas ip address\Données\..............

That's all folks !
Thank you all for the help ! ;)

[maru]

Wow. Great that you managed to solve it and sorry that we couldn't help. Could you explain better what you eventually changed to make it work? You changed path in asset browser?

[aurelarchi]

Don't worry you help to solve it !
I fact you have choice for a network link :
For example my NAS is named z: on network drive but dont work in UNC link on DR.
So i just replaced the name of the network drive by the ip adress.
This is mean :
Before  -> z:\Données\...............
Now -> my nas ip address\Données\..............

Now DR is ok, but i clearly don't have this issu on vray , i can use z: , \\NAS , ip adress, all this link in UNC work good.

[borisquezadaa]

Ok... as i see there is a potential translation error of names using corona DR on the UNC path names. And the solution was to use IP address instead?. Any clues on why DR server does not resolve ip from name?.
If that is the case it could resolve a lot of error issues around.

[Ondra]

this is not related to corona DR, this is 3ds max thing...

[Frood]

Not even max, it´s the basic network configuration which is faulty imho. Name resolution does just not work. When opening a shell on the slave I bet a "ping nas" would´t work either. We would have to know a few other things to resolve that completely, e.g. is there a DHCP and/or name server in his network or is he using static ip´s and a etc/hosts file, how is the tcp/ip configuration set on the slave etc... But yes, it´s in fact no CoronaDR issue (any more :)