Revit NWC Export has Wrong Floor Elevations

Revit NWC Export has Wrong Floor Elevations

Marcus_lahn782BP
Explorer Explorer
150 Views
3 Replies
Message 1 of 4

Revit NWC Export has Wrong Floor Elevations

Marcus_lahn782BP
Explorer
Explorer

Hello all - I want to preface this that I am fairly new to using Revit so please bear with me. I have tried to find similar issues online or in these forums but wasn't able to find this issue with a fix. I am using Revit 2025 and the associated Navisworks NWC Exporter Utility, along with Navisworks Manage 2026.

 

When exporting my 3D view in Revit to an nwc, I get a result that is roughly 1/4" (51/256") off in elevation, but I can't seem to find any reason for that based on my Revit project. The only mention of a similar scenario online (Autodesk Forums) they said to try export settings as "Internal Origin" vs. "Shared coordinates". These are the results I get:

 

Internal origin - I believe this is the export type I would like to use. I have my project base point set at this grid line intersection, elevation 100'-0". This nwc export seems to have the correct origin, but the elevation is off by 51/256". The model has not been transformed.

Marcus_lahn782BP_0-1785245143182.png

Marcus_lahn782BP_1-1785245218478.png

 

 

Shared coordinates - I believe this has something to do with real world coordinates and true North? I have set up the true project North in my project but do not have any real world coordinates I can assign to my project.

 

Anyway, when exporting this I still have an issue with the model elevation. It does produce a result that has the correct floor elevation of 100'-0" (**side note: why does Navisworks display this as 99ft 12in, even when I have the accuracy set to 1/256" - other threads online just called this out as a bug). But then, looking at the transform of the model, it moved the model by 51/256" up to get the correct elevation. So really this model isn't even at the right elevation, just transformed to the correct elevation? 

Marcus_lahn782BP_2-1785245448129.png

Marcus_lahn782BP_4-1785245631188.png

 

I could apply this same Z transform to my internal origin export and that would fix my issue, but I was hoping to better learn and understand what is going on to produce these results with slightly off elevations. I would like to fix the root cause, as I assume there is something in Revit I am missing or not doing correctly.

 

Looking at my Revit project, I have this grid line intersection as the project base point and survey point with an elevation of 100'-0". My finished floor level is set at 0'-0" from the project base point. Revit project is at 1/256" accuracy, and I changed my floor level 02 by 1/256" to display this accuracy.

Marcus_lahn782BP_8-1785246567284.png

Marcus_lahn782BP_0-1785246686307.png

Marcus_lahn782BP_7-1785246215457.png

 

My gut feeling after finding issues in my nwc export was that my project base point or finished floor level elevation were off somehow, but I couldn't find anything that indicated this. Any help is appreciated!

 

 

 

0 Likes
Accepted solutions (1)
151 Views
3 Replies
Replies (3)
Message 2 of 4

Pavankumar_H
Autodesk
Autodesk
Accepted solution

Hello @Marcus_lahn782BP ,

Thanks for reaching out to us on Forums.

I understand that you are experiencing an elevation discrepancy when exporting/appending a Revit model to Navisworks, where the model does not appear at the expected elevation.

Please review the following points to help identify and correct the coordinate/elevation mismatch

1. Check the Survey Point and Project Base Point

  • In Revit, make the Internal Origin, Project Base Point, and Survey Point visible and review their relationship to the Finished Floor level.
  • In particular, please verify the Finished Floor elevation relative to the Revit Internal Origin. Since the Project Internal export shows an approximately 51/256" elevation difference, while the Shared Coordinates export shows approximately +51/256" as a Z transformation, this may indicate an existing vertical offset between the model geometry/Internal Origin and the configured project/shared coordinate system.
  • If possible, please confirm whether the Finished Floor is approximately −51/256" relative to the Internal Origin. This would help determine whether the observed result is coming from the Revit coordinate setup rather than an NWC export precision issue.

2. Review the Navisworks export coordinates

  • Check the coordinate setting used when exporting the Revit model.

  • Depending on your project setup, test the appropriate coordinate option, such as Internal or Shared Coordinates.

  • If you are unsure which coordinate system the project is intended to use, compare exports using the available coordinate options and verify the resulting alignment in Navisworks.

3. Verify the elevation base in Revit

  • Review how the relevant levels are reporting their elevations in Revit. Please note that the level's Elevation Base controls which coordinate reference is used for the displayed elevation and does not by itself establish the model geometry's position relative to the Internal Origin.
  • Therefore, before changing the Elevation Base, compare the Finished Floor against the Internal Origin, Project Base Point, and Survey Point.

4. Review the Autodesk guidance

5. Check software versions and updates

  • Confirm that Revit, Navisworks Manage, and the Navisworks Exporter are updated to compatible versions/builds available for your environment.

Please avoid sharing any confidential project information publicly.

For further investigation, you may also create a support case with Autodesk Support and attach the relevant files, logs, and screenshots for deeper analysis.

Kindly, click on 'Like' or 'Accept Solution' if this has led you to direction in order to resolve the raised issue.

Thank you!

Message 3 of 4

mari.shimode
Community Manager
Community Manager

Hi @Marcus_lahn782BP, how are you doing? Did you find the information provided useful? If so, please click the Accept Solution button on the post you found helpful so that others with the same issue can benefit from it in the future.

 

If you still have the issue, please let us know. Thank you.



Mari Shimode
Community Manager
0 Likes
Message 4 of 4

mari.shimode
Community Manager
Community Manager

Hi @Marcus_lahn782BP, since the methods suggested in @Pavankumar_H's reply may provide a solution or helpful tips for others who have the same issue, I have marked it as an accepted solution so they can refer to it.

 

If you're still having the issue or have any other questions related to what you originally asked, please create a new topic with a link to this post included so the community can follow the conversation easily. Please visit the Autodesk Community again if you need any help in the future.



Mari Shimode
Community Manager
0 Likes