Fix #485: Allow avalon to initialize correctly with Maya 2020#486
Merged
Conversation
davidlatwe
approved these changes
Dec 14, 2019
Collaborator
davidlatwe
left a comment
davidlatwe
left a comment
There was a problem hiding this comment.
Can confirm this PR fixed the issue in Maya 2020.
Nice work !
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
2 participants
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's changed?
This fixes #485 so that Avalon launches without errors in Maya 2020. Without this change the Avalon menu would not initialize with Avalon's
userSetup.pyfor Maya and would give errors in the Output Window.I've tested this change in Maya 2019 and 2020.