Why

[WWX]

Decided to test 1.5RC2 DR with an old scene and still experiencing the same problem, the other machines does not render all the textures.

My network is setup so on all machines the drive which host the texture files has the same letter, for example drive T. And this is what I end up with.

Also tried the option of copying the texture files to the local hard drives of each render slaves, configure Max Paths on each machine, but still this is the resulted image.



Totally baffels me, please help.

[jaggos]

you have a network issue and not Vray, you need to map your network drivers. in each machine map the driver where your textures are and also on your workstation and when you import the texture to max import them through the mapped driver and not directly from the local drivers. so max can have the full path and when the rest of the machines have the same mapped drivers it will work.
to map a driver
go to windows explorer and click on tools then choose map network drivers.

[WWX]

Thanks for the reply, but I think my network is setup correctly as you describe.

I have one computer with a shared folder in which all the textures sit. this folder is mapped and accessible from all the render slave i.e. i can copy files from this folder ontop any of the slaves and vice versa. Max on all the salves is also configured to look at this location for the textures.

The only reason i also copied the texture files on to the local drives of the slaves is because it was once suggested that the reason for this problem was that sometimes the texture file is not read quick enough over the network.

In case you wondered, i also configure Max to look at the location of where the texture files are located on the slaves local drives.

[calvino56]

Try copying your 3dsmax.ini file into each of the slaves 3dsMax directory.
Hope that helps.

[Clifton Santiago]

I assume this is with DR? I get this sometimes. Try stopping and re-starting your Vray spawner service on each render node, and try again.

[WWX]

Will try these options - thanks

[nvanherpt]

i set my bitmap paths through network places instead of drive letters, always fixes this for me.

eg:

\\servername\

instead of

G:\

[jaggos]

What version of backburner you using, when DR is Working it uses the backbburner to lunch the spawner or something I can remember what exatcly. if you have the lates that comes with MAX8 I remember there was a problem with it, try using the previous. and see if it works.

[DaForce]

yeah, DEFINITLY use UNC paths not drive letters.. will often be the cause for this problem.

UNC paths is like what nvanherpt showed.
\\SERVERNAME\SHAREDFOLDER

[dominiquelaksmana]

i just set up my dr also for 4 days. 2 first days, it worked fine. the next two days, it does something like what wwx experienced. i have to cancel render, and render again, and there it is. so i guess can't do walkthrough.. since it is like that.. ps : i have all the maps in each computer.

[WWX]

just to clarify I am using UNC path system.

[DaForce]

so your definitly not using drive letters in your bitmap paths?

[WWX]

Hi Da Force, if refering to the way my setup looks inside of MAX path configuration, yes i don't use drive letters - just busy with some morning tasks and then would get some screen captures.

The drive letter example i used, was to explain that when i mapped the shared folder in Windows, I used the same drive letter on all machines - hope that made sense.

And so if you ask, did I use a drive letter when mapping the folder on the various machine in Windows then the answer would be yes.

Not sure if this is now more confusing than ever before but i post those screen captures soon.