/ magnum-plugins Public
AssimpImporter: support multiple meshes per Assimp node #81
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.
Magnum::MeshObjectData3Dsupports only one mesh instance, the importer has until now silently ignored any additional meshes per scene node.
We now add additional child objects for any extra meshes. This adds some ugliness to
doObjectData3D()and friends, because we need to differentiate between "original" nodes referring to Assimp nodes and the new "additional mesh" objects.
This also adds a unit test using a hybrid quad/line mesh exported from blender.