BILT Speaker

BILT Speaker
RevitCat - Revit Consultant
Showing posts with label update. Show all posts
Showing posts with label update. Show all posts

Saturday, 25 September 2021

Revit 2022.1 So Good it Trashed the Installer

 Excited by all the hype about Revit 2022.1, I just downloaded and installed it.

All went well apart from a couple of minor glitches:

1 - Parallel Installs

It decided that it could not install more than 33%, and sat there for ages before announcing that it had failed due to some other install going on.  I have no idea what it was - some kind of system update, which required a reboot?

After rebooting the computer the install worked smoothly and quickly

2 - Trash the Installer

After completion, I decided to make a backup of the installer software and remove it from the hard-disk to save space - all 851 Mb of it.

Where the heck was it?  I searched high and low - in the Download folder?  In the Software folder that I had previously moved it to?  No.  

Eventually I found it in the 'Recycle Bin'.  How did it get there?


I may be getting a bit forgetful, but I surely would know if I had somehow deleted the installer?

Could it be that Autodesk have built this "Self-Destruct" capability into the installer?

Or could it be some new trick that Windows 10 performs?

Conclusion

If you want to save time, reboot your computer, and then make a backup of before installing this update.

Now I look forward to testing the new features

Thursday, 28 May 2020

Revit Callout Crop Boundary Mismatch



When placing callouts in Revit, it is a common situation that you might want the crop boundary on the callout view to be different to the view reference on the parent view.  Here is a typical example:
  • When a callout (eg. for a bathroom) is created, you typically leave a large zone around the walls so that the callout is clearly visible on the plan

  • When you go to the callout view, it has greater extents than required
  • If you adjust the crop in the view to be tight around the walls, to display as you'd typically like it on the drawing sheet . . .
  • it also affects the parent view callout reference - so the callout boundary is very hard to see on the drawing.

This is how Revit callouts were designed to work - but it does not allow you the flexibility to make your drawings look neat and readable.


The workaround solution that I would normally recommend is to create the bathroom layout views without usng the Callout tool (duplicate views, crop manually); crop them as desired; then use Callouts with 'Reference Other View'.
  • This allows you to have slightly different callout and view crop boundaries
  • Be warned that it does mean that the callouts will not automatically update if the view crop boundary is changed.

 More detail on this technique in a following blog post . . .

Friday, 22 November 2019

Travel Path Update in Revit 2020.2

Hooray - with the release of 2020.2, we finally have something useable in the Revit 2020 Path of Travel feature!

The initial release in Revit 2020 Path of Travel and Follow Up and the improvements in 2020.1 actually gave us a feature that was unusable in almost every situation.

It still has a number of limitations but at last we can make use of it to some degree.  What makes the big difference is the ability to add "Waypoints" anywhere along the path of travel.



You may remember (from my earlier descriptions) that when you place a 'Path of Treavel' by clicking the start and end points, Revit calculates the path for you - and you had little control over that, apart from choosing which elements form obstructions (or not).  Hence, in the standard Autodesk sample file, the path calculation was not able to determine that a sofa at a lower level should still be an obstruction:
Path or travel in v2020

In 2020.2, the calculation seems to have been slightly rationalised to give a more sensible path through the corridor to the north, but it still goes over the sofa in the split-level living area.
Path of Travel in 2020.2

Add Waypoints

We now have the ability to add (or remove) 'Waypoints' - this allows us to nudge the path to a more sensible course around the sofa.

If you need to make your path of travel orthogonal (as required in some jurisdictions), it can be done by adding enough waypoints - rather laborious but at least it works.


This is a very welcome addition to this feature.  However, it is still taking longer than the Daleks to learn how to manage stairs and changes of level in the building.
There is still no way to control the minimum width of a gap between obstacles (about 430mm or 17")

Friday, 23 August 2019

Dynamo Version in Revit 2020.1

Autodesk have just released Revit 2020.1, which is great news for MEP Revit users.  For the rest of us there are a few goodies (to be dealt with in another post), but there are implications for which version of Dynamo you are using:

As of Revit 2020, you (BIM Manager) don't get to decide which Dynamo version to use in that software, as it comes packaged in the Revit install, and subsequent upgrades.  However, in the real world, we are all still using and supporting Revit 2019, 2018, 2017 and if you are unlucky, 2016 & 2015 . . .

The compatibility between different Revit versions and Dynamo versions is quite complex.  Refer to my previous Revit 2020 Dynamo Version posts on this matter.
You can also refer to John Pierson's Sixty Second Revit matrix of compatibility

Installing Revit 2020.1

I have just installed Revit 2020.1.  It now automatically includes Dynamo 2.2.1

Logically you would want to have this same Dynamo 2.2.1 version installed in Revit 2017, 2018, 2019, 2020.

I would have assumed that the moment Dynamo is updated in Revit 2020, it would also be available to install in all previous Revit versions that support it?  In fact you would expect the dynamo version to be available well before it is pushed out in the latest Revit 2020 service pack/upgrade?

Well, is it?

I'm not entirely sure?

If you go to the Dynamo BIM downloads site, it lists all the versions available

Yes, it lists 2.2.1 - but hang on, that is only the 'DynamoCoreRuntime' version, not the full install, which only seems to be 2.0.3 (which is many months old).  My understanding is that the Core install is  only available for Sandbox (ie. Geeks, not average Revit/Dynamo users), which runs outside the Revit environment - so we can't install that in Revit?

Refer to Dynamo Core 2.2 Release
or A new way to get Dynamo Sandbox, which explains what it is:
         What is Dynamo Sandbox?     "Dynamo Sandbox is for package developers and other folks working with Dynamo code who want to stay up to date with the latest and greatest stuff coming out. Sandbox is Dynamo’s “Core” functionality distributed in a way that doesn’t interfere with other Dynamo installations and doesn’t require any other applications (except for a few windows components and some optional extras)."


So, how do we keep all our versions of Revit running with the same version of Dynamo?  Can someone at Autodesk help to explain this, please?

Could the Dynamo folks please have an explanation on the downloads site?  And maybe separate the Sandbox stuff?


Other New Features in Revit 2020.1 include:

Thursday, 18 April 2019

Path of Travel - The Dalek of Revit 2020

Path of Travel - New Feature in Revit 2020

One of the new features that is particularly relevant for architects is the 'Route Analysis' tool.  This works by placing point-to-point lines between the start and finish of a route in plan.  Revit will then analyse this and find the shortest route between the points, avoiding obstacles on the way, and it will place a segmented detail line along that path, in the chosen view.  The intention for this tool is to create such things as:
  • Fire Escape plans
  • Emergency Evacuation plans
  • Life Safety plans (USA)
Here follows a detailed analysis of the new feature:


Analysis of Route Analysis


The tool is found on the Analyse tab, called 'Path of Travel'

Once the tool is activated, the ribbon displays a Linestyle choice.  It defaults to a linestyle called 'Path of Travel Lines'

Step one is to draw a line between two points.




 Revit then thinks a moment and places a 'Detail Line' segmented pathway between the two points



The first thing you'll notice is that its really hard to see.

This is because the default linestyle is not set to what you'll most likely need.

Path Linestyle

The default linestyle is system defined, but unfortunately its name is not enclosed in < > brackets, so its likely to get lost in amongst many linestyles.

Go to the Linestyles dialog to change its global settings (Not to 'Object Styles', which might be your first instinct) - it  is after all, just a detail line.

  • Note that it cannot be deleted or renamed. 
  • You can change its Weight, Colour or Pattern
  • In this case I've just bumped up the weight to something really visible


You can also create some more linestyles to use for different kinds of paths - this is the nearest we'll get to creating 'Types'.

In this example you might want to distinguish between an escape path to Outside vs to a Stair:
  • The original line can be changed to 'Path to Outside'
  •  A new line 'Path to Stair' could be added
 

  • Revit will again calculate the shortest path (around furniture/fixtures)

 Notice how hard it is to read the direction of the lines. 


  • Sadly there does not appear to be anything the user can do about the dot at the start, or the arrowhead - neither of which are very distinguishable with heavy lineweights at any scale above 1:50 (is that 1" to 48' in imperial?).
  • Overlapping lines can be moved Backwards/Forwards




Update Paths

If the underlying geometry is changed, you may want to update the path

  • Select a path
  • Click on 'Update Path' on the ribbon
  • Revit will recalculate it




Move It 

I am quite sure this was not the design intent of the update command, but it serves to demonstrate some weird behaviour:

  • Select a path
  • Move it
  • In this example I moved it partially out of the building (keeping the ends inside)
 


  • Try the 'Update' command
  • It may or may not work



  • This may be your first experience of a very unhelpful warning that does not tell you why it cannot update the path
  • My instinct told me to try again, with the whole path kept inside the building

  •  This time it worked


  • A gold star to anyone who noticed that the path did not avoid all of the furniture - even on the very first attempt


Split Levels & Dizzying Heights

You may have noticed that this example is the Autodesk sample file - a perfect vehicle for testing, as it has a split-level plan:

  • The living area is 3 lower than the rest of the house - and this is where Revit has failed to pick up the obstacles.
  • The question is, does the furniture project high enough to interrupt the path?
  • A section shows that it should - just.

Just to be certain, we should check the calculation heights:

  • Click on the tiny, tiny Route Analysis settings arrow

  •  The lower height is set to a default value of 203.2mm (8") above the view associated level (upper part of split level)


  • This may be just above the furniture, so I tried dropping it to zero, then 'Update' the path
  • Computer says 'No'

  • Then I tried just above floor level, say 10mm, but it still failed
  • The lowest level it would let me go without failing, was 175mm, but it still did not pick up the furniture on the lower floor.

 I then set the lower height back to 10mm, and tried a new path:

  • This time the message was a bit more informative:


I still don't know what the problem is, but it is a bit of a worry that the Autodesk sample file has uncovered a problem or limitation in the software so easily.  I'll update this section when more information comes to light, from Autodesk.

[Edit - it seems that the only part of the sofa high enough to be in the analysis zone is the sofa back, which explains the initial problem - but does not explain why the update path does not work when you lower the analysis zone - Refer to this blog post for more detail]


The Dalek of Revit 2020

Whovians would already have guessed that these paths of travel cannot go upstairs (or down).  That is certainly going to be a limitation for some situations, not the least being split-level plans.

Properties

Each Path that you place has some interesting system instance properties


  • Strangely there is no 'Comments' property.  This is very unusual, as almost every other element type does have a system Comments property that can be used in almost any situation (Filter, tag, schedule, key schedule etc)
  • The only properties that a user can change are the Line Style and Mark
  • Time = Calculated time it takes to walk from the start point to the end point of the path of travel. Walking speed is set to 3 mph/1.34 mps (Read only)  [From help file - mps presumably means metres/second.  I'd prefer 5 kilometres /hour]
  • Length = Total length of all segments of a path (Read only)
  • The system properties can tagged

  •  And scheduled


  • From Room and To Room properties are labelled as 'Not Available'.  In the Autodesk help files, they are labelled as 'For Future Use', which is a promising sign for something to come.
It is possible to add your own Project Parameters to Path of Travel lines
  • These must be instance properties
  • If you try Type properties, the Lines category is not available


View Filters

View Filters can access the all the same system properties (except Count)

  • Path of Travel Lines can be filtered by such things as Length, which would be very useful for highlighting paths over specified limits.

  • Path of Travel Lines can be filtered by Linestyle, for separating different kinds (in the absence of Types)

Since Path of Travel elements are actually Detail Lines, they are view dependent, so it unlikely that you would want to hide them in a view, so its more likely that you would want to override properties.

However, you could just do that with Category overrides - so I am not sure you would use view filters for this, unless you want them with halftone.


Obstructions

The settings menu lets you remove categories from the calculation.  By default the door category is removed (checkbox ticked).
I would like to see the standard filtering ability for the category list (its missing from the dialog box)
  • By Discipline
  • Show only selected

Path of Travel Calculations

The Autodesk Revit Help Files have a section describing how the paths are calculated.  I am not quite sure I understand it all - particularly as it only seems to be talking about plans, rather than how it checks for obstructions in 3D.
Path of Travel Calculations

Conclusion

This is obviously a first pass at what should be a very useful tool at some time in the future.

I am very pleased that it seems like Autodesk have been careful not to tailor this tool to any particular country or style of doing Escape Plans / Fire Safety, which is a very good thing (NB. Area plan calculations are a real pain for anyone outside the USA, as an example of country specific coding).  In fact the tool is sufficiently general that it could probably be used for all sorts of other purposes.  Presumably the tools have been made available in the API so that developers can create country specific addons?

In its present format, it does have quite a few limitations, which will hopefully be addressed in future iterations:
  • The Dalek conundrum - how to get up or down stairs
  • No system 'Comments' property.
  • Type properties not available (in Project Parameters, or anywhere else)
  • Users nominate Start point and End point - it does not allow us to nominate any intermediate points that we want to go through.  
  • Perhaps Autodesk could create a way to link paths to allow this?
  • It is not possible to move either the start or end point individually - it seems like you have to recreate a new one if you get it wrong first time. 
  • What happens if you don't like the route that algorithm has chosen as the shortest route?  You may have good reasons for not wanting that route.  I would like to have the ability to either choose another option (Like Google Maps directions), or else to be able to nominate intermediate points, or even to be able to drag individual joint nodes between each segment.

Cartoon - With thanks to Birkett (Punch Magazine)

More On Path of Travel

Improvements to Path of Travel in point releases: