Model in Navisworks disappears when rotating in a specific area of the model

[Anonymous]

I have an issue where when I rotate my view then a specific area of the model is not show

Se attached recording.

I have checked my settings according to this: https://forums.autodesk.com/t5/navisworks-forum/sectioned-navisworks-model-disappear-in-certain-quad...

But that has not worked.

As you can see in the recording it is like there is a box of the area that make this section, when I try rotating in from left, right, top or bottom.

Kind Regards

[Patrick_Aps_9121]

There are 2 things you can try:

1) select something, like a column -> Right mouse menu -> Focus on item. Then see if orbit and/or Look around behave better

2) Home -> File Options -> first tab "Culling, lower half "Clipping Planes". Switch from Automatic to Fixed and set Near to 0,001 (meter) and far to 1000 (meters)  If this helps, save your NWF /NWD so that it stays fixed the next time you open it.

[dgorsman]

In addition to @Patrick_Aps_9121 point (2), wonky view clipping and navigation can be the result of an extremely large model, usually caused by an isolated object waaaaay out in space.  Navisworks automatically sets the clipping planes and navigation speed by the overall physical size, so a rogue object can throw things off (nothing like popping into a model and finding the walk speed is 10k m/s...).

[Anonymous]

I think I have found the solution/issue myself

There was a element hidden i the .dgn files we received and that element was far away from our designed model - it was a modelblock information stored at 0,0,0.

After removing it from the files and reloaded the files has the issue been fixed.

[ajit.menon · Accepted solution]

Hi as discussed on our call this morning, it was the text nodes and lines that were located really far away from the model, that caused the issue. Zooming extents in plan view, locating those objects and hiding / removing them, allows the model to also be fully visible in the viewport. The zoom orbit and realtime zoom works fine after this. As discussed you could also retain those elements if needed, but create a search set to hide them when working in your model. 

[aman.kumarRVKHA]

Dear Patrick,

The second solutions which you suggested, was very helpful!