Major DR problem - pls HELP

[PIXELBOX_SRO]

Hi guys,
i came to work today to check on my workstation and found out that some of the DR buckets render with slightly different light intensity (gamma/exposure).
We have 6 nodes in our office.

i ran a region again with a VrayDRBucket pass.......and surprisingly, its my workstation where i started the DR from!!!

i think its got something to do with IES light.

how can this be? my comp is not sending me any errors of missing files or anything....

can this be a bug?

has anyone encountered this b4?

THANKS FOR ANY HELP!!!
DEADLINE COMING

Best Regards

[simmsimaging]

It's happened to me before. Restarting the workstation and all the nodes fixes it most of the time.

[Morne]

I find this happens if your path to the IES is a mapped network drive instead of a UNC path
even if all machines has access to the mapped drive, I find it better to ALWAYS use UNC paths

[PIXELBOX_SRO]

how do i force the node to use UNC path???
i dont have access to MAX on them as its only installed for rendering purposes...

[Morne]

you dont do anything with the nodes. In your scene on your workstation make sure it is using a UNC path. All your paths are copied as is to nodes.
So if in max you see a path of c:\maps\myies.ies then that actual file must be copied on ALL nodes to that path on each local drive
However if you see in max on your workstation it says someting like H:\myserver\maps\myies.ies then that is more than likely a mapped network drive and the drive must be mapped on all nodes (mapped using windows explorer - mapping drives has nothing to do with max)

However as I mentioned I've had problems in the past with mapped network drives especially with ies files.
so a better option to use is UNC paths which is a direct path to the file (not using mapped drives) so it will be something like \\myserver\maps\myies.ies or even an ip address \\10.0.0.1\mymaps\myies.ies

hope that helps

[PIXELBOX_SRO]

Thanks for the help guys, will definitelly try it.

all my nodes have same letters assigned to the mapped drives...its really weird the way max handles this issue.