Friday, May 29, 2015

Revit 2016 - Collaboration for Revit 2016 is Available

The 2016 version of C4R (Collaboration for Revit) is available now.

Click this to download or click the image for an overview


You'll need to visit your Subscription page to access the download to install it. Look at the Services page and it should be listed among whatever services you are entitled to. If you don't see it then you'll have to sort out your A360 account first.

This is the video they offer at the online help documentation site to explain how to initiate a project with C4R

Thursday, May 28, 2015

Revit 2015 Update Release 8 and New Project

When I click New under the Projects (or Family) list on the Recent Files page Revit is opening a new strange page instead of opening the New Project dialog.


That's a bit ridiculous...

If I rely on the Application Menu > New (Project/Family) the normal dialog appears. So for now avoid relying on the Recent Files page...

Revit 2016 Updates Redux

This morning I gave Autodesk Application Manager (AAM) another chance by removing it and installing it again. It reports a number of things requiring my attention; A360, Navisworks, Revit 2016 Extensions and AutoCAD OSNAP support. That's a bit more encouraging, it seems to be awake at least. In the past it just stopped caring about updates and didn't seem to find any despite Luke telling me otherwise on his blog.

The Revit Clinic has since provided a post with information regarding 2015 and 2016 updates.

I noticed that Revit 2016 now has Service Pack 1 installed. After a year of Release Updates we are now returning to language of old with Service Pack. Okay...

In a comment for yesterday's post Phillip asks why isn't there one update application that installs the necessary features based on what is installed...for each Revit version? Good question! They must be able to figure out what is installed and hopefully they know what is needed, better than me trying to figure it out from the information they aren't putting on the website at least.

Luke also followed up his previous posts with another regarding Revit 2016 Extensions (he's observed they are now being deployed via AAM), Space Naming Utility (now generically "version-less" wrapped up and delivered at Autodesk Exchange Apps). I'm still not sure where to expect to find Worksharing Monitor or the Collaboration for Revit (C4R) 2016.

After installing the 2015 update I find C4R is broken, it triggers the usual message that only a programmer's mother can love.

I'm glad that AAM seems to be working now but it is soooo slooooowwww installing updates. The Navis updates just report "installing" with no indication for the degree of progress while some of the others do. Consistent inconsistency. The updates for Navis and ReCap put fresh icons on my desktop where there were none. It's not hard to delete them but its rude to put something on the desktop that wasn't there prior to the update.

Grumpy but not as grumpy as yesterday...

Wednesday, May 27, 2015

Revit 2016 and 2015 Updates via What Revit Wants

Once again Luke has written posts about updates for Autodesk software before their own web site offers them...?!?

Thanks Luke!

I'd really like to see this stuff posted on their own bloody website(s) in a timely fashion!

Yes, Autodesk Application Manager is supposed to let us know (and it did for Luke apparently) but it hasn't worked on my computer except the first month it was installed. Oh and the Revit 2016 versions of necessary tools like Space Naming Utility and Worksharing Monitor are still missing in action. It's not like they didn't know a new release is out??!!?? Gosh I'm grumpy right now.

Luke's post about Revit 2016 Release Update 1
Luke's post about Revit 2015 Release Update 8 for R2 (note that's not the regular Revit 2015, he does provide a link to download that update though)
Luke's post about Collaboration for Revit (C4R) v5 for Revit 2015

I guess I shouldn't ask where C4R for 2016 is?

Wednesday, May 20, 2015

Create View Template - Tool Description

Oh so...subtle...

The command via the ribbon is called Create Template from Current View.


The right-click context menu offers this version of the command instead (Create View Template From View).


It's subtle because the right-click version is based on the fact that we've selected a view and used right-click. The context doesn't demand using the language Current View because it's based on the view we selected in the first place. The ribbon version leaves out the word View because it is listed as part of the View Templates button already. It also declares that it will create the template based on the Current View since it is possible to have accidentally changed which view has focus prior to using the command; for example if views are tiled or cascading in the drawing window.

My initial reaction was that they were inconsistent and wrong to use a different description for a command that will produce the same result. After mulling it over I think it is a reasonable subtlety since their use is different and the phrasing is intended to help us know what to expect in each situation.

Sunday, May 17, 2015

Revit 2016 - IFC Observations

Autodesk recommends that we visit Autodesk Exchange|Apps to download the latest IFC application before starting to work with IFC data.


While testing these features I exported some walls and doors to IFC 2x3 so I could import them as IFC geometry. When I used Link IFC there were Generic Model openings filling the door openings to provide room bounding geometry.


There is a bit more going on behind the scenes when we import IFC. In the past we had to open an IFC which created a Revit project file we could then link. Those extra steps are done for us now as a background operation. There are three files that Revit creates based on the source IFC we link.


If I get obnoxious and delete these files and then open my active project file I get a warning message that Revit couldn’t find a linked file. When I use Reload From and select the IFC file I linked in the first place Revit creates those three files all over again. In the background it’s really just referencing the IFC file named "Linking.ifc.RVT".

I then opened the .RVT file that Revit created during the Link IFC process and deleted the openings and replaced them with Room Separator lines. Rather than doing that we can just leave the Generic Model elements but we need to use a Filter to turn them off. Revit creates a shared parameter file based on the IFC data. We can create a Project Parameter using one of its parameters (ObjectTypeOverrides) so we can create a Filter focused on the Generic Model category.


Once we understand that we can use the same approach to override the appearance of the existing walls, doors and windows so they look more like existing elements.