A note on C4R Update 9 and Revit2015Update12: Users of A360 Collaboration for Revit may experience an error on Revit startup if they install the Revit2015 R2 UpdateRelease12 but not the corresponding A360 Collaboration for Revitupdate, version 2015.9. The error dialog will reference the following: File name: ‘Autodesk.RevitServer.Versioning.Client,…..
To continue using A360 Collaboration for Revit, close all sessions of Revit, then download and install the Collaboration 2015.9 update and restart Revit.
To stop using A360 Collaboration for Revit, uninstall this program via the Programs and Features functionality of the Windows Control Panel.
I’m sure you have probably seen this message before: Can’t editthe element until ‘problemUser’ resaves the element to central and relinquishes it and you Reload Latest
This may be caused by one of your team members not syncing with Central, and then experiencing a crash, or just logging out and going home. Before you send off an angry email, perhaps you could use one of these methods to get rid of the element locks and keep being productive. Method 1 is a bit more disruptive to a large team, while Method 2 is a bit more ‘hacky’. Important: Both methods will mean that ‘problemUser‘ has lost their work and will have to redo it.
So, maybe Method 0 is ‘call problemUser on the phone’ and see if they want to come back intothe office to try and sync their work back to Central… but if that isn’t an option, you may have to use one of these methods:
Method 1 – Recreating the Central File:
Notify all team members to Sync with Central and Close Revit
Make a copy of your current Central file and _backup folder and put it somewhere for safekeeping
Detach from Central
Save As Central – overwrite the same file
Notify your team members to open the model again, using ‘Create New Local’ tickbox
Method 2 – Using a Known User Name to Relinquish Element locks
First, make a note of the user name that has the lock. In the image below, it is ‘rds check3‘:
Open a new Revit instance and set that as the user name in Options:
Open the model normally (Create New Local) under that user name, and immediately click ‘Relinquish All Mine’…
… and then Synchronize with Central. The element locks should now be gone.
In one of the other model instances (ie. your own user name), you can now Sync with Central… (or Reload Latest)
… and you can successfully modify the element that was previously locked.
As usual, the best idea is to do What Revit Wants and Sync with Central regularly so that lost work is minimized.
You would like to assign OmniClass numbers using the 2012 standards but are not able to because the default file shipped with Revit provides numbers from the previous standard.
Symptom: When trying to assign OmniClass 2012 numbers in the family editor the numbers supplied from the table are incorrect.
Issue: The OmniClassTaxonomy.txt file installed with Revit is an older version of the table. The file installed with Revit needs to be replaced with the updated OmniClassTaxonomy.txt file which can be downloaded here.
Solution: Download the attached file and follow the procedure to update the file in the Revit installation.
Note: The AppData folder is a hidden folder, so you need to first enable the viewing of the hidden folders on your system before performing the procedure.
Navigate to C:Users\AppDataRoamingAutodeskREVIT Example: “C:Users\AppDataRoamingAutodeskREVITAutodesk Revit 2015”.
Rename existing “OmniClassTaxonomy.txt” to “OmniClassTaxonomy_bak.txt”.
Copy the downloaded file to this location. Repeat this processfor each user on this local machine.
In addition, copy the file to the following location. This step ensures that any new future users of this computer will get the updated file. C:ProgramDataAutodesk\UserDataCache Example: “C:ProgramDataAutodeskRVT 2015UserDataCache.
Repeat process for each Revit product installed (RAC, RME, RST….) as needed.
Note: When using the updated OmniClass file, category sorting is not available. You must manually navigate to the correct category to assign an OmniClass number.
When setting upViewFilters in Revit, you can only select Filter parameters that are ‘common‘ among the Categories that you have ticked… If I haven’t lost you yet, here is a quick way to build aViewFilter that uses a custom parameter (like a Shared Parameter) and works across all possible Categories.
Firstly, add the Shared Parameter toall Categories using Manage – Project Parameters
Create a new Filter
Tick one of the top Categories in the list, and choose your desired Shared Parameter as afilter criteria
Now, start ticking the categoriestoapply this to one by one…
As you go down the list, Revit will occasionally give this prompt: “The selected set of categories requires that the filter criteria be reset“
When you see this message, click No, and then move on to ticking the next Category
In this way, you retain you Shared Parameter as aFilter Criteria for as many Categoriesas possible…