You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be possible to enhance instancing by using the FamilySymbol member of an element's FamilyInstance object. For example, when instancing via hashing geometry objects, only two of these 5 benches instance. However, they all share the same Symbol reference:
A point of confusion is that these benches export with differing numbers of verts and faces, which is why they fail the hash test for instancing. However, they look like genuine instances in other ways.
It might be possible to do away with hashing geometry data completely. The addin spends ~50% of its time serializing the data to hash.
The text was updated successfully, but these errors were encountered:
(This is arguably not necessary for GTM.)
It might be possible to enhance instancing by using the FamilySymbol member of an element's
FamilyInstance
object. For example, when instancing via hashing geometry objects, only two of these 5 benches instance. However, they all share the sameSymbol
reference:A point of confusion is that these benches export with differing numbers of verts and faces, which is why they fail the hash test for instancing. However, they look like genuine instances in other ways.
It might be possible to do away with hashing geometry data completely. The addin spends ~50% of its time serializing the data to hash.
The text was updated successfully, but these errors were encountered: