You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the renderer is specified in display_options={"rendererName": "viewport2"}, with Viewport 2.0 options specified in viewport2_options={}. That is a bit unintuitive. How, for example, would one specify options for hardwarerenderer, or a bespoke renderer?
Make all display options part of one dictionary, and separate rendering option into it's own argument.
The text was updated successfully, but these errors were encountered:
I'm looking into using capture to perform playblasts (or renders?) that use hardware rendering and include the z-depth buffer into the output format. (e.g. in a iff file). I'm curious as to how to get this going. Any ideas?
What's more, I would like a way to Software Render as well, such that playblasts can be made offline and on machines without graphics cards. This sounds like a good step in this direction, as it would change the parameters as significantly as Software Render would (e.g. no HUD).
Maybe we could go the extra mile and actually "reimplement" critical parts of the hud, such as camera name and FPS, in these alternative renders. That might actually make maya-capture offer something other than a wapper to cmds.playblast. A unique value. Lots of studios seem interested in offline playblasts.
As for how to do it, sorry I haven't tried. Have you had a look at whether cmds.playblasts can do it?
Have you had a look at whether cmds.playblasts can do it?
Haven't gotten to something usable with that yet. I'm not sure it can even do hardware of software renders like that. Honestly I haven't investigated it too deeply yet but I'm very interested in the possible solutions.
Goal
Enable specifying which renderer to capture with.
Motivation
At the moment, the renderer is specified in
display_options={"rendererName": "viewport2"}
, with Viewport 2.0 options specified inviewport2_options={}
. That is a bit unintuitive. How, for example, would one specify options forhardwarerenderer
, or a bespoke renderer?Make all display options part of one dictionary, and separate rendering option into it's own argument.
The text was updated successfully, but these errors were encountered: