Objects not visible in section views

[tknapp]

First let me start with a little background. I am running Revit Struct 2009. I have an overall structral model that has 3 models linked into it (steel framing imported from RAM Struct). I put the foundations in my overall model. Here is my problem. I cut a section & go to view the section & the foundations show up (modeled in overall) but nothing from the linked models shows up. HERE COMES THE KICKER. When I flip the section mark (the same section mark & location) everything shows up proprerly. What is going on? Does anybody have any ideas???????

[G_J]

I have had a similar problem in the past with Structural Connection families....

There seemed to be a bug in Revit that made the system get confused when representing structural connections.

Connections were visible in sections even though they were 'outside' the sections view range/extent. Also structural connections were not appearing 'hidden' when behind an object.

The work around was to put all structural connections onto the generic model category in the family category menu.

I know that isn't much help with your situation, but it could be a similar bug..

Have you tried submitting a support request to Autodesk?


Regards

[tknapp]

No I haven't put in a support request. I will do that.

[tknapp]

No I haven't put in a support request. I will do that.

Autodesk support hasn't been able to figure this one out. The Tech. Support rep. is submitting my files to the development team for futher investigation. Sounds like a bug! Guess, I will just wait. I had to do some creative work arounds to get the job out the door.

[tknapp]

O.K. Here is what Autodesk Support has told me . . . .

"I am very sorry for the delay while the development team was investigating the files. They have confirmed that there is an issue with back clipping that needs to be resolved. In the meantime, they have suggested setting the Far Clipping parameter in the sections' Properties to "clip without line" - the elements should then become visible. I hope this is an acceptable workaround for the time being. Again, I apologize for the delay. If you have any questions please do not hesitate to send an update to the case."

[mwarwick]

I can confirm that this issue still occurs with Revit 2017.