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
When copying the same linked model several times, Speckle converts them only once. The issue occurs when sending everything by view or selection.
To Reproduce
Open Revit
Link a file
Copy the file several times
Send to Speckle
Expected behavior
We would expect each instance of the copied link to be converted.
System Info
Version 21.02
Revit 2024
Proposed Solution (if any)
When reading selected elements, you must track their origin, including which version of the linked document they refer to.
Currently, the implementation relies on a unique ID to prevent elements from being converted multiple times. However, the issue is that these copied elements share the same “unique” ID and refer to the same Document. One way to distinguish them is by using the RevitLinkInstance.
We understand that this repository may no longer be your primary focus, but please consider this approach when working on version 3 of the connectors.
The text was updated successfully, but these errors were encountered:
Prerequisites
What package are you referring to?
Revit converter
Describe the bug
When copying the same linked model several times, Speckle converts them only once. The issue occurs when sending everything by view or selection.
To Reproduce
Expected behavior
We would expect each instance of the copied link to be converted.
System Info
Proposed Solution (if any)
When reading selected elements, you must track their origin, including which version of the linked document they refer to.
Currently, the implementation relies on a unique ID to prevent elements from being converted multiple times. However, the issue is that these copied elements share the same “unique” ID and refer to the same Document. One way to distinguish them is by using the RevitLinkInstance.
We understand that this repository may no longer be your primary focus, but please consider this approach when working on version 3 of the connectors.
The text was updated successfully, but these errors were encountered: