Actual projected view of hotlinked elements - Floor cut plane does not affect ifc

[Lyngordon]

Is there any way to control visibility of hotlinked elements on a per story basis? We have a renovation project where we want to coordinate with the construction engineer and show the concrete walls (from the engineers) in our plans. They are modelled correctly and associated with the right story, but because they start 30 mm below the second story level, they get displayed as if they were symbolically cut on the first floor. The result is that on our first floor plans, both the walls on the second story and the first are displayed on top of each other. 

If we change our story definition such that the second story starts 30mm lower, they disappear from the lower story. However, that is not acceptable, as the stories are locked and placed at the level of the finished floor of the new part.

No amount of tweaking the floor cut plane affects this. This seems like a basic functionality that is missing - I want hotlinked elements to be projected just like native elements, and I want them to be represented in the model as they are going to be built. 

Story 01: red is story 1 elements, blue is story 2. The blue elements are shown as they would be if they where symbolically cut on story 2.

Story 2: green is story 3 elements. The red story 01 elements stretch over several floors, that is acceptable.

 Section: The offending walls from story 2 are shown selected.

Operating system used: Windows WIN 11 25H2

[Lyngordon]

And here you see the result of moving story 2 30mm lower. Walls get displayed correctly on story 1 but not a cut of the floorslab is shown on story 2. 😕

 

Story 1: 

Story 2:

[Lingwisyer]

Just clarifying, these conrete walls from your engineer are hotlinked as IFC files?

Is there anything in the translator settings regarding linked storeys?

Ling.

[Lyngordon]

Yes, hotlinked IFC from Revit. 

The translator is basically the standard Revit Structure-translator that ships with AC29, we've only changed the layer suffix from .Revit to .RIB. I don't see anything in the translator settings that should affect this.

The ifc is set to keep elevation, and as said, the story definitions in the IFC match ours.  The only difference is that we have more stories in total, because our model also has the new stories (which are included in a separate IFC hotlink from the engineers). All objects are linked to the right stories, and have the right elevation. It's just visually in plan view that they are displayed wrong. 

[AllanP]

If I was trouble shooting this I would look at this:

why is the structure an Object?

are all the Revit IFC elements Objects?

Objects don't work well with the "floor plan cut plane".

I would check the IFC conversion settings to see if things are set to Objects, or Element or Morphs.

File -> Interoperability -> IFC -> IFC Translators

Revit Structure Import -> Geometry Conversion -> are they set to Objects, Building Elements, or Morphs?

[FIRE BAD, NAPSTAR BAD, OBJECTS BAD, Building Elements GOOD]

I would also switch the Cut Plane form "Story(s) Above" to "Current story"

also check to see if the Revit object are set to "All relevant stories"

Try and see,

I hope this helps.

[Lyngordon]

Thanks. Most of the walls behave as walls on import, but there are some that get converted to objects. That seems to be a seperate issue, possibly related to how the openings are modelled in revit. Anyway, all objects are shown with outlines only without any indication of where their openings are placed. 

The issue here are those elements that do get imported as walls with openings. We have no control over the Floor Display of a hotlinked IFC, and they don't respond to the cut plane settings of the project. (As explained in my first post). 

 However, that seems to have resolved itself on it's own, as the latest version of the file the offending walls are suddenly shown as projected. The settings seem to be the same though. ¯\_(ツ)_/¯ 

Previous version:

Current version, same element, same settings? 

[Stefan L_]

Not exactly your case, but I'm importing ProvisionForVoids here as Morphs, and I've to configure the Morph tool first (show on relevant stories...) to get what I want.

It might help to check/set the relevant tools before importing.