Fix random inconsistencies between instantaneousShutter and ignore_motion_blur#2514
Merged
cpichard merged 2 commits intoAutodesk:fix-7.4.4from Jan 16, 2026
Merged
Conversation
cpichard
approved these changes
Jan 16, 2026
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.
This PR makes it so that the render delegate support for instantaneousShutter and ignore_motion_blur is consistent between husk and kick.
As it's usually done when arnold and usd attribute conflict, the arnold one should take precedence. So as soon as the arnold attribute
ignore_motion_bluris set in the render settings, it will override the usdinstantaneousShutter.We could consider in a future release to make it so that either of these 2 flags disables motion blur, but that would break existing scenes so it should be planned for a major release
Issues fixed in this pull request
Fixes ARNOLD-17155