Floor problem when moving walls...

[kpaxton]

OK, now I get a turn to ask a problem question....

I've enclosed two images showing a before and an after of what is happening. This is a small problem and I think I've already solved how to get it my final outcome to work correctly, but it's the larger issue of what should it be doing that concerns me.

• I have created a couple of rooms - a laundry room, powder bath and a small mechanical closet, adjacent to a larger Media room. (see Before jpg)
• In these rooms, I created a second floor (1/8" on top of the main 'structural' floor) to represent the tile flooring etc. We've done this with much success in the past.
• I create these floors using the linework tool - NOT select walls. These lines are not locked to any wall, so they can 'float'.
• The N-S wall between these rooms and the Media room was one wall - I used the Split wall command at the Powder room wall.
• After splitting, I gabbed the bottom grip of the PWD wall and dragged it over to the right, hoping to angle this wall about 60 degrees.
• Off the bat - I get a "Floor Sketch Invalid" error - for the floor in the Laundry room!!! This is for a wall that goes beyond the 70 degree mark.
• I try a smaller angle (74), which allows the wall to be moved, but the floor in the Laundry floor... well.. moves. (see the After.jpg).

If these floors are not locked or aligned to the walls, why are they behaving as if they are??? I have found that if I delete the LDY floor to clipboard (Ctrl-X)- move the PWD wall - then paste the LDY floor back into the room, it (looks) fine.

Thanks for your replies!
Kyle

[DanielleAnderson]

I've been complaining about this since I started using revit. Why do floors move, or adjoining walls, when you move a wall? why! why! why! The only way I have found to get around this is to copy the wall and delete the previous one instead of just moving it. You can get around a little bit of this if you pin your exterior walls, but not all of it. It is so difficult when teaching people how to use Revit to get them excited about the software when they find these sort of glitches all on their own.
All I can say is try using the copy command, and I hear your pain.

[Scott D Davis]

Have you tried checking the Disjoin button in the Options bar after selecting the Move tool, but before you move the object?

[DanielleAnderson]

Okay Scott, I'll put on the "I'm an idiot" tag for a while, but I gotta tell you, I"ve asked around and no one in my office picked up on that disjoin button, for 2 whole years! Just goes to show there is always something to learn.

[Scott D Davis]

It's okay, we all miss some! That's why i stress to my office to watch two things in Revit very carefully, especially in the beginning: the Options Bar and the Status Bar. The Options Bar changes for every tool. The Status Bar reports very important infomation back about the object you are highlighting, or the "next move" for the selected tool.

[kpaxton]

Thanks Scott -
I appreciate the assist and I will try your hints in the future. I've since went back and redesigned the space, so it changed anyway...

But I don't think my original WHY was answered (it may never be).... and that is... if I had split the wall, and even pulled these two walls apart... why do I have to manually disjoin these two objects?? oh .. and WHY were these associated with one another anyway? Is this something inherent in the floor tool? that if there is a wall nearby... stick to it? (I'm being very fascicious, but it's cloaking an honest question)

Thanks again for the tip - I watch that damn bar all the time... just didn't know I HAD to do something...

Kyle

[Scott D Davis]

its true, there is a built in assocation between the floor and the walls, because when you drew the floor, you probably picked those walls to draw it. It's an "implied" constraint. The same as if you draw two walls in a "T" if you pull the top part of the T upward to make a taller T, the leg of the T extends with it, even though you never locked it or told Revit to keep those two things locked together.

[Rols]

I think Scott's getting pretty warm. It seems to me that Revit pays very close attention to Osnaps, especially in the family editor. If you chose the intersection or endpoint of one of the walls as you sketched your floor, Revit will use that osnap as a constraint. Or, at least that's the theory.
These behaviors have driven me crazy on more than a few occasions. I think it all goes back to Chris Zoog's "6 steps to the Zen of Revit", number 6: Learning what Revit likes and dislikes. (to paraphrase)

[aaronrumple]

Watch the move command with disallow join when you are deep into CD's. If that is used - associated dimensions will be deleted and you'll have to track down what is missing.

[kpaxton]

its true, there is a built in assocation between the floor and the walls, because when you drew the floor, you probably picked those walls to draw it. It's an "implied" constraint. The same as if you draw two walls in a "T" if you pull the top part of the T upward to make a taller T, the leg of the T extends with it, even though you never locked it or told Revit to keep those two things locked together.

Yeah, I can understand that. However I did NOT use 'pick walls' to make my lines. I did, however, use the linework arrow (or pick entity) tool and used the interior face of the wall as my pick - Are you saying this is essentially doing the same thing as picking the wall and having it associated? ...As opposed to using the just the linework tool and drawing the boundary by hand? C'est La Vie, no?.

-Kyle