Rendering Cross platform

#2

The queue manager doesn’t matter that much. There are a few ways you could do it, like use environment variables to define the root path of the project that get set at the beginning of the job, then use only relative file paths in the scenes. Or a script could run when the applications starts that looks for file paths and changes them according to the platform it’s running on.

On the Mac side look into autofs so the mounts are there every time and the users don’t have to manually mount the network shares. You can pick where to mount stuff and/or make symbolic links to shorten the path the users have to deal with like “/data” instead of “/Volumes/production/data” (or whatever your structure happens to look like).

https://ssl.apple.com/business/docs/Autofs.pdf

#3

I read that you need to set a unified render path by on MAC creating a file “Render” in the /etc/paths.d/ directory.

So then if you submit the render through the “create backburner job” and add “Render” in the Renderer path parameter it will point to the correct location on the respective platform (MAC/WINDOWS)

Where do you put the equivalent “Render” file in windows though?

#4

Heya olson

thing is I dont want the network locations to auto mount, I want the user to input his/her respective username and password.

All I want it to do is instead of mounting it as a AFP: path (e.g. afp://Volumes/whatever)
I need it to mount as SMB: path (e.g. smb://whatever)

have noticed now that if I try setting the project file in maya, it automatically tries to mount as /volumes.

#5

You can add stuff to the path in Windows like this, happened to be the first Google result so there might be other guides out there that explain it better.

http://www.computerhope.com/issues/ch000549.htm#0

#6

Autofs can be tied into the domain or whatever user accounts you want. If you don’t want to change where it mounts (which you can) then you can setup symbolic links wherever you want to link back to the mount.

#7

just throwing this out there, not trying to confuse the situation but windows doesn’t use the POSIX pathing methods but rather UNC convention… so if you find a POSIX style utility you may be able to correctly do the pathing in one method that works well across all platforms. Perhaps Cygwin?

#8

Windows does have a path, it’s not just as obvious and it has some quirks. Cygwin works if you want bash or other Unix like utilities (rsync, sed, etc.), but that doesn’t matter in this case for rendering.

#9

perhaps I mis-understood the issue, but doesn’t this boil down to the configuration file that gets passed between the systems… and since they reference the network storage differently (POSIX style versus UNC), it could be causing a problem for him?

so, if this is the case… you could enable POSIX style pathing support on the windows backburner controller so when it parsed the config file logic it would understand the references?

#10

The directory referred to above on OS X (/etc/paths.d) holds files that add to the path. I think we’re using the term path differently.

https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man8/path_helper.8.html

Windows has an equivalent feature that I linked to earlier.

#11

I tried adding that to the Path settings olson and it doesn’t seem to work…

what its supposed to do is if I open cmd and type render… it should in essence start the render.exe in c:\Program Files\Autodesk\Maya2014\bin\

but it just returns a “‘render.exe’ is not recognized as an internal or external command,
operable program or batch file.”

we are supposed to be running on a UNC based setup, if i understand it all correctly

#12

Double check the path variable and the path for the render.exe, also restart or logout because the changes won’t affect the current session.

#13

restarted my machine, still didnt work

#14

The syntax is probably wrong for the path variable. Can you copy and paste what you have entered for the path variable?

#15

I mix Linux/OS X and Windows with V-Ray for Maya – the recent nightly builds added automatic transfer of assets on the back end so you don’t have to worry about sharing identical paths. I don’t know what renderer you’re using but if it’s V-Ray, you should look into the nightly builds

if you’re just looking for a simple way to add the render command to the OS X terminal, I wrote this a while ago:

http://polygonspixelsandpaint.tumblr.com/post/701899285

But maybe you’re looking to do it for all users, so olson’s method seems more global.

#16

under System Variables
under the “Path” variable the value is set to:
C:\Program Files (x86)\Mozilla Firefox;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Common Files\Autodesk Shared;C:\Program Files\Common Files\Autodesk Shared;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\3DPaintBrush;C:\Program Files (x86)\QuickTime\QTSystem;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Autodesk\Backburner;C:/Program Files/Autodesk/Maya2014/bin/Render

#17

The slashes go the other way on the last item, backslash instead of forward. Not sure if that would prevent it from working but it’s worth trying out.

#18

wow… thats rather blind of me O_O
i will change it and give it a try

#19

ok, seem to have the path variable working, BUT seem to have another odd issue relating to it.

All servers are set with the same path variable so if I run “cmd” and type in “render” it says “missing file name” which I understand as being correct.

now… if I submit the backburner job with “render” in the in the “Render Path” setting it doesn’t seem to work. It just gives a “CmdJob adapter: Create Cmdjob process error: 2”

if I change the path back to “c:\Program Files\Autodesk\Maya2014\bin\render.exe” it seems to submit it fine.

(this is only on the windows machines right now, but if it doesn’t work like this I doubt its going to do any different from OSX)

#20

I’ve never used Backburner but if it’s anything like other queue managers it will have very detailed logs of exactly what happened. The summary of “error: 2” doesn’t mean anything to anyone except for Backburner developers or gurus.

#21

actually, the setup is completely different for OS X/Linux. See my linked article. Just type this in the terminal, and you’ll be up and running in OS X:

echo "PATH=\$PATH:/Applications/Autodesk/maya2014/Maya.app/Contents/MacOS/" >> ~/.bash_profile
source ~/.bash_profile

for Linux it would be:

echo "PATH=\$PATH:/usr/autodesk/maya2014-x64/bin/" >> ~/.bash_profile
source ~/.bash_profile