e19f0042ca
During the import process, many importer nodes are replaced with their engine node counterparts. For example, ImporterMeshInstance3D is replaced with a MeshInstance3D node. Any meta data set on these importer nodes, i.e. through a GLTFDocumentExtension, are lost during the conversion. This change copies over any meta data set on these importer nodes to their engine counterparts. |
||
|---|---|---|
| .. | ||
| doc_classes | ||
| editor | ||
| extensions | ||
| structures | ||
| config.py | ||
| gltf_defines.h | ||
| gltf_document.cpp | ||
| gltf_document.h | ||
| gltf_state.cpp | ||
| gltf_state.h | ||
| gltf_template_convert.h | ||
| README.md | ||
| register_types.cpp | ||
| register_types.h | ||
| SCsub | ||
| skin_tool.cpp | ||
| skin_tool.h | ||
Godot GLTF import and export module
In a nutshell, the GLTF module works like this:
- The
structures/folder contains GLTF structures, the small pieces that make up a GLTF file, represented as C++ classes. - The
extensions/folder contains GLTF extensions, which are optional features that build on top of the base GLTF spec. GLTFStateholds collections of structures and extensions.GLTFDocumentoperates on GLTFState and its elements.- The
editor/folder uses GLTFDocument to import and export 3D models.