dbaldacchino
2007-12-17, 07:05 PM
Hi all,
Typically we leave the default setting for Room and Area settings to "At System Computed Height". This sets the "cut plane" for area calculations at some value, which is typically offset 0'-0" from the level. Or at least that's what it has done until today.....
I'm looking at a project where the system computed height is now 4'-0" above the levels. How does Revit determine this? The reason we discovered the issue was because we had a series of openings in the walls, set at 2'-6" above the level and the rooms kept "flowing" through. I kept raising the Bottom Offset until finally, at 4'-1", the rooms started behaving like I'd expect them. I also tried grouping the area in question and save it out to a file, but when opening this file, the system computed height went back to 0'-0", which indicates there's something in the project causing this. Once we set the Room and Area settings to "At Specified Height" of 0'-0", the rooms started recognizing their bounds and the areas calculated correctly. I've never had to change this manually before. Anyone run across this?
We also tried auditing the central file, resolved all warnings in the project pertaining to overlapping walls, room separation lines and rooms, but the issue remained.
Typically we leave the default setting for Room and Area settings to "At System Computed Height". This sets the "cut plane" for area calculations at some value, which is typically offset 0'-0" from the level. Or at least that's what it has done until today.....
I'm looking at a project where the system computed height is now 4'-0" above the levels. How does Revit determine this? The reason we discovered the issue was because we had a series of openings in the walls, set at 2'-6" above the level and the rooms kept "flowing" through. I kept raising the Bottom Offset until finally, at 4'-1", the rooms started behaving like I'd expect them. I also tried grouping the area in question and save it out to a file, but when opening this file, the system computed height went back to 0'-0", which indicates there's something in the project causing this. Once we set the Room and Area settings to "At Specified Height" of 0'-0", the rooms started recognizing their bounds and the areas calculated correctly. I've never had to change this manually before. Anyone run across this?
We also tried auditing the central file, resolved all warnings in the project pertaining to overlapping walls, room separation lines and rooms, but the issue remained.