Revit 2012 – massing & voids

This may seem rather obvious to the seasoned Revit user; but for the new kids on the block, when using voids to cut massing geometry in Revit, sometimes you need to think a little differently. The process of using voids to cut geometry can be a bit confusing. This is especially so, since the way voids cut in the conceptual massing tools is a little different compared with voids in say the in-place editor or family editor.. For instance, take a look at the image below. This was created by generating a freeform surface using the massing tools….then roof by face to generate the actual geometry for the roof.…it looks reasonably straight forward to achieve, but you need more then two voids to cut the initial massing surface.

Let me explain in more detail…..

So the surface was created using the massing tool, which consisted of a series of spline reference lines, then a surface generated between the reference lines. As indicated below.

Next up, a inner boundary & a outer boundary of reference lines where sketched. These will be used to form the voids which will cut the surface.

Now the natural logic here is to also create a large rectangle to go beyond the surface, like this…..

However, this is not going to work for us, because if you try & build the void, from the rectangle & trimming reference lines you are going to get the dreaded “Unable to create form element error”.

Instead, you need to create two voids from reference lines to cut away the excess surface. With a reference lines configuration like this.

The image below, hopefully explains it a little better.

All we then need is to create a void from the inner reference lines to cut the opening & we are good to go.

You may need to use the Cut Geometry tool to force the cutting.

I hope the above makes sense, I guess I should really do a youtube video to explain it in more detail, but this should at least give you some useful guidance.

Revit 2010 UI - a step forward or a step back?

There has been much discussion about the new Autodesk Revit 2010 UI. Some people like it, others hate it. It's a bit like marmite (vegemite to those outside the UK). However, the reality is that the UI in 2010 is changing and it will have an impact on our use of Revit from now and into the future. UI design is not easy, not that I have any particular experience myself, but my brother is a programmer and we have discussed this subject on a number of occasions. Therefore, I want to present the facts, the for's and against and then gauge your opinion. To some extent the UI has to change to make Revit look like the modern application it should be and the old UI from graphical appeal was looking dated. I know the background behind the change and a common look and feel across all the Autodesk applications was one of the primary goals. But the old UI did work and it worked very, very well. Having trained numerous architects in Revit over the last 6 years users always commented that they felt that the user interface had been built and designed by somebody who understood the architectural business. It was clean and easy to understand and everything was immediately accessible, unlike AutoCAD which could have multiple configurations. You only need to look at Sketchup to understand what I'm getting at, easy accessible icons that allow you to build great models, not that I am comparing Revit to Sketchup.

First take a look at this youTube video posted by Phil Read (yes, the Phil Read, ex Autodesk consulting and Revit guru). You should also read his post which supports this video. It is extremely funny but it does have a serious side and Phil puts this across very eloquently.

http://architechure.blogspot.com/2009/03/well-intentioned-road-paving.html

Now read this post on the Autodesk site and view the supporting video which explains the methodology behind the UI. It explains a little bit of the decisions making process and how the new UI works.

http://insidethefactory.typepad.com/my_weblog/2009/03/the-ribbon-process-in-four-minutes.html

Ok, so there you have it, two different viewpoints. I have an in the "middle" stance on this. I actually want to like the new UI, it makes Revit look better and if it looks better then the assumption is that it works better. Probably the wrong way to look it, but it's like driving a new car, if it looks cool, you feel cool. Although this is not always the case, as beauty is in the eye of the beholder. Design and detailing buildings is not a straight forward process, but it follows a certain number of rules and workflow can be divided into a specific set of task, looking at the new UI I don't think it always follows these rules particularly well. It seems to jump all over the place and can confuse the user. Certain elements are not consistent and this is annoying. In this current world economic slowdown, firms are looking at the bottom line, they can't afford to be unproductive. Previous releases of Revit allowed users to continue to work with the Revit that they know and loved, yet get to grips with the new tools when they have time, therefore no lose in productivity. This release will immediately affect firms if they deploy it, because the user experience is unfamiliar. As users get to grips, I guess this will improve, but there is no good explaining this to your CEO as he sees productivity dropping away. The world has changed, firms are watching productivity carefully, so impacts on workflow will not be popular at all. Saying that, this is not a good enough reason not to deploy the product. Take time to evaluate it, plan carefully, even consider running internal seminars to sow the seed of this release. You may actually find that your users are less worried about the UI than you may think. This certainly seems to be the case for the office I am working in.

It would good to get a readers viewpoint. Use the voting poll at the top of this page to let me know what you think. I will then publish the results in a future post.