Revit 2013 - Moving level issue - non bounding rooms

[pmcmahon534439]

Hi all,

I want to change a building level 01 height from 4m to 4.5m. Upon doing this (constrained) all of the level 01 room tags appear as non enclosed. However, they are still associated with level 01. All walls, floor, roofs etc are room bounding. They have all moved correctly upon the level change and appear fine in section. All model work appears correct except the room enclosures. I've racked my brains (I have been using revit for 7 years) and cannot figure this out. Is this a 2013 bug ?

Any help appreciated.

Patrick.

[Alfredo Medina]

The computational height of the level must intersect the walls for the rooms to work properly. It behaves like a plane. Select the datum level symbol for Level 1 and check its computational height value. Then check the properties of the walls for that level. Is that plane intersecting the walls or not? In addition, check the settings for upper and lower limits of the rooms.

[pmcmahon534439]

Alfredo - Thanks.

I should have mentioned that I checked / tried amending the computational height (set at 0 before and after and no change dispite playing with this) and room limits with no luck. Everything you would expect (wall / plane intersections) were correct.

Upon trying again this morning on an archived model the solution was to go into a section / elevation, select the levels and then move (with constrain and disjoin unchecked !) - everything has moved appropriately and the rooms remain intact as you would expect.

However, in the current model (only a few days between them) I do the same thing and all rooms are now not enclosed.....

Patrick

[pmcmahon534439]

I found a ridiculous solution -

I copied the entire model (including the non-bounded rooms following the level change) into an archived version (having deleted all geometry in that model) and everything resolved itself.

Fine as a solution to a project in the relative early stages but madness if this was an advanced project. Unsure whether the model was corrupt. Hopefully someone will uncover a more sane solution.

Patrick.