I’m using external 3d applications which have layers and groups, but can only find one way to import these such that either maintain associations: as mesh nodes using FBX comp with .fbx or .3ds formats (import obj → groups don’t work; could be my editors).
FBX import suggestions/help requests:
Request: a way to import geometry where groups are maintained and/or converted to TD groups.
edit: deleted, was my problem unrelated to TD
Each mesh gets imported with a nested sibling node of a default material; no export settings allow me to change this.
Should I care? Do orphaned material nodes (without any active cooking) degrade performance?
If so, is there a way to mass delete these, other than a python script .destroy()?
We only do grouping for merged operators but we could add an option for importing groups from the file, though it may not be possible to do both.
I’m not sure if I’m following your second point – could this be solved with the import scale parameter?
A lot of extra nodes can degrade performance. One big impact is in navigating networks – but if the extra nodes (MATs in this case) are within a COMP and part of only a small network then that impact would be mitigated.
A python script is a good way to clean up nodes. The FBX COMP has an onImport python callback that can be used for this purpose. The Replicator COMP or cloning could instead be used, but python would probably be needed in those cases anyway.
Thanks Eric! On the second point, it’s on my end: I am developing in CAD software which has specifiable units for designers (Rhino). It can switch from millimeters to miles (and more), but no matter what I set it to, there’s a strange conversion factor being applied to the exports.
