DR issue

[vjaramillo]

So I'm running into farm issue. When I render just with my machine, every thing is beautiful. When I turn on distributed Rendering I run into bucket issues:

I'm also getting a error message. See attachments.

[Morbid Angel]

so a few questions - does the DR machine(s) have access to those drives? Can you open the scene on the dr machine / max and see if it can read everything and go from there. Also make sure all of them have same vray version etc.

[vjaramillo]

Yes...all our assets are located on a server on the network. Nothing is done locally. All machines have the same version of MAX, Vray and Forest Pack. Here is another example using Progressive with Denoiser with DR on. As you can see I'm getting ghost trees and missing geometry. The second one is with DR turned off.

[Morbid Angel]

so next question would be what kind of server is it? linux, windows? how many machines are accessing it?

[vjaramillo]

Windows 10...I have 7 dedicated render nodes.

[Morbid Angel]

did you try to open a scene on a slave machine in max? any errors?

[ivan.slavchev]

How are the render spawners on the render nodes started? Manually or as a service? If they run as services - which account do they use? Should be an account with permissions to access the shared location where the assets are stored (by default the spawners run with Local system account unless specified otherwise). Also - how are the assets added - UNC paths or from mapped drives?

[vjaramillo]

The render nodes are running spawner as a service under the local system account. Assets are added using mapped drives.

[Morbid Angel]

so service if its not logged in won't map the drive if I recall correctly. Could you try one machine where its running a spawner when logged in to user account.

[vjaramillo]

We fixed the issue. We decided to run manually since we use mapped drives. I was launching the old spawner before. Once I launch the 2019 spawner all issues are resolved. Thanks for the help.