Blender 2.7 and 2.8 support for exporting #21
Conversation
This file contains 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
Provide a more clear error message when a mesh exceeds the boundaries of the MD3 model space
export will now cancel if no objects are visible fixed return type if an exception is thrown during export
|
Good work, too bad he doesn't even care about pressing the merge button, could have closed a few related issues |
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 version supports both 2.7 and 2.8, but for exporting only. I have tested this in both and it works as expected. 2.7 will emit a version warning.
I have not touched the import script at all, since it is not in my use case.
I see there is another pull request for blender 2.8 support, but it does not seem to support 2.7.
Feel free to take what you want from these changes, or pick it apart, and take pieces as you see fit.