Network render: Issue w/ texture paths

Network render: Issue w/ texture paths#347102

By monochrome - Wed Sep 14, 2011 5:12 pm

- Wed Sep 14, 2011 5:12 pm #347102

I'm trying to use another node on our network. I get failures coming from texture paths missing, even though everything is linked correctly and I get single node renders w/o error.

All of my textures are kept in the 'S' drive on the server and the model is on the 'P' drive.

Re: Network render: Issue w/ texture paths#347103

By monochrome - Wed Sep 14, 2011 5:13 pm

- Wed Sep 14, 2011 5:13 pm #347103

Re: Network render: Issue w/ texture paths#347106

By JDHill - Wed Sep 14, 2011 5:23 pm

- Wed Sep 14, 2011 5:23 pm #347106

I'm not sure this is something the plugin can help you with. You could try disabling Pack and Go in the plugin, in order to see if, on your configuration, the network system likes absolute paths better than the relative ones you get with Pack and Go.

Next Limit Team

Re: Network render: Issue w/ texture paths#347109

By monochrome - Wed Sep 14, 2011 5:56 pm

- Wed Sep 14, 2011 5:56 pm #347109

Wow, that was easy. I didn't realize pack-and-go was the conflict. I am now successfully rendering across the network. Thanks!

Re: Network render: Issue w/ texture paths#347110

By JDHill - Wed Sep 14, 2011 6:01 pm

- Wed Sep 14, 2011 6:01 pm #347110

Well really, the Pack and Go way should be superior, since it doesn't tie the scene to any specific location -- Maxwell network should be finding your files in the /textures directory. But thanks for confirming that it affects the behavior.

Next Limit Team