Revit Make Local

Installation

Download the AUGI Revit Launcher and unzip the contents into a folder on your computer or a network location. The files Revit Make Local.exe, Settings.ini and Logo.jpg are all required to be in the same folder. The other files consist of the uncompiled AutoHotkey script (text file), a Readme file and the icon used for the shortcuts. These files are not required to run the AUGI Revit Launcher.

How does it work?

The application lets users find the central file folder and then display RVT files that follow the naming convention shown on the application window. Once the user picks an option through the right-click context menu, it will then launch the correct version & flavor of Revit, create a local file (using the log-in username as a suffix) or a detached copy, and/or prompt to specify which worksets to open. By default a desktop shortcut will be created and used next time around to make the launcher run through the same process for the chosen project. This is the fastest way to work in Revit with local files.

The application performs various checks behind the scenes, such as whether a local file for the same project and user is already running, whether the correct flavor of Revit is installed at the paths specified in Settings.ini, whether the Central File in the shortcut still exists, and it also writes and checks the Revit Build info. against that of the project team. For further information, please check the Readme file.

Instructions

Application Window

1. Click the top-right button to navigate to the Central File folder.
2. A list of Central Files will be displayed.

Right-Click Context Menu

3. Right-Click and select an option. That was easy!

Next time, just double-click the desktop shortcut to repeat the same operation as you just did through the GUI. Note that you can uncheck the option to add a desktop shortcut (for example when you want to work in a project just once). Also, this default behavior can be changed (see Customization). The created shortcut name will be indicative of what action it performs. Hovering over it also reveals an informative tool-tip.

Shortcut

The Help Me! button will land you on this page. Clicking the AUGI logo will open up the latest Revit forum posts.

Build Checking

The launcher will check the Revit build and write it to Projects.ini. If you run the Detach option, Build Checking is not performed. Users with builds older than the project’s build will be warned and once the machine is upgraded, the message will go away automatically. By default Projects.ini is created in each central file folder. You can edit Settings.ini to supply a path for a centralized location of your choice. In this case only one ini file will be written and will contain all project information in your office or firm.

Below is a map of the build checking routine logic.

BuildCheckLogic

Customization

You can customize some settings by editing Settings.ini. Once you open the file (Notepad will work fine), read through the commented lines for more information. You can change the following Paths:

  • Local Files
  • Default path when navigating for Central File Folder
  • Projects.ini (when path is blank, it will be written to each Central File Folder)
  • URL when clicking the AUGI logo
  • Help Me! button URL
You can also change the following Defaults:
  • Application title
  • Shortcut behavior
  • Right-click context menu default option
The Revit install paths are not part of the launcher code and can be customized in settings.ini. If you don’t have certain versions of Revit installed, you can either remove the paths or the entire key (line). However you can also leave them there as the launcher still performs a check to verify if the application is installed.

Finally, if you find a problem or you have an idea for enhancing this little program further, please feel free to comment on this post or send me an email!


Share/Save/Bookmark

27 comments:

Matt said...

It would be great to be able to make all the shortcuts with out actually launching revit.

Dave Baldacchino said...

Thanks Matt, that's doable. You skip the part of the script that launches Revit under label "LocalOperations". A checkbox could be implemented and if the UI is onvoked it would skip that part. Then if the shortcut is launched, it would launch Revit. I'm curious as to why you would want this functionality.

Matt said...

This way the Revit project leader could quickly create the 3 shortcuts for the project and copy them to the Project directory. In doing so any new team members joining the project would just have to navigate to the project directory and copy whatever shortcut they need and they would be ready to start working.

It's not that your tool is hard to use, I actually find it quite easy, but there are always some users that just want to click and go.

Dave Baldacchino said...

Gotcha, but why not just let the users themselves use the tool to navigate to the central folder, pick their file and launch it? That creates their desktop shortcut automatically and then it'll be business as usual. I'm not seeing why having a project leader create a shortcut and placing it in the Project folder which the users have to navigate to and copy & paste to their desktop is any better than the above.

Thanks for your feedback though!

Anonymous said...

I tested on prior jobs in 2009 but having trouble with a new 2011 Revit Structure file. File name as shown:

Colorado_Judicial_Complex_Garage_S_11_Central.rvt.

The Revit Structure 2009 files are named the same way so not sure whey 2011 do not lanch.

Thanks

Dave Baldacchino said...

There should be no space between the S and 11 (no spaces, underscores, dashes, etc. Should just be S11).

Anonymous said...

Hey Dave,

I was trying your little tool but am having problems. We have installed Revit under C:\RMEP2010_64.
When I go and modify the Settings.ini to that location. I keep getting the following message:
Revit MEP 2010 is not installed at the path specified in Settings.ini.

I also tried this: "C:\RMEP2009_64\Program" just in case it was looking for the Revit.exe file but still the same.

I tried all kinds of namin conventions for the central file. Here is the latest 1234_M10_Central.rvty

If I modify the "M" to "MP" in the Settings.ini would that allow me to name my file ...MP10..., instead of M10?

Thanks Dave.

Regards,
Plamen Hristov

Dave Baldacchino said...

Plamen, your path is incorrect. It needs to end in a slash. So it needs to be C:\RMEP2010_64\ if that's where Revit is installed (where the folder "Programs", "Journals", etc. are located).

As to the naming convention, you can use MEP11 if you want. The application will only look at the three charactwers from the back and assess for that. In this case it'll read "P11", which will launch Revit MEP (M, E or P all launch Revit MEP), version 2011. All this is built into the program code and settings.ini expects a one letter discipline designator. So in your example if you want to use MP10, that would be fine as Revit will launch the application associated with "P10" (3 characters from the right).

Melanie & Matt said...

I'm wanting to find an easy way of checking what build of RAC is installed on multiple PC's (nothing to do with Central files, just the install) - is this possible with this utility?

Dave Baldacchino said...

The build checking routine does that. Obviously you have to have everyone use this little app. on workset enabled projects. Otherwise take the build checking routine into it's own file, make necessary tweaks and run it on each user's machine (maybe call it from the logon script). It should then write the info. out where you want it.

Will said...

I'm looking forward to trying this out but got a consistent error saying that Revit 2001 could not be found and would I like to try another version.
I had to insert the following into the settings.ini file to get it to work:
A01=C:\Program Files\Autodesk\Revit Architecture 2011\
etc etc

Dave Baldacchino said...

You must have named your Central file incorrectly...A01 does not exist :) You probably mean A11.

WILL said...

The script is going to work for Revit 2012

Anonymous said...

Hello Dave we are having the "Revit Make Local" icons on the user's, MS Windows 7 x64 bit OS, desktop disappearing!
So they recopy the icon to their desktop create the project icons and during the day specifically the "Revit Make Local" and all project icons are gone. Any Ideas? Thanks.

Dave Baldacchino said...

Are Revit project icons disappearing? I honestly don't know why the Revit Make Local icon would disappear.

Anonymous said...

After several attempts and getting it to see my Revit 2012 installation, All I get is a failed to open document and the folder for the detached central file is empty.

Any Ideas

Dave Baldacchino said...

Not sure what's going on as I have not tested for 2012 (pretty much don't use the app anymore). I'm not understanding what you mean by "the folder for the detached central file is empty" as the file is not copied when you pick the detach option.

Anonymous said...

First off, Thank you for this tool! Is it possible to have a backup file created each time this is launched on a per day basis? Basically, an archive copy on the local drive. Could a radio button be added or user prompted to make backup?

Dave Baldacchino said...

Hi, thanks for your comments.

Yes, this could be coded if needed. However keep in mind that the current implementation places the old local file in your Recycle Bin. So as long as you don't empty your Recycle Bin, unlimited "backups" are technically stored there.

Ben Fitch said...

I have been using Revit Make Local for some years now. The main reason I continue to use it is to make sure that users open projects in the correct version of revit so they don't get accidentally upgraded to a version the rest of the team is not on. However, the script doesn't work with 2014 because there are no separate disciplines of Revit any more. It's just Revit. I guess there is a way to fix the script, but I just wonder what most people do to deal with this issue...
Thanks,
Ben

Dave Baldacchino said...

Ben, it shouldn't be a problem. You can still keep using the same discipline naming convention for your models and just have the ini file point to the same installation path for all disciplines.

Plamen.Hristov said...

Dave,

Are you planing on updating the script to work with 2014? We also have been using it for a few years and would love to continue using it.

P.S. 2013 is working but it doesn't answer the first message that users have to Ok. Not a biggy, but if you are looking into updating it, would be nice to get that incorporated too...

Plamen

Dave Baldacchino said...

Hi Plamen, I've received several requests and even got cornered at RTC a few times, so I guess I'll update it as soon as possible and will post back here.

Plamen.Hristov said...

GREAT! Thank you Dave!

Dave Baldacchino said...

An updated utility (V5.1) has been posted.

Ben said...

Dave,
Thanks a ton for fixing Revit Make Local! It now works great! It was a pleasure to actually meet you at RTC after following your blog all these years. Thanks again!
Ben

Dave Baldacchino said...

You're welcome Ben, nice to meet so many Revit enthusiasts! Enjoyed chatting with you and I'm glad this little tool will keep being of use to some for at least another year :)

Post a Comment