AWS Thinkbox Discussion Forums

Cinema4D / Maya export Redshift Windows > Linux path translation not working

I’m submitting from Cinema4D R19.068 with Redshift 3.0.28 using Deadline 10.1.9.2

Using the Export option in the integrated submitter to locally export RS files in C4D and then render standalone on linux

The job goes through but the submission path stays in Windows so I don’t get the output file.

Does anyone else experience this?

2020-09-30 14:54:35:  0: INFO: Creating New Console: False
2020-09-30 14:54:35:  0: INFO: Running as user: root
2020-09-30 14:54:35:  0: INFO: Executable: "/usr/redshift/bin/redshiftCmdLine"
2020-09-30 14:54:35:  0:  **CheckPathMapping: Swapped "\\ServerName\DeadlineRepository10\_tests\c4d\outpt\c4d_rs_export__Main0000.rs" with "/mnt/DeadlineRepository10\_tests\c4d\outpt\c4d_rs_export__Main0000.rs"**
2020-09-30 14:54:35:  0: INFO: Argument: "/mnt/DeadlineRepository10/_tests/c4d/outpt/c4d_rs_export__Main0000.rs"
2020-09-30 14:54:35:  0: INFO: Full Command: "/usr/redshift/bin/redshiftCmdLine" "/mnt/DeadlineRepository10/_tests/c4d/outpt/c4d_rs_export__Main0000.rs"
2020-09-30 14:54:35:  0: INFO: Startup Directory: "/usr/redshift/bin"
2020-09-30 14:54:35:  0: INFO: Process Priority: BelowNormal
2020-09-30 14:54:35:  0: INFO: Process Affinity: default
2020-09-30 14:54:35:  0: INFO: Process is now running
2020-09-30 14:54:38:  0: STDOUT: Redshift Command-Line Renderer (version 3.0.28 - API: 3023)

Shows it works, but… when saving it reverts back to the Windows path???

2020-09-30 14:54:43:  0: STDOUT: Primitive loading time:                        66ms
2020-09-30 14:54:43:  0: STDOUT: Tess/Disp time:                                 0ms
**2020-09-30 14:54:43:  0: STDOUT: Saving: //ServerName/DeadlineRepository10/_tests/c4d/outpt/c4d_rs_00_0000.png](//ServerName/DeadlineRepository10/_tests/c4d/outpt/c4d_rs_00_0000.png)**
2020-09-30 14:54:43:  0: STDOUT: Shutdown Rendering Sub-Systems...
2020-09-30 14:54:43:  0: STDOUT: Shutdown mem management thread...

I have a ticket open for this, I got a request to check the
ImageOutputDirectory=[outputDirectory]

I don’t have this in the job only

Blacklist=
EventOptIns=
Frames=0
IsFrameDependent=True
MachineName=PC
Name=r19_rs_00 - Main - Redshift Standalone
OutputDirectory0=\\ServerName\DeadlineRepository10\_tests\c4d\outpt
OutputFilename0=c4d_rs_00_####.png
OverrideTaskExtraInfoNames=False
Plugin=Redshift
Region=
ScheduledStartDateTime=06/10/2020 17:51
UserName=user

just to update I have a working solution from the ticket I have open, just needs a little refinement

But now I’ve discovered Maya is doing the same thing, Houdini however exports and renders no problem!

Can’t believe I’m one of ‘those’ people who leave a thread without showing the found solution!!

I attached the updated py file from @zainali for c4d, I’m not sure if I got a solution for Maya or if this was fixed in a later release (first issue was 10.1.9 and just ran into it again with 10.1.15) I don’t see this in the Release Notes

Here’s the fix for C4D:
SubmitC4DToDeadline.py (183.5 KB)

Here’s the fix for Maya:

This will only be working if the you’re not writing output to multiple directories as -oip (ImageOutputDirectory) overrides all output directories ignoring layers/camera folder structure which could cause file overwrites.

"C:\DeadlineRepository10\submission\Maya\Main\SubmitMayaToDeadline.mel"
PluginInfo is written between line 8364 and 8370fprint $fileId ( "SceneFile=" + $inputPath + "\n" );fprint $fileId ( "WorkingDirectory=" + CheckSlashes( $projectPath ) + "\n" );fprint $fileId ( "Threads=" + `intSliderGrp -q -v frw_redshiftThreads` + "\n" );fprint $fileId ( "CommandLineOptions=" + `textFieldGrp -q -text frw_redshiftArgs` + "\n" );
You can add:fprint $fileId ( "ImageOutputDirectory=" + $outputFilePath + "\n" );

^
Thanks again to Zain for the quick fixes dished out here

Privacy | Site terms | Cookie preferences