Wrong data granularity - Selection Resolution - Same Revit Input - Different Navisworks Output

mmunoznieto — Mon, 13 Nov 2023 18:22:39 GMT

Hello,

This situation has been a headache for a while. Situation: Snip Attached.

Revit Model : Same Family - 2 different instances - Same Instance parameters values (less location and ID obviously)

Exported to Navisworks. Both instances follows this selection resolution structure tree:

Item 1: - File > Layer > Collection > Collection > Collection > Composite Object > Geometry

Item 2: - File > Layer > Collection > Collection > Collection > Composite Object > Insert Group > Composite Object > Geometry

These 2 Extra levels is always destroying my Selection Inspector Data List, from where I check Models Data.

Navisworks Export settings obviously are the same for both, cause is same exportation. No nested families inside the family, no assemblies, no Revit Groups.

Any idea, or guidance on how Navisworks works internally to create this levels or hierachy?

Thanks!

topic Wrong data granularity - Selection Resolution - Same Revit Input - Different Navisworks Output in Navisworks Forum

Wrong data granularity - Selection Resolution - Same Revit Input - Different Navisworks Output