Autodesk
PR: Curious case of linking behaviour in 24.2
Problem Description
I had the following linking issue with an IFC from Vectorworks:
In Revit 2023 and previous versions I get the old familiar linking behaviour where some models with large coordinates appear miles away from the project base point:
In Revit 2024, however, the linked IFC is placed fairly cloase to the project base point, but not origin-to-origin:
I would be happy to send in the file to get to bottom of what is causing this.
Workaround
Remap the coordinates to local with a custom tool, link first in Revit 2023, only then link in Revit 2024. Not exactly my idea of fun.
Revit Version
2024.0.x
IFC for Revit Addon Version
24.x.x
Windows Version
10 22H2
Hello @andydandy74 ,
Sample files to reproduce your issue would be very helpful. Could you please share the .rvt project, .ifc file, and any additional information to my email ([email protected])?
Regards, Oleksandr
Hi @andydandy74,
To fully understand the issue and make the correct fix that works for you I need to know the configuration of Project Base Point and Survey Point of both Revit models. Is it possible to share the .rvt file you are exporting from and the .rvt file you are linking to?
Thanks, Ihor [email protected]
@t-vasyi Sorry for the late reply. I can only share the model the IFC was linked into since the IFC itself was created in Vectorworks. I sent you a download link for the model.
Hello @andydandy74, Thank you for reporting this behavior.
After thorough investigation, we confirm that this is expected behavior due to how Revit handles IFC files with large global coordinates during import and linking. Starting in Revit 2024, the Hybrid Link mode adjusts for large coordinate values by shifting geometry closer to the internal origin as part of an intentional "large coordinate fix." This adjustment is handled internally by ATF (Autodesk Translation Framework) and does not imply incorrect positioning.
In your case, the IFC file contains element coordinates located over 3000 km from the origin, while the IfcProject or IfcSite placement is at (0, 0, 0). Revit compensates by relocating the geometry so that it can be visualized and manipulated correctly.
This issue is now considered resolved as "By Design." We appreciate your feedback and are tracking suggestions for more granular control over positioning behavior.
