New SP3 Revit Builds Available – All co-released! (20071109_2345)

It has happened. All three releases on the same build at the same time! It is definitely time to upgrade and install! Learn about and download the latest builds using the links below.

Click on the Web Update Enhancement List links below to read about the changes and fixes provided in the latest builds.

Want to download the latest English builds directly?
Get it/them at Autodesk by clicking on these links:

Be sure to read up on the content changes. I guess the renaming wasn’t complete when they released the last build. Hopefully this will be the last.

It is a party now that all disciplines are on the same build….

Updated for 2008: Routine to Copy Layer Keys Between Layer Key Styles

Need to migrate your layer keys in AutoCAD Architecture 2008? I updated the routine to work in 2008. Get it here.

Blog relocated to blogspot temporarily

I’ve relocated BesideTheCursor to blogspot temporarily to overcome technical problems originating with IPower during the transition to a new server. Until direct ftp access is restored, you can access my blog at http://bsidethecursor.blogspot.com

Note: the e is missing from besidethecursor

Identify Revit Builds Painlessly

I thought you might be able to use a tool to identify what Revit build is sitting on your pc. If so, continue reading…

  1. Are you a CAD/BIM manager responsible for installing and updating Revit on multiple computers?
  2. How about a quick way to check all the Revit Build Numbers on each computer without actually launching Revit?

Sounds good right? Download the zip file containing a short vbscript routine and run it on each machine that has Revit installed. It will display a web page with all the build information for each Revit product installed. It will look more or less like the image shown below.

?

Want to capture info from multiple computers?

  1. Search the code for the following string: “c:BTCrevitbuild.log”
  2. Replace it with a path to file somewhere on your network.
  3. Make sure to create the file in the appropriate folder
  4. Every machine that runs the script will now append it’s info to the log file.

Lather, rinse, repeat….