topic Re: Twin Motion load not on the marble in Revit Architecture Forum

Twin Motion load not on the marble

dcarlsen8GY35 — Thu, 19 Dec 2024 06:14:57 GMT

My project loads in Twin Motion way out in left field. Why and how do I fix it ?

Re: Twin Motion load not on the marble

RDAOU — Thu, 19 Dec 2024 07:51:34 GMT

Why is related to the difference between coordinate systems (Internal Origin vs Project Base Point) and the coordinate system in Twin Motion.

If your model in Revit is using sharedcoordinates in general or when modeling large sites and/or geometries modeled therein are far from either points (worse when far from the internal origin), it will cause displacement issue in Twinmotion. Only way to avoid this is ensuring that the Project Base Point is within range from the Internal Origin of the revit model.

How to ensure they do not get too far off from each other?

Use the tools such as Relocate Project instead of just manually draging the Project Base Point
Model sites in separate model and when site is XXXL or say +/- larger than a 10 soccer fields, consider splitting the site into multiple models. (Revit is not an Urban planning software)

Re: Twin Motion load not on the marble

dcarlsen8GY35 — Fri, 20 Dec 2024 17:55:46 GMT

Thanks, I think this is where the solution lies. Just to have more information, I looked in Visibility Graphics<Site and checked IO and PBP and sure enough, the distance between the two appeared to be the amount of the offset from the marble. So 1) the marble seems to use the IO as the placement point, and 2) If I go to a plan view and can see the underlying model with the PBP in blue and the IO in color for the underlying model quite a distance from the PBP and select Manage<Position<Relocate Project and hover over the visible color IO and select that, the entire project will be relocated so the PBP and the IO are at the same point ? When I check the visibility in the VG, I also see the numerous greyed out IO and PBP for the linked models. I assume they do not relocate in some way that changes their relative position in the overall project, just the underlying project PBP for the base model determines the relocation details and the linked models are brought along in their currently relative positions?