Nodes not rendering XRefs

[Macker]

Hey guys, I've got a weird problem here.

I'm rendering from my local machine with distributed rendering, and the nodes aren't picking up the main building that is referenced into the scene - which is in the same folder as the site, that IS rendering correctly. My local machine renders it all fine.

I've restarted my local copy of max, and all of the DR spawners on all of the nodes. Still nothing.

[edit] I've restarted all (three) of the render nodes and only one of them is rendering correctly now, the other two are still doing the same.

[Macker]

When I go into the XRef and render it, all of the render nodes work just fine.

[Dave_Wortley]

Are you using UNC paths or drive letter mapping?

[Macker]

Drive letter mapping - we had some issues with UNC so switched back.

All of the nodes can see all of the drives, and they're all mapped to the exact same letters. Both the scene that I'm rendering from AND the XRef are in the same folder, so clearly the nodes can access it otherwise they wouldn't render the roads/grass etc.

We have network logins which load a group policy every time you log on, so all drives are always mapped to the same letters.

[Dave_Wortley]

If you are running VrayRT as a service it may need to be UNC pathed though.

[Macker]

This isn't RT, this is normal/production VRay.

[Macker]

Fixed:

Because we have max set to use "relative" paths, which works fine with every other asset, for some reason it doesn't with DR/XRefs. Not sure if this is a bug with 3DS max or VRay.

[Dave_Wortley]

Fixed:

Because we have max set to use "relative" paths, which works fine with every other asset, for some reason it doesn't with DR/XRefs. Not sure if this is a bug with 3DS max or VRay.

It's worth reporting to support@chaosgroup.com to see if they can reproduce.

[Zdravko.Keremidchiev]

Thank you for sharing. But this seems to work fine on our side. Which V-Ray version is this?