Basic instance collection support #655
Open
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.
My personal workflow benefits from instance collection support, and on seeing that the issue that's raised for it (#326) hasn't been touched or commented on in the last two years, I figured I'd bash out a basic implementation.
The implementation as is recurses objects in the 'Exports' collection and ensures that all nested objects make it to UE. Each instance collection attached to a mesh is converted to a socket with the format
MeshAttach_{collection name}#{unique child name}
.This is intended not as a complete and mergeable snippet, but as a stopping off point for others that need this kind of support. I don't know much about blender scripting or the plugin-preferred way this should be implemented, so will probably leave it as is.