Should Deadline Submitter Settings be Persistent with Scene Files
Yes, all relevant submission settings should always be stored in the scene file
Yes, some submission settings should be configurable to be stored with the scene file and optionally prompt the user with the list of what will be changed when loading a scene.
Yes, but it should require a manual Load operation so they don’t overwrite local settings on scene load without notice
No, never (current behavior)
0voters
I’m not a big fan of how Deadline stores it’s sticky settings. Some I agree are settings you want globally across all jobs you submit, like path settings etc… but other are individual per job.
Groups/Limits/Tile/Regions are all setting that in my opinion should be saved with the max file you save.
For the vanilla Deadline Submitter, i think this settings should be persistent (avoiding globals ) to the file max. It may help other team members get the correct settings, for a re-render.
I updated the initial post with an actual Poll.
I agree that the current SMTD behavior could be improved.
But I disagree that the settings should just propagate without asking.
The current behavior came from the following usage model:
A Deadline user would be assigned a project and would work on it for several months (typical in VFX). The majority of SMTD settings would be set once and never touched. If I open a scene created by someone else, it would drive me mad if my SMTD settings would be changed to something I don’t know about (with the egocentric assumption that everyone in the company is more stupid than me )
Thus, I am inclined to introduce a way to store and restore SOME settings with the scene file. But I would like to also provide mechanisms to define what settings will stick with the scene. We can then either prompt the user via a callback when a scene is loaded to accept all or some of the incoming settings created by someone else, or even provide a manual set of buttons to Store / Restore settings from the scene file when desired (similar to the Presets loading dialog which shows what is different between the current and the incoming settings, but using data riding in the scene file).
Another useful idea would be to stamp the settings data with the user name, and have the option to accept automatically any settings that were created by the same user as the current one, and prompt when the settings are coming from a different users to avoid frustration and conflicts between users (“That moron limited the job to his workstation and I did not notice #*@!”).
In short, I am open to the idea, but would prefer to have a long discussion about how it should work so everybody gets the desired flexibility without any negative side effects…
I am talking only about the Submit Max To Deadline script as I am not responsible for the other integrated scripts. But the discussion could eventually lead to their changing, too.
) to the file max. It may help other team members get the correct settings, for a re-render.
)