Fix Renderers that store their output V-Ray ignores scene's vraySettings.fileNamePrefix; submitter falls back to <Scene>/<Layer> - #453
Open
dzavada wants to merge 12 commits into
Open
Conversation
…than # defaultRenderGlobals.imageFilePrefix. V-Ray's Render Settings Common tab # writes the "File Name Prefix" field to vraySettings.fileNamePrefix and does # not update the legacy defaultRenderGlobals attribute, so reading the default # attribute for a V-Ray scene picks up a stale/empty value and the submitted # job ignores the prefix the user actually configured.
dzavada
commented
Aug 10, 2026
dzavada
left a comment
Contributor
Author
There was a problem hiding this comment.
Fix formatting in renderers.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was the problem/requirement? (What/Why)
V-Ray ignores scene's vraySettings.fileNamePrefix; submitter falls back to / default 443
What was the solution? (How)
Renderers that store their output file name prefix somewhere other than
defaultRenderGlobals.imageFilePrefix. V-Ray's Render Settings Common tab
writes the "File Name Prefix" field to vraySettings.fileNamePrefix and does
not update the legacy defaultRenderGlobals attribute, so reading the default
attribute for a V-Ray scene picks up a stale/empty value and the submitted
job ignores the prefix the user actually configured.
What is the impact of this change?
N/A
How was this change tested?
I submitted jobs through Maya and tested that is in fact was following the correct naming prefix.
Integ test result
delete text starting here
If src/ was modified or a file was added/removed, then update the integ tests and post the test results below. See
DEVELOPMENT.md on additional instructions on running some, or all integ tests.
delete text ending here
Installer test result
ADAPTOR_OUTPUT: STDOUT: Performing action: {"name": "output_file_prefix", "args": {"output_file_prefix": "Mavic/%s/%l/%l_%v"}}
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
No
Was this change documented?
No
Did you modify schema files?
Yes
[ X] No
If yes, Did you bump the integration_data_interface_version in src/deadline/maya_adaptor/MayaAdaptor/adaptor.py and update the test constants?
See the "Schema Versioning" section in DEVELOPMENT.md for details.
Yes
[ X] No
Is this a breaking change?
No