Shared Coordinates option in Revit's Navisworks Export not working?

[kristina.bollin596153]

I am exporting several Revit 2012 files to Navisworks 2013 using the export Add-In. The Revit files are using Shared Coordinates and are aligned correctly in Revit. I tested this using a blank file and linking each file in "By Shared Coordinates". Everything falls into place perfectly. When I export to Navisworks (YES, the "Shared" option is selected in the export Options), the files come in as if they were using the Project origin. Can someone tell me what is happening here? Is this a better post for the Revit forum?

To clarify, I am exporting each file individually, not all together with the links (by the way, the option to include links isn't working for me either). Also, I have tried binding the links after linking by shared coordinates, and that works. However, that isn't a good workflow for continuous exporting.

Any help is appreciated. Thanks in advance!

[kristina.bollin596153]

Update to post - I started blank Arch & Struct projects and set up shared coordinates, then exported to Navisworks using the Shared setting, and everything works beautifully. So, it's not the exporter, and it's not Revit... it's the project. Does anyone have any clue as to why a certain project would cause this error? Again, I tested that the Shared Coordinates were set up correctly by linking in each discipline into a brand new blank file. The files were all linked using By Shared Coordinates and fell into place correctly in Navisworks. They just don't export to the correct location, even though the Shared option is selected. Furthermore, this same project does not like the "include Linked files" option, as the links never come through either. Any thoughts?

[brenehan]

Maybe just check the units are consistant?

Just a thought.

Brian

[RevitNinja]

If you are using NW 2013, you can just open the Revit files in NW. Try that instead of exporting NWC from Revit 2012.

[Revit for Breakfast]

You can have 2 different project basepoints. The real problem is if just one of those basepoints physically gets moved. That one is hard to detect. Sometimes its the north / true north setting. Most times it is frustrating. With experience you'll figure out how to cope with it. I would love somebody it explain the whole coordinates thing using a cartoon. It seems to be different is every software.

[diarmuid.ryan697366]

This problem only seems to effect Revit models imported into Navisworks. It really is something that requires addressing by Autodesk (hint hint).

The issue is with the Project Base point location. Revit has a default "internal" origin (this internal origin is not accessible or viewable by mere mortals such as us). It is known as the "Project Start Up Point" Your Project Base point should be at that location (it is by default). obviously you can give the project base point any value you want, provided it remains at that "Project Start Up Point" location.

How do i check if my project base point as at this “Project Start Up Point”?

The Project Base Point can be reset to this "Project Start Up Point" point by setting it to unclipped, right clicking on the icon and selecting Move To Start Up Location. It will divert revert to this default location.

Navisworks will use shared co-ordinates, but it will only use this “Project Start Up Point” as the insertion point for the Revit models imported into Navisworks

The solution I’ve come up with (as it is only a small model) is to create a plan with unlimited view range and use the move command and select all of the objects move them "the old fashioned way”. If anyone knows of a more correct way of moving the model please feel free to make a suggestion.

Diarmuid