@infosia Yeah, totally. And actually that’s already how it behaves internally. The assimp plugin just populates the
dcc_asset truth object owned by the
dcc_asset plugin, then after import The Machinery operates on the
We also have our own gltf2 importer plugin but it hasn’t been tested in a while as assimp has precedence. But you can try to delete the assimp plugin and you should see that you can still import
I think we probably should just open source both the assimp and the gltf-plugins as samples to show how to roll your own importers. It’s fairly straightforward.