Showing posts with label Versions. Show all posts
Showing posts with label Versions. Show all posts

Monday, January 25, 2016

Revit Version Build Update and Service Pack Naming

Bill (Mr. BIM Thoughts) shared this subtle bugger with me the other day.


Oooh boy... so Revit 2016 R2 is called Update3 behind the scenes if you look at the Control Panel\Programs\Programs and Features > View Installed Updates and Revit 2016 R2's update is called Update 1 for R2...

Phew...just when I think I understand the naming...

Tuesday, January 12, 2016

Revit Version and Build History

Philip and Luke both mentioned this on their blogs so I'm just echoing their mentions of this recent development. Autodesk put together a list of versions and builds going back to Revit 2012.


It's important to keep everyone that works on the same Revit project(s) on the same version/build, perhaps this will help?

It was fun discussing (while talking to a friend on the phone) the version/build/service pack/update naming yesterday, he'd missed the recent Update Release 1 for 2016 R2...damn it gets confusing.

Monday, March 02, 2015

Saving Backward

It is a common question and the answer is no, Revit does not save backward, to an older version. 

People often regard saving a file from one format to another as a trivial matter. As software evolves and new features are introduced these new things have no equivalent representation in the older format. Even Microsoft Word or Excel warns us when we save a file to an older version and those are much simpler elements.

For example, when Revit Parts were introduced. If we could save to an older version that did not know what Parts are how should that transition be handled? What should the developers decide to do with them? What can they become and retain some usefulness?

With AutoCAD there are new features that can survive a trip backward, like Tables can be reduced to text and lines so it still looks like a table but is really less elegant than the Tables they came from. If the file is then saved in the most current version there is no "make me back into a table assumption" so fidelity is lost.

It is difficult to allow for forward saving (upgrading) too. Nobody is very pleased if they upgrade a file and something breaks. Saving backward is most assuredly going to break elements the more object oriented our design tools become and evolve.

Revit's founders chose to eliminate the complexity and development distraction of saving backward at the outset. Most software like Revit does too even if they don't acknowledge it outright. They may allow saving backward in concept but there is always some loss of fidelity or utility in the process.

Revit does permit exporting data to other formats to permit it being referenced in some way by other tools but it remains impractical to expect casual backward and forward file translation.

When Revit was introduced in 2000 it was a rental, we paid monthly and internet access was required. Using the latest version was expected, required. That's never changed even when Autodesk purchased Revit Technology Corporation in 2002. They just made it possible to buy a perpetual license like their other software. Conceptually though nothing has changed.

Autodesk has a legacy of customers who transition from AutoCAD where it is normal to ignore a new release for several years before upgrading. That is possible because the rate of change for AutoCAD has generally been much less aggressive than with Revit which is much younger and has different objectives. 

It is easy to have access to the latest version at all times, via subscription. Fwiw Autodesk recently announced that new licenses will soon be all subscription based (rental) going forward so the concept that Revit embraced in 2000 has come full circle.

I'm not always pleased with Autodesk's choices and how they affect me as a customer but no company is perfect. For example, I'm writing this post on an iPad that can't just give me bloody arrow keys (without an external keyboard). Instead I have to use a goofy fussy magnifying glass to reposition the cursor.


Tuesday, July 22, 2014

Revit 2014 Web Update 3

This is an echo of what other blogs have already mentioned because the new Application Manager for Autodesk 2015 products is blind to this previous version's update. You'd have to run Revit 2014 and have communication center enabled to get a prompt about it.

Revit 2014 Update Release 3 Release info
Revit 2014 UR3 (32-bit) (exe - 68327Kb) "one-box"
Revit 2014 UR3 (64-bit) (exe - 106583Kb)"one-box"

Revit Architecture 2014 Update Release 3 Release Info
Revit Architecture 2014 UR3 (32-bit) (exe - 68327Kb)
Revit Architecture 2014 UR3 (64-bit) (exe - 106583Kb)

Revit Structure 2014 Update Release 3 Release Info
Revit Structure 2014 UR3 (32-bit) (exe - 68327Kb)
Revit Structure 2014 UR3 (64-bit) (exe - 106583Kb)

Revit MEP 2014 Update Release 3 Release Info
Revit MEP 2014 UR3 (32-bit) (exe - 68327Kb)
Revit MEP 2014 UR3 (64-bit) (exe - 106583Kb)

Revit LT 2014 Update Release 3 Release Info
Revit LT 2014 UR3 (32-bit) (exe - 68327Kb)
Revit LT 2014 UR3 (64-bit) (exe - 106583Kb)

Wednesday, February 05, 2014

Open File Project Version Warning

I wrote a post in November that complained about Revit not asking if I really wanted to upgrade a project before going forward. In response Harry Mattison wrote some code (and I wrote another post) and made a solution available through his Udemy API class.

Since then I've used it so much that I've been starting to think it's part of Revit. I was using another computer the other day and was confused for moment when Revit didn't ask first, puzzled until I remembered..."oh, yeah...Harry's app isn't this computer". (sad face)

Well Harry has made a new version of the app available HERE and has decided to use a Pay What you Want approach as a test to see how well that works for him and us. You can read Harry's blog post and explanation of features HERE and here's his YouTube video.


Friday, November 08, 2013

Project Version Wish Revisited

Blogging, twitter and otherwise working "on the line" is cool!! I complained in a blog post just two days ago about not knowing the version of a Revit project file. Sean Burke via Twitter suggested the API might be harnessed to provide a solution, specifically tagging Harry of Boost Your BIM. Harry took up the challenge and within a few hours provided a solution and a video to demonstrate how cool working with the Revit API can be (yes Harry is cool too).

Here's the video he shared via his Blog Post response.


Harry's solution looks great and I'm off to download it!! Of course this means I'll have to whine on my blog more often.

Thursday, October 20, 2011

Don't be Double Clicker!

Should be no surprise, when software is installed a file association is created that links its special file extension with Windows. This allows you/me to double click on a file to open it with the correct application.

Revit versions don't distinguish themselves with a special executable file for Windows to recognize them as different, they are all just "Revit.exe". This means that Revit Architecture, Structure and MEP are the "same" when Windows sees a .rvt file (or .rfa, .rte and .rft).

Having more than one version of Revit (RAC,RST and RME) and/or having more than one release 2010, 2011 or 2012 for example is a recipe for problems. When you install just Revit Architecture, no problem. If you install a newer version Windows thinks the newer version is the "one". Double click on a 2011 file now and you'll likely be opening it with 2012 instead. If you install RAC first and then RST Windows will think every project is a RST file. It all boils down to wasting your time waiting for a file to open with the wrong version of software and having to do it over again.

Simple, don't be a "double clicker"!

Tuesday, November 17, 2009

Dept. of Subtle - Architectural Tools

When you get to use all three versions of Revit it is only natural to see differences. Here's one example, how the floor, ceiling and roof tools are made available in each version. First up is the Revit Architecture ribbon Build panel. You can watch a short video if you prefer.



Notice the nice ascending order? Floor, then ceiling and at the top Roof. It's even logical, or at least to me it is. Next is the Revit MEP Architect Ribbon and the Build panel.



This time around they are jumbled a bit and not in ascending order. They could be but they aren't. Roof is also off to the side at the bottom and Column is where Roof ought to be (could be).



Last is the Revit Structure Architect and Site ribbon tab and the Architect panel. In this case we just have Roof because Floor is elsewhere, part of the structural set of features and ceiling is deemed unnecessary. I suppose this sort of inconsistency doesn't really affect many users but they could be more consistent?



Wednesday, November 12, 2008

Want it all? What do you Buy?

What combination of Revit software will give the most with the least outlay of cash with the current Autodesk product delivery strategy? I believe that the answer is Revit Structure (RST) and Revit MEP (RME).

These two versions have all of the features that Revit Architecture (RAC) has spread between them plus there are compelling extensions for both whereas RAC has simply inherited its own from them.

It isn't really a coherent work flow to travel between the applications to do your work if you are an architect. As an example, you can't make a ceiling plan in RST but you can in RME. You'd have to use RME for full documentation purposes, not RST. At the very least you'd have to travel back and forth.

You might not even consider it efficient if you aren't. It would be more slickerer coolerer, Sweeterer (my opinion) if it were one seat of Revit that provided all the tools but that was a different post.

Schedules in RME offer both conditional formatting and embedded schedules, very useful and potentially interesting in that order. RST offers Graphical Column Schedules while RME and of course, RAC don't. RST also offers more tools to provide more accurate structural conditions like beam coping and curved beams.

Deployment would be a bit of a pain because you'd have to download the RAC content from the Autodesk web libraries and setting up templates might be a bit of a pain since you'd have engineering templates to work from instead.

I've experimented lately with not using RAC and favoring just RST/RME to see when I bump into something insurmountable, so far I haven't.

Perhaps Autodesk would recognize the value of a combined version if RME/RST sales began to cannibalize RAC sales? I was told that my earlier survey heavily biased the result by how I wrote the choices. I suppose but then what survey doesn't have a bias?

Something to consider. As usual be sure to prove it to your self satisfaction...your mileage may vary! Buyer beware...reader beware!

Thursday, October 19, 2006

New Builds for Revit 20060928_2300

A new build for Revit Building was posted on Friday night. The following information is from the Revit Building download page:

This build, (20006_0928_2300), addresses several upgrade issues discovered in Revit-based release 9.1 project files.

Issues related to the following areas have been addressed:

File inconsistencies stemming from the upgrade process
Behavior of Rooms with Plan regions
Improvements in snap to DWG
Filtering as it relates to the Save-to-Central function
Unexpected behavior when using the spacebar
Placing revision tables inside of titleblock families issue
Irregularities within the Keynote function
Inconsistencies when upgrading template
Issues with portable license utility

Download Link:

Revit Building

Friday, September 01, 2006

New Versions: Revit Building and Revit Structure

Revit Building 9.1 and Revit Structure 4 are now shipping. I waited to post this article until the Revit Building web downloads were posted. Revit Structure is still not posted, will post a link when it becomes available.

This release of Revit Building is best described as an "alignment" release whose focus is less on major features than fixing issues, performance and coordinating the behavior of all versions of Revit. People who are "wishlist" watching won't find a lot to be thrilled about for this reason. We will have to wait for the next full release for the next round of major improvements and/or features.

I'm am pleased with the subtle improvement to Elevations however. The addition of the wordy parameter "Hide at Scales Coarser Than" means we now have a level of control over the visibilty of these buggers that is long overdue. Here's hoping we get the rest next time!

Download Revit Building 9.1 HERE and just READ about it. (remember you have to choose your language, then you can select version (RB9.1 or RBS9.1) which to download.