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
Files transformed by the transformer often keep huge unused definition elements like geometry parts. We need to track references to geometry parts (in geometry streams, line symbols, pattern symbols) while cloning geometry to prevent this.
Users facing this now must use the IModelDb.elementGeometryRequest API to check for used geometry parts themselves, and not import them, but the transformer should start doing this in its own native geometry cloning routine.
The text was updated successfully, but these errors were encountered:
Hi Michael, is there an estimate on when this fix will be available? This has come up as a paid prod issue labeled as high priority and the client has been asking about this.
Thanks,
Tim
Hi Michael, is there an estimate on when this fix will be available? This has come up as a paid prod issue labeled as high priority and the client has been asking about this. Thanks, Tim
The estimate I gave when I was asked monday was 3-4 weeks. Please contact me if you think that is an issue.
longer term fix rewrite native geometry processing to record references as it goes, which will go hand-in-hand with the refactor of all native geometry processing
Files transformed by the transformer often keep huge unused definition elements like geometry parts. We need to track references to geometry parts (in geometry streams, line symbols, pattern symbols) while cloning geometry to prevent this.
Users facing this now must use the
IModelDb.elementGeometryRequest
API to check for used geometry parts themselves, and not import them, but the transformer should start doing this in its own native geometry cloning routine.The text was updated successfully, but these errors were encountered: