- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
I am experiencing the following strange problem. I am creating an in-place element as described in this article. The element is created far away from the document base point/origin. However, if at this point I run a CustomExporter and I read this element's Transform, it says that it is the Identity transforms, i.e. Origin is (0,0,0) which is not true.
Inspecting the family instance with Revit Lookup shows the same wrong origin (BeforeMove.png)
After I move the element somewhere, its Origin is now correct, i.e. not zero.
Steps to reproduce:
1. Open the attached InPlaceFamilyWrongOrigin.rvt file
2. Select the only element in the project, i.e. the in-place created element (ElementId: 202108)
3. From Revit Lookup -> Snoop Current Selection -> GetTransform -> Origin: shows (0,0,0), when it is clearly visible that the element is not at the document's origin, i.e. the blue symbol.
4. Slightly move the element with the mouse in any direction.
5. From Revit Lookup -> Snoop Current Selection -> GetTransform -> Origin: shows the correct origin, i.e. different from zero.
We experience the same problem when the user creates an in-place family and then we export data from Revit. All in-place created families which were never moved appear in the document origin, because the Revit API call to GetTransforms always returns the Identity Transform.
Solved! Go to Solution.