Export GLTF instead of FBX, and use GLTF settings.#86
Open
Nightriff wants to merge 6 commits into
Open
Conversation
…ne.gltf until Blender 4.4.0
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.
GLTF is a more open standard than FBX, and is therefore the preferred format for better interoperability between programs. Now that the OpenCloud endpoint supports gltf, we can transition this add-on to use it as well.
Blender supports a different set of settings for GLTF than FBX. This PR replaces the FBX settings in AddonPreferences with GLTF settings. Similarly to how FBX settings were ripped from Blender's core exporter add-on, the same is done for GLTF settings to support the same export settings as the regular export flow. A subset of settings have been removed in favor of add-on defaults, such as restrictions on which objects get exported and removal of deprecated settings.
Additionally, a few defaults have are changed (e.g. blender defaults to not Apply Modifiers during export; this add-on defaults to True, since it seems more useful to do so).
Instead of cluttering index.py, any settings that were pulled from blender's core add-on have been placed in their own separate private dependency file.
The overall functionality of the add-on remains largely the same, except for a different set of export settings to work with.
Granted, it's difficult to test every setting available here to ensure it works, because there are so many. I have smoke tested a few of them and all the ones I tried worked just fine. They're simply passed directly into the export operator, so it should just work.
The new setting also includes a +Y Axis Up setting, which implements #13