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
drop custom Deadline plugin and explore vanilla Deadline plugin's RPC implementation
add support for rendering multiple passes
publish with preview (and all the different AOV's)
persist submitted P4 changelist in rendered EXRs metadata and AYON
Using Media Render Queue
use jobs in MRQ as render instances in similar fashion we use render layers in Maya
being able to create multiple renderQueue's to submit more than 1 shot to deadline
when creating the publish instance (type render) it should update the MRQ item automatically
deadline job should be named after the level sequence that should be rendered
Using Media Render Graph
implement custom blueprint node
Perforce
ChangesViewer should only show changelists from current stream and depot
Collect Latest Changelist should collect from local stream only not throughout the depot
support for Multi-Stream setups by using stream/templates
automatic creation of local P4 workspaces based on workspace templates
enables using streams as tasks in AYON
Suggested implementation?
I started something kinda working that's much influenced by this post.
It covers a lot of the notes atop but is very rough around the edges. Should convey the idea tho.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
As discussed on discord this shall serve as a milestone and is currently rather a summary.
General Rendering Suggestions
-MRQInstance
on nodesUsing Media Render Queue
Using Media Render Graph
Perforce
Collect Latest Changelist
should collect from local stream only not throughout the depotSuggested implementation?
I started something kinda working that's much influenced by this post.
It covers a lot of the notes atop but is very rough around the edges. Should convey the idea tho.
Describe alternatives you've considered:
No response
The text was updated successfully, but these errors were encountered: