AWS Thinkbox Discussion Forums

Maxwell multi layered EXR Deadline 6.1.53441 (Beta 9)

Hi guys,

while working with our Deadline render farm (four blades plus a few workstations OSX/LINUX/WINDOWS)
we noticed an issue when generating multi EXR files via Maxwell render.

At this time it is not possible to generate a multi layered EXR file in Maxwell using the Deadline pipeline
all the generated files come out separated except we define a output path adding an explicit .exr
suffix to the file name. For example only a multi layered EXR file will come out of if we set
the output name to example.exr without the suffix no layered file will be produced.

As long as we are rendering still images everything is fine since we know what to do to render
a layered file. But when we are rendering animation sequences this workaround does not work anymore.
Instead of producing an image sequence of layered EXR files only one multi EXR files generated and
will be overwritten by the next latest rendered frame. No sequence/frame tags are written in the
file name anymore, so there is no animation sequence at all :frowning:

Another thing we noticed: Deadline slave provides a wrong cpu information (Linux and Windows). For example
it recognizes a 1,2 GhZ cpu instead of a 3,1 GhZ.

Find a log file and a screenshot of our render settings attached (for the multi EXR issue).
We would very appreciate it if you could help us with any of these things.

Thank you, best regards

flip2013
log.txt (10.2 KB)

Based on the log, it doesn’t look like Deadline is doing anything that would explicitly cause this behavior. There aren’t any arguments being passed in the command line that are overriding the output, and I’m seeing this in the log:

If you run the following command from a command prompt on one of your render nodes, are the results the same?

"C:\Program Files\Next Limit\Maxwell 2\maxwell.exe" -mxs:"R:\EXR_TEST\Windows\EXR_TEST.mxs" -nowait -hide -threads:0 -sampling:10.0 -node -verbose:4 

If they are, then it sounds like this is a more general Maxwell issue. Have you contacted Next Limit at all about this problem?

Cheers,

  • Ryan
Privacy | Site terms | Cookie preferences