Duplicate Node Created and Transformation Identity Issue When Appending Revit Files in Navisworks 2024

Duplicate Node Created and Transformation Identity Issue When Appending Revit Files in Navisworks 2024

jevimech
Explorer Explorer
265 Views
1 Reply
Message 1 of 2

Duplicate Node Created and Transformation Identity Issue When Appending Revit Files in Navisworks 2024

jevimech
Explorer
Explorer

 

Hello,

 

I am encountering an issue when appending Revit files to Navisworks 2024. When I append a Revit model, it creates a duplicate node in the selection tree. The duplicate node appears to act as an instance, but I am seeing a "transformation identity" for this node. Meanwhile, the actual transformation is applied to the node located below the duplicate in the selection tree.

 

This issue only occurs when appending Revit files and does not happen with other types of files. The problem seems to stem from how Navisworks is interpreting the transformations of the Revit model during the append process.

 

I have already tried verifying the export settings in Revit and checking the transformation data, but the issue persists. I am also working with the latest versions of both Navisworks 2024 and Revit.

 

Has anyone experienced a similar issue, or are there any known fixes or suggestions to resolve this behavior?

 

In the attached image, the highlighted nodes are where I am getting the actual transformation values.

 

Any help or insights would be greatly appreciated!

forum.png

 

Best regards

0 Likes
266 Views
1 Reply
Reply (1)
Message 2 of 2

naveen.kumar.t
Autodesk Support
Autodesk Support

Hi @jevimech ,

 

Is this issue related to the Navisworks API or the Navisworks product itself?

Please note that the Navisworks API rarely supports functionality that is not available in the user interface. Therefore, if an issue exists in the Navisworks UI, it is likely to occur in the API as well.


Could you try appending your file manually via the Navisworks UI without using the API? Does the issue persist in the UI?

If so, it would be best to first explore and identify the optimal manual approach before attempting to implement it programmatically. I recommend resolving the issue in the Navisworks UI first, as this will provide a clearer path for implementing it via the API.


Once the best manual approach is identified, I will assist you in replicating it through the Navisworks API. Let me know how it goes.


For Navisworks product-related issues, please contact experts in the Navisworks Product Forum.


Naveen Kumar T
Developer Technical Services
Autodesk Developer Network

0 Likes