DR Frustration - HELP!

[flino2004]

probably you are using vista home edition....there are some restrictions i think
(5 computers is the maximum searching the same folder at the same time)

[glorybound]

vista

No, I am using VISTA Ultimate

[glorybound]

Vista

I ran the scene on a Windows XP 64 workstation and it is also dropping all the slaves on a more complex scene so it isn't a Vista issue.

[voltron7]

I am using Vista Ultimate, too, and this is what fixed my DR...
http://www.chaosgroup.com/forums/vbu...ad.php?t=45536

It was just a permissions problem, ever since, my DR has been working 100%.
Best luck

[glorybound]

Mapping

All my machines are using the same network username and password and they are all mapped to the save network drive. I did copy all my maps and proxies locally, to each machines, and it might be working. If this is what it takes to make this work then something is just wrong.

[voltron7]

This sounds literally like what I had going on...if I copied everything to each slave, it worked, but clearly this was not a good work flow, so i fixed how my network drives were shared. (Not talking about logging on when the machine boots, up, but when you map/connect to a network drive, you can choose which user at that point, too.) Since i did this, i don't have to copy anything to the slaves anymore...

[glorybound]

did you have a network log in that you used for each machine? Did you log in locally and connect that way?

[voltron7]

did you have a network log in that you used for each machine? Did you log in locally and connect that way?

I was logged into the slave as admin, and logged into the WS as admin, too.
Then, on the slave, I did "map network drive" and in that Dialog box I chose connect using a different user name... At this point I chose the admin account from the drop-down list that appeared.

[glorybound]

log in

But were you logging in locally as an admin or under a domain? Currently I log in under our domain, with my network user name and password, with administrative privileges. I would try locally, but I don't have the local admin information.

[voltron7]

My network is just a simple local workgroup not using a domain.

[glorybound]

Domains

OK, that helps. I was getting it to work with all my textures local on each slave, but I just stopped/started the scene and not it is failing to connect again. I restarted the spawner and I'l see if it works again. if not I'll get the local admin info and try that. Are you running as a service?

[voltron7]

not running as a service, i just star it and let V-ray restart spawners at render end/cancel.

[glorybound]

DR

OK... my conclusions.

I am logged in locally, as an administrator, on all slaves and master. I have the same user name and password for all machines. I have all machines mapped to a network drive and I am accessing that network drive using the same credentials. If I run the DR Spawner manually it drops the slaves and if I run DR Spawner as a Service it finds the slaves, but drops the texture maps and proxies. I copied all the textures to all machines local drives using the same naming convention, but it still renders black buckets.

[voltron7]

Hmmm...yuck.
If you look at vraylog.txt on a slave, you might see some info about the issue. Good luck, man

[simmsimaging]

I wondering if you are actually using UNC paths properly - that is what I had to switch to in order to get around the random black bucket problem (although sometimes it still happens if I run to many back-to-back renders to quickly).

You mention a mapped network drive here and there so thought maybe you are still using that approach.

Just check that ALL the maps and assets in your scene are setup through the network and make sure there is no drive letter shortcut. I often make the mistake of doing some of them with a local path letter, because the shared drive that has all my texmaps is also a local drive for me.

It was not clear before in the earlier posts: do you know how to assign them via unc rather than mapped drive?

b