Add logging level control for gltf exports #2299
Merged
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.
Issue: Exporting scene as gltf when using python built as a module is very noisy with
INFO
logging entries.I have made changes to
ExportGLTF2_Base
in:blender/scripts/addons_core/io_scene_gltf2/__init__.py
changes support setting the log level instead of using the hardcoded
INFO
value here which produces way to much output when exporting.ImportGLTF2
already has a pattern for this here so I created a globalset_debug_level
function they can both use in the same manner.The user can now set the log level before exporting by setting
bpy.app.debug_value
like:This will solve issue 2267