AWS Thinkbox Discussion Forums

Unable to renumber frames using Vray/Maya

Hi
We are facing an issue here with Deadline 9.0
We are using Maya 2016 and Vray 3.52 and Deadline 9.0 on Centos 7.
we have a simulation that starts at frame ’ -15’ and ends at frame 150.
we want to render it with frame number starting at 1001.
when we use ‘Renumber frames’ in common render settings tab and also check ‘Frame Number offest’ in Deadline submission script.
It doesnt work. the renders fail giving an error .
I am copying the log report below here


=======================================================
Error

Error: Renderer returned non-zero error code 204. Check the renderer’s output.
at Deadline.Plugins.PluginWrapper.RenderTasks (System.String taskId, System.Int32 startFrame, System.Int32 endFrame, System.String& outMessage, FranticX.Processes.ManagedProcess+AbortLevel& abortLevel) [0x002bc] in <048acd89fd9548cb898cdcdf52a91e73>:0

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.SandboxedPlugin.a (Deadline.Net.DeadlineMessage A_0) [0x0021c] in <048acd89fd9548cb898cdcdf52a91e73>:0
at Deadline.Plugins.SandboxedPlugin.RenderTask (System.String taskId, System.Int32 startFrame, System.Int32 endFrame) [0x000b5] in <048acd89fd9548cb898cdcdf52a91e73>:0
at Deadline.Slaves.SlaveRenderThread.a (Deadline.IO.TaskLogWriter A_0) [0x00734] in <048acd89fd9548cb898cdcdf52a91e73>:0

=======================================================
Log

2017-08-03 14:41:50: 0: Loading Job’s Plugin timeout is Disabled
2017-08-03 14:41:51: 0: Executing plugin command of type ‘Sync Files for Job’
2017-08-03 14:41:51: 0: All job files are already synchronized
2017-08-03 14:41:51: 0: Synchronizing Plugin MayaCmd from /media/CX_VFX/_DeadlineRepo/plugins/MayaCmd took: 0 seconds
2017-08-03 14:41:51: 0: Done executing plugin command of type ‘Sync Files for Job’
2017-08-03 14:41:51: 0: Executing plugin command of type ‘Initialize Plugin’
2017-08-03 14:41:51: 0: INFO: Executing plugin script ‘/tmp/Thinkbox/Deadline9/chromatix/slave/blade_08/plugins/59831a0d5047de7b9a1f7fd8/MayaCmd.py’
2017-08-03 14:41:52: 0: INFO: About: Maya Cmd Plugin for Deadline
2017-08-03 14:41:52: 0: INFO: Render Job As User disabled, running as current user ‘chromatix’
2017-08-03 14:41:52: 0: INFO: The job’s environment will be merged with the current environment before rendering
2017-08-03 14:41:52: 0: Done executing plugin command of type ‘Initialize Plugin’
2017-08-03 14:41:52: 0: Start Job timeout is disabled.
2017-08-03 14:41:52: 0: Task timeout is disabled.
2017-08-03 14:41:52: 0: Loaded job: PDi_OLD_v15 - Smoke - persp (59831a0d5047de7b9a1f7fd8)
2017-08-03 14:41:52: 0: Executing plugin command of type ‘Start Job’
2017-08-03 14:41:52: 0: Done executing plugin command of type ‘Start Job’
2017-08-03 14:41:52: 0: Plugin rendering frame(s): 1
2017-08-03 14:41:52: 0: Executing plugin command of type ‘Render Task’
2017-08-03 14:41:52: 0: INFO: Setting MAYA_DEBUG_ENABLE_CRASH_REPORTING environment variable to 0 for this session. Set to 1 if you need Maya debug log
2017-08-03 14:41:52: 0: INFO: Setting MAYA_DISABLE_CIP (ADSK Customer Involvement Program) environment variable to 1 for this session
2017-08-03 14:41:52: 0: INFO: Setting MAYA_DISABLE_CER (ADSK Customer Error Reporting) environment variable to 1 for this session
2017-08-03 14:41:52: 0: INFO: Setting MAYA_DISABLE_CLIC_IPM (ADSK In Product Messaging) environment variable to 1 for this session
2017-08-03 14:41:52: 0: INFO: Setting MAYA_OPENCL_IGNORE_DRIVER_VERSION environment variable to 1 for this session
2017-08-03 14:41:52: 0: INFO: Setting MAYA_VP2_DEVICE_OVERRIDE environment variable to VirtualDeviceDx11 for this session
2017-08-03 14:41:52: 0: INFO: Performing path mapping on ma scene file
2017-08-03 14:41:53: 0: INFO: Stdout Redirection Enabled: True
2017-08-03 14:41:53: 0: INFO: Asynchronous Stdout Enabled: False
2017-08-03 14:41:53: 0: INFO: Stdout Handling Enabled: True
2017-08-03 14:41:53: 0: INFO: Popup Handling Enabled: True
2017-08-03 14:41:53: 0: INFO: QT Popup Handling Enabled: False
2017-08-03 14:41:53: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2017-08-03 14:41:53: 0: INFO: Using Process Tree: True
2017-08-03 14:41:53: 0: INFO: Hiding DOS Window: True
2017-08-03 14:41:53: 0: INFO: Creating New Console: False
2017-08-03 14:41:53: 0: INFO: Running as user: chromatix
2017-08-03 14:41:53: 0: INFO: Rendering with Maya version 2016.0
2017-08-03 14:41:53: 0: INFO: Not enforcing a build of Maya
2017-08-03 14:41:53: 0: INFO: Executable: “/usr/autodesk/maya2016/bin/Render”
2017-08-03 14:41:53: 0: INFO: Rendering to network drive
2017-08-03 14:41:53: 0: INFO: Rendering with VRay.
2017-08-03 14:41:53: 0: INFO: Argument: -r vray -threads 0 -x 1920 -y 1080 -rl Smoke -s 1 -e 1 -b 1 -rfs 1002 -rd “/media/CX_VFX/Der_Zauberlehrling_VFX/SEQ/ASSETS/RENDERS” -im “/_v/_v” -cam “persp” -proj “/media/CX_VFX/Der_Zauberlehrling_VFX/SEQ/ASSETS/MODEL/PROPS/PREV” “/tmp/Thinkbox/Deadline9/chromatix/slave/blade_08/jobsData/59831a0d5047de7b9a1f7fd8/thread0_tempn5Rwf0/PDi_OLD_v15.ma”
2017-08-03 14:41:53: 0: INFO: Full Command: “/usr/autodesk/maya2016/bin/Render” -r vray -threads 0 -x 1920 -y 1080 -rl Smoke -s 1 -e 1 -b 1 -rfs 1002 -rd “/media/CX_VFX/Der_Zauberlehrling_VFX/SEQ/ASSETS/RENDERS” -im “/_v/_v” -cam “persp” -proj “/media/CX_VFX/Der_Zauberlehrling_VFX/SEQ/ASSETS/MODEL/PROPS/PREV” “/tmp/Thinkbox/Deadline9/chromatix/slave/blade_08/jobsData/59831a0d5047de7b9a1f7fd8/thread0_tempn5Rwf0/PDi_OLD_v15.ma”
2017-08-03 14:41:53: 0: INFO: Startup Directory: “/usr/autodesk/maya2016/bin”
2017-08-03 14:41:53: 0: INFO: Process Priority: BelowNormal
2017-08-03 14:41:53: 0: INFO: Process Affinity: default
2017-08-03 14:41:53: 0: INFO: Process is now running
2017-08-03 14:41:53: 0: STDOUT: Usage: /usr/autodesk/maya2016/bin/Render [options] filename
2017-08-03 14:41:53: 0: STDOUT: where “filename” is a Maya ASCII or a Maya binary file.
2017-08-03 14:41:53: 0: STDOUT: Common options:
2017-08-03 14:41:53: 0: STDOUT: -help Print help
2017-08-03 14:41:53: 0: STDOUT: -test Print Mel commands but do not execute them
2017-08-03 14:41:53: 0: STDOUT: -verb Print Mel commands before they are executed
2017-08-03 14:41:53: 0: STDOUT: -keepMel Keep the temporary Mel file
2017-08-03 14:41:53: 0: STDOUT: -listRenderers List all available renderers
2017-08-03 14:41:53: 0: STDOUT: -renderer string Use this specific renderer
2017-08-03 14:41:53: 0: STDOUT: -r string Same as -renderer
2017-08-03 14:41:53: 0: STDOUT: -proj string Use this Maya project to load the file
2017-08-03 14:41:53: 0: STDOUT: -log string Save output into the given file
2017-08-03 14:41:53: 0: STDOUT: Specific options for renderer “vray”: V-Ray for Maya renderer
2017-08-03 14:41:53: 0: STDOUT: All purpose flags:
2017-08-03 14:41:53: 0: STDOUT: -exportFileName string
2017-08-03 14:41:53: 0: STDOUT: Use this to force exporting to a .vrscene file with the
2017-08-03 14:41:53: 0: STDOUT: given name. Example:
2017-08-03 14:41:53: 0: STDOUT: Render -r vray -exportFileName “c:/1.vrscene”
2017-08-03 14:41:53: 0: STDOUT: -noRender
2017-08-03 14:41:53: 0: STDOUT: filename
2017-08-03 14:41:53: 0: STDOUT: -noRender
2017-08-03 14:41:53: 0: STDOUT: Use this to disable rendering.
2017-08-03 14:41:53: 0: STDOUT: Usually it is used with -exportFileName to produce a
2017-08-03 14:41:53: 0: STDOUT: .vrscene file. Example:
2017-08-03 14:41:53: 0: STDOUT: Render -r vray -exportFileName “c:/1.vrscene”
2017-08-03 14:41:53: 0: STDOUT: -noRender
2017-08-03 14:41:53: 0: STDOUT: filename
2017-08-03 14:41:53: 0: STDOUT: -exportSeparate
2017-08-03 14:41:53: 0: STDOUT: Use this to export to separate .vrscene files. Example:
2017-08-03 14:41:53: 0: STDOUT: Render -r vray -exportFileName “c:/1.vrscene”
2017-08-03 14:41:53: 0: STDOUT: -noRender
2017-08-03 14:41:53: 0: STDOUT: -exportSeparate
2017-08-03 14:41:53: 0: STDOUT: filename
2017-08-03 14:41:53: 0: STDOUT: -exportCompressed
2017-08-03 14:41:53: 0: STDOUT: Use this to export to compressed .vrscene file (still
2017-08-03 14:41:53: 0: STDOUT: experimental). Example:
2017-08-03 14:41:53: 0: STDOUT: Render -r vray -exportFileName “c:/1.vrscene”
2017-08-03 14:41:53: 0: STDOUT: -noRender
2017-08-03 14:41:53: 0: STDOUT: -exportCompressed
2017-08-03 14:41:53: 0: STDOUT: filename
2017-08-03 14:41:53: 0: STDOUT: -exportFramesSeparate Use this to export each frame to separate file.
2017-08-03 14:41:53: 0: STDOUT: -exportSpecific string
2017-08-03 14:41:53: 0: STDOUT: Use this to restrict the exporter to a list of (DAG) nodes. Example:
2017-08-03 14:41:53: 0: STDOUT: Render -r vray -exportSpecific “pSphereShape1 pSphereShape2 pPlane1” filename
2017-08-03 14:41:53: 0: STDOUT: General purpose flags:
2017-08-03 14:41:53: 0: STDOUT: -rd path Directory in which to store image file
2017-08-03 14:41:53: 0: STDOUT: -of string Output image file format. See the Render Settings window to find available formats
2017-08-03 14:41:53: 0: STDOUT: -im filename Image file output name
2017-08-03 14:41:53: 0: STDOUT: -rep boolean Replace or not the rendered image if it already exists (-rep true/false)
2017-08-03 14:41:53: 0: STDOUT: Frame numbering options
2017-08-03 14:41:53: 0: STDOUT: -s float Starting frame for an animation sequence
2017-08-03 14:41:53: 0: STDOUT: -e float End frame for an animation sequence
2017-08-03 14:41:53: 0: STDOUT: -b float By frame (or step) for an animation sequence
2017-08-03 14:41:53: 0: STDOUT: -pad int Number of digits for the frame number in the output image file name
2017-08-03 14:41:53: 0: STDOUT: Camera options
2017-08-03 14:41:53: 0: STDOUT: -cam name Specify which camera to be rendered
2017-08-03 14:41:53: 0: STDOUT: -iip Ignore image planes when rendering
2017-08-03 14:41:53: 0: STDOUT: Bake rendering
2017-08-03 14:41:53: 0: STDOUT: -bake_node name Specify object to bake render
2017-08-03 14:41:53: 0: STDOUT: -bake_map name Which UV set to use
2017-08-03 14:41:53: 0: STDOUT: -bake_padding float Edge padding in pixels
2017-08-03 14:41:53: 0: STDOUT: Resolution options
2017-08-03 14:41:53: 0: STDOUT: -reg int int int int Set sub-region pixel boundary of the final image:
2017-08-03 14:41:53: 0: STDOUT: left, right, bottom, top
2017-08-03 14:41:53: 0: STDOUT: -x int Set X resolution of the final image
2017-08-03 14:41:53: 0: STDOUT: -y int Set Y resolution of the final image
2017-08-03 14:41:53: 0: STDOUT: -par float Pixel Aspect Ratio for the rendered image
2017-08-03 14:41:53: 0: STDOUT: System options
2017-08-03 14:41:53: 0: STDOUT: -threads int Specify how many render threads to use (0-auto)
2017-08-03 14:41:53: 0: STDOUT: Render Layers and Passes:
2017-08-03 14:41:53: 0: STDOUT: -rl boolean|name(s) Render each render layer separately
2017-08-03 14:41:53: 0: STDOUT: Mel callbacks
2017-08-03 14:41:53: 0: STDOUT: -preRender string Mel code executed before rendering
2017-08-03 14:41:53: 0: STDOUT: -postRender string Mel code executed after rendering
2017-08-03 14:41:53: 0: STDOUT: -preLayer string Mel code executed before each render layer
2017-08-03 14:41:53: 0: STDOUT: -postLayer string Mel code executed after each render layer
2017-08-03 14:41:53: 0: STDOUT: -preFrame string Mel code executed before each frame
2017-08-03 14:41:53: 0: STDOUT: -postFrame string Mel code executed after each frame
2017-08-03 14:41:53: 0: STDOUT: *** Remember to place a space between option flags and their arguments. ***
2017-08-03 14:41:53: 0: STDOUT: Any boolean flag will take the following values as TRUE: on, yes, true, or 1.
2017-08-03 14:41:53: 0: STDOUT: Any boolean flag will take the following values as FALSE: off, no, false, or 0.
2017-08-03 14:41:53: 0: STDOUT: Examples:
2017-08-03 14:41:53: 0: STDOUT: render -r vray -cam persp -s 1 -e 10 -x 512 -y 512 scene_x.mb
2017-08-03 14:41:53: 0: STDOUT: render -r vray -cam persp -threads 1 -bake_node pCone1 -bake_map map1 scene_x.mb
2017-08-03 14:41:53: 0: STDOUT: Invalid flag: -rfs
2017-08-03 14:41:53: 0: INFO: Process exit code: 204
2017-08-03 14:41:53: 0: Done executing plugin command of type ‘Render Task’

=======================================================
Details

Date: 08/03/2017 14:41:56
Frames: 1
Elapsed Time: 00:00:00:06
Job Submit Date: 08/03/2017 14:41:49
Job User: kishore
Average RAM Usage: 1464516608 (3%)
Peak RAM Usage: 1467994112 (3%)
Average CPU Usage: 3%
Peak CPU Usage: 4%
Used CPU Clocks (x10^6 cycles): 6175
Total CPU Clocks (x10^6 cycles): 205818

=======================================================
Slave Information

Slave Name: BLADE_08
Version: v9.0.1.1 Release (16886394d)
Operating System: Linux
Machine User: chromatix
IP Address: 10.0.10.158
MAC Address: FF:FF:FF:FF:FF:FF
CPU Architecture: x86_64
CPUs: 32
CPU Usage: 2%
Memory Usage: 1.3 GB / 62.7 GB (2%)
Free Disk Space: 793.733 GB
Video Card: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)


Could you guys please help us in finding a solution for this, else we have to rename the frames using batch renamers which is quite a work for us, considering the passes and iterations we have to do.

Regards
Kishore

Actually, I had a call a similar call about this with Redshift yesterday but that dealt with render layer overrides of frame numbers.

The problem with Maya’s frame renumbering in the ‘common’ render settings tab is that every instance of Maya starts renumbering from the same point, regardless of which frame we asked it to start from. That becomes a problem because each Slave will start at a different point in the timeline but count from the same start for the file name. Example:

Task 0: 00-09, this Maya starts numbering files at 0 but frame contents are for frame 01
Task 1: 10-19, this Maya starts numbering files at 0 but frame contents are for frame 10
Task 2: 20-29, this Maya starts numbering files at 0 but frame contents are for frame 20

Because this is a sim and will be running on only one machine, it’s probably fine, but for others reading this thread later it’ll be important. This may have changed since I had my last call about it with Maya 2014, but give it a try with a test cube and a positive number.

Now, the actual problem here is that we’re feeding a flag named “-rfs” into Render and it has no idea what we’re talking about. It seems they deprecated that flag since Maya 7.0 seems to have supported it:
tokeru.com/t/bin/view/Maya/M … derOptions

To work around that, try disabling Deadline’s renumbering since it won’t work here or try MayaBatch in case there’s some melscript equivalent.

Hi Edwin,
Thanks for the reply.
I understand what you mean, the ‘-rfs’ flag works if we are using either Mental ray or software renderer. But sadly that wont be of help for us.
What I did was

  1. like you said, by disabling the Deadline renumbering and enabling ‘Renumber Frames’ in Vray Common render settings.
    However this renders only one frame on the farm, as every task overwrites the other when it starts renumbering.
  2. So I increased the ‘Frames per task’ to 45 ( the length of the shot) in the Deadline submission script, while this works but then
    the job is only handled by one blade, which isnt really that helpful.

Edit: A workaround we found is to offset the start of RBD simulation cache which took quiet a while, but works.

Are you able to distribute a simulation across multiple machines effectively? I’ve only seen something like that in Houdini with partitions. Usually for Fume, ReadFlow, and friends you’re going to be more efficient restraining the sim to one box to write out the data, then rendering across many with the cache.

Glad you made it through that one. I’m wondering what happens with file naming once things go negative. I’ve been thinking about how we might just do the renumbering for you if we do local rendering or similar.

Privacy | Site terms | Cookie preferences