Custom Revit ini

Honour the settings in Revit

 

This article aims to help with some questions relating to the use of a custom Revit ini file.

The initiative to test and write this came from some questions raised to me in person and some existing threads online, dating back to 2015, about the ini file settings not taking effect when launching Revit.

The first question I had then was. Have the ini file been customised in a text editor only or was the settings set from with-in Revit? E.g. Family Template location set in the Revit options to be written to a blank FamilyTemplatePath line in the ini file.

When developing an ini file. The standard settings should be setup and written to the ini file from within Revit and then saved. This version of the ini file, stored in the users roaming location, should serve as the default ini file for a deployment or standalone installation. I.e. save that copy of the ini file from the user roaming location in to the UserDataCache location in the general resources on the network. Then delete the ini from the user roaming location and the ProgramData location.

My second question was. Is the Revit install based on a Deployment or a Standalone install?

If the installation is from a deployment you need to ensure that the installGUID value is defined and identical in the copy of the ini file in both the ProgramData/ UserDataCache and the users roaming location.

i.e. don’t edit the installGUID.

One issue that I had, and you might have come across, is that even if you have an identical InstallGUID in both locations. Still the settings are not picked up. Why? I don’t know. But What I did to fix this was to run a repair of Revit to generate a new ini file. I then copied over the custom ini settings to the new ini file generated from the repair.

I did copy over line by line and fired up Revit after each copy, but I never came across the root if the issue again. But Revit is now picking up the settings.

Once the ini file has been created and Revit deployed or installed on a single machine. The ini file should be copied (or deployed to all users via PowerShell) to the ProgramData/ UserDataCache.

When Revit is fired up, a copy of the ini file is saved to the users roaming location and the custom settings in the ini file should be picked up.

So, some key points:

  • Run a Revit repair to generate a new ini file with the InstallGUID
  • Copy the custom ini lines in to the new ini file. Generated by opening Revit and making the settings, as well as typing the lines for the settings you need e.g. Export file locations etc.
  • Save as a default ini file to the resources
  • Use for deployment
  • Don’t edit the installGUID
  • Make sure the PC have access to the network before you are testing. (that was 10 min I never get back!!)

 

#revit #ini #configuration #aecpeople