Move and Change Temp dimension have different warnings

[Anonymous]

I want to move a level when I use move command or changing temp dimension I have different warnings!

• Move command shows about 100 warning which some of them will delete objects
• changing temp dimension shows less than 10 warnings which are soft!

see the screencast

 does it have any concept on the background? should we use only temp dimension for these complex movings or it is a bug of Revit which cannot detect warnings for changing temp dimension?

Screencast will be displayed here after you click Post.

ca70cbbc-0f73-4e5f-a524-a033f633cc2a

[barthbradley]

You're changing the the elevation of a Level?  It's not usual that this would throw up a bunch of warnings.  Frankly, that's a good thing. Expand the warnings and inspect what is being affected.  Maybe you can ignore them all, but you definitely want to know about them before you proceed.  

[Anonymous]

Yes! My client Changed his mind. at the end of work, he asked to have less excavation!

If I use move command it will delete many walls!! but changing temp dimension only shows some overlap warnings. My question is: If changing temp dimension do the same job why they have this amount difference!? If I didn't use temp dimension I should redraw many walls!. It should be some differences.

maybe changing temp dimension doesn't manage all of movings or doesn't detect warnings or can handle objects better than move command.

My model at this stage has many objects if I use temp dimension is it any guarantee that I don't lose anything?

It should be clarified by developers.

[barthbradley]

Can't you just change the elevation of the level itself?    

[Anonymous]

There are many walls and objects which are based on that level and moving the level should change their property.

moving that level is possible by two methods 1- move command 2- changing the level temp dimension

according to warning and errors, these two methods don't have the same result.

Please take a look on the video

[Anonymous]

I tested. changing level's elevation shows warnings the same as changing temp dimensions. 

[barthbradley]

@Anonymous: I'm not really understanding. Are you saying that Revit is preventing you from changing the elevation, or just alerting you to the effects of making the change?  Either way; the Warning dialog box should be identifying everything, including giving you the effected Elements' IDs to use to find them, in case "Show in View" doesn't work.  

[Anonymous]

it doesnt privent me. i can move. if i use move command it will delete some walls. if i use changing temp dimention it doesnt delete any thing and only shows some warning. i know what is the concept of warnings and they are useful. i say way these two method acts diffrent?

[Corsten.Au]

Move ,Modify ( Constrain, Disjoin )

Theres a big difference between 

1. Changing temporary dimensions and

2. Moving any 3D element.

Moving any element gives two options before executing that command . 

a. Constrain and b. Disjoin..  ( total four combination, constrain on, disjoin on, both on , and both off )

These vary depending on the type of element... 

ex: something constraint to level or surface, Revit doesn't allow to move unless its " unconstrained " and so on..

probably thats why you are getting less error while changing temporary dimensions than moving the levels.

Best luck

[barthbradley]

@Anonymous: There's something that I don't understand. The client asked for less excavation; right? I would interpret that as meaning he wants to raise the whole building -- not just the basement floors. If so, wouldn't you just want to lower the Survey and Project Base Points?  

[Anonymous]

We have City By-Law limitations for pick of roof hight and first level hight also we have two basement levels. he asked to bring one foot upper the lowest basement level. I can not change the survey level's elevation because it will change the hight of the first level and pick of the roof.

[Anonymous]

So changing temp dimension for levels doesn't care about constraints because it doesn't show any errors or warning about them. also when I wanted to move I checked both of constraints and disjoin check boxs.

[barthbradley]

I understand @Anonymous. We have like restrictions on building height.  But there are codes governing "basement" construction as well.  I'm sure you took those into account as well.  Sounds like the client has really ham-stringed you with this last minute design change.  And, yes: I understand what lowering the SP/PBP would do.  That would only be an effective way to "raise" the entire building, which is what I was suggesting. Obviously, that's not an option because of Building Height restrictions.  

...how about a lower roof pitch?  he, he.  

[FAIR59 · Accepted solution]

I think you should leave disjoin unchecked.

from the Help:

Disjoin: Click Disjoin to break the association between the selection and other elements before moving. This option is useful, for example, when you want to move a wall that is joined to another wall. You can also use the Disjoin option to move a hosted element from its current host to a new host. For example, you can move a window from one wall to another wall. This feature works best when you clear the Constrain option.

Moving a level with disjoin results in walls loosing their "Base Constraint", and they get deleted. Deleting the walls results in deleting all the elements hosted on those walls etc etc. 

[Anonymous]

I checked the model as you said without disjoin the warning and errors reduced to 4 and 0 🙂