I have T4 running in macOS nicely. Also, in Windows, which is my primary platform. I have Deadline 10.1 setup and it's able to find everything and que up jobs. Deadline has a PATHS setting so that Linux, Mac, can know how to interpret a Windows file path. i.e. "P:\" becomes "/Volumes/Production/"
That works and Deadline is able to find the share and load the Terragen file. The issue I am having is Terragen's render output path. It's hard coded to the Windows share location. "P:\xxxxx..." So of course macOS Terragen has no idea what that is.
Is there a solution for this? Do I need to save my frame outputs in Terragen a different way to be Windows and macOS friendly? I create all my Terragen jobs on my Windows PC. This macOS is just an experiment to see if it was viable.
My guess this is a failure of Deadline intercepting and converting the requested path to a macOS friendly path. As it did successfully for the loading of the Terragen file. Other render controllers allow for work-arounds when explicit paths are written in to program outputs. They do this, generally, by forcing you to use UNC paths when creating content. Then you configure their PATHS swapper to make it all work. Deadline seems to lack that.