![]() And those hundreds of views? They are now free and not controlled by your Scope Box. So, it works like a copy and delete command? Brr.Įven scarier – try to rotate the Scope Box using the Rotate command with Disjoin checked – it will now rotate but also become a new Scope Box without you noticing. It will move but at the same time become a new Scope Box – and your views are now not controlled by the Scope Box anymore. ![]() Now try to move it using the Move command with Disjoin checked. Imagine it’s controlling hundreds of views in your model. This bug with Scope Boxes is more than concerning.Ĭreate a Scope Box, lock a view to it. They are truly the hero of Revit – and everyone has opinions about them – “why don’t they snap”, “why are they only boxes”, how do I schedule them” and so on. I have a strange relationship with Scope Boxes – perhaps from my applications. My inner Tuvok/Spock is greatly concerned. Unless you do the same without Disjoin checked which logically can be described as “confusing”. Now try to rotate the desk using the Rotate command with Disjoin checked – it will not work. Over the years that have given rise to many strange things. Although it’s just a normal, everyday Level based family. Following old and strange Revit behaviour the family is now not really hosted to a Level but hosted to the Floor, or rather – hosted to a 3D Face on that Floor. This one came from a customer – place a loadable family (like a desk) on top of a floor. Place a Legend View on a Sheet and then try to use the Move command to move it with Disjoin checked – you will get a strange error message: “Sheet Views cannot contain more than one instance of the same view” – so Move with Disjoin checked basically works like Copy?īut the scary thing is that the original Legend view is now Deleted – it’s gone from the Sheet. Revit links forgetting their Shared Site (Move and/orRotate with Disjoin).Scope Boxes becoming new Scope Boxes (Move and/or Rotate with Disjoin).Unable to rotate loadable families (Rotate with Disjoin).Legend Views disappearing instead of moving on Sheets (Move with Disjoin).But why haven’t I noticed it before during +10 years working and supporting customers with Revit?Īnyway – dangerous in only Revit 2022 or all versions, doesn’t matter – be careful with Disjoin! So what are the “bugs” or surprising behaviour I noticed so far? Has it always been this way with Revit? Perhaps. And I especially noticed this with Disjoin. In Revit 2022, the application now remembers your settings more than before and options which were not that often used before seems to be remembered and checked when you least expect it. And I suspect it all boils down to this tiny little new feature (or improvement) in Revit: Remember Modify Tool Settings ![]() But in Revit 2022 for some reason Disjoin have started to give me headaches and troubles like never before. And it all comes down to one thing – that little checkbox saying “Disjoin”.īefore I never really used Disjoin – except for separating walls from other walls. Support requests from customers and claims of strange bugs turned into several personal encounters with surprising results. During the last couple of weeks I’ve started noticing a series of strange behaviours while working with and supporting Revit 2022.
0 Comments
Leave a Reply. |