Incorrect Room Boundaries

[PhilvK]

I had 2 rooms set up in a project with Room tags, and everything working fine. I then had to raise the slab of the floor in these rooms 4” to accommodate site issues. After raising the floor and trying to raise the base of the walls sitting on the slab, I get the message “Room is not in a properly enclosed region”. I deleted the rooms and tried to re-place them but get the same message. I can’t figure out what I messed up by raising the slab. Is there something obvious that is related to room boundaries that is changed by raising the floor level?

[Alfredo_Medina]

Probably you should have raised the level, not the slab and the base of the walls. At the moment, the base of the walls are 4" above the level. Levels have a parameter named as "Computational height" whose default value is 0". The level is not seeing any walls at that level, so your rooms lose their boundaries. Solution: raise the level instead of raising the slab and the walls, or change the value of the computational height parameter of the level so that it intersects the elevation of the base of the walls.

[PhilvK]

Alfredo – Your response got me to thinking: I should have just added another level instead of linking one of the slabs to Level 0-0 and offsetting it 4”. I tried that but it too is messing with the room boundaries. I’ll try some more until I get it right. It will be good practice for me. Thank you again.

[Alfredo_Medina · Accepted solution]

No, don´t add more levels just for that reason. Levels should be, ideally, from floor to floor, and everything in between can be handled by offsets. Too many levels with short distances in between can create a confusion with view range settings, because they are by default set to "upper level" or "lower level".

[chrisplyler · Accepted solution]

What? No they aren't. The view range of plan views is by default set to the associated level with defined offsets. I frequently make several levels between floors to control various things, and have no view range problems whatsoever. The only annoyance is having to clean up elevation views by hiding all the levels I don't need shown in them.

[Anonymous]

Late answer but it might be useful to other people faced with this problem. I situations where you have a secondary floor you need to ensure that your Computation Height for the level is set correctly. Computation Height is an instance property of a level that is used to compute the room perimeter, area, and volume.

Also look into room instance properties where you can set various offsets that are used in area computation.

[Anonymous]

all this stuff needs to be fixed. With yearly subscriptions, this is unacceptable. This is how architects work and YOU need to adjust this software in response... not "you should have"... and so on.... which is generally the answer to every issue on this site.