BIM One have released a new automatic color filter addin for Revit. It is very simple to use, and its free:

  1. Install the addin using the install tool (refer here for steps on using the addin manager)
  2. Open a Revit project
  3. Go to BIM One ribbon
  4. Click on Color Splasher
  5. Click on a Category
  6. Click on a Parameter
  7. A color set is automatically generated
  8. Click on Apply color set

If we check the element VG, we can see that this addin basically runs through and applies a By Element override to each element in the view:

Note: a nice added bonus to the above functionality is that if you open Color Splasher and click “Clear Set”, every Element visibility override in the current view will be removed. Might be handy for QA and model management?

They have also provided a Element GUID tool. It works like the Select by ID tool in Revit, but instead of using the Element ID, it works on the GUID parameter inherent in all Revit elements:

I previously posted about the BIM One NWC Batch Exporter here:
NWC Batch Export from Revit – multiple Revit views to multiple NWCs with one click

via
http://us8.campaign-archive2.com/?u=f58c55b9516e3ecd984b6ff84&id=95df102b3a&e=3729ed9af6

For some projects, Revit Warnings become a metric in model audit processes (this may be regardless of how much impact those warnings may have in real terms). For example, perhaps your model has become populated with many “Elements have duplicate ‘Mark’ values“. How can we fix these quickly?

I explored a number of options, and I think I have found the easiest. In one particular situation, the Mark value was not important for documentation, and it was simply necessary to make them unique to clear the warnings. What if we could also grab some otherwise unavailable information and apply it to the item? Like Element ID or GUID?

Bonus Tools can do that. Here’s the steps:

  1. Get Bonus Tools
  2. Open your RVT model, check the Warnings dialog, and see what Category is affected
  3. In Bonus Tools 1 ribbon, start Copy Parameter tool
  4. Pick options as per screenshot below

After clicking Ok, the tool will quickly copy the unique ID into the Mark parameter. You can now tag it or schedule it (keeping in mind that it is a static value and may need to be updated from time to time). What I like is how quickly the tool runs – it can do an entire category of thousands of elements in a minute or so.

Note: you could also use Bonus Tools to:

  1. Export multiple categories to Excel using a Multi-Category Schedule – “Export Schedule to Excel”)
  2. Adjust the Mark quickly in Excel with autofill, and 
  3. Re-import to Revit. This method is a bit slower, but you can have more control over how the parameter looks, and you can span multiple categories with unique-yet-readable Mark values.

There have been various other automated ways suggested to fix this over the years, such as:
Automatic Numbering of Elements Within Revit 2015 – Cadline Community 
using element positioning

Revit OpEd: Duplicate Mark Values
using Model Review
 
UPDATE: Recent updates to Bonus Tools include

  • new “Show Warnings” tool (applies a temporary Hide/Isolate after you select a html warning export from Revit) and 
  • a “Renumber Categories” tool (select multiple elements on different categories and it will renumber all elements on those categories by pushing the Element ID into the Mark parameter. It is very fast)

Just installed CloudWorx (more on this later) and it had a GUID conflict with CADtoEarth – weird?  Wonder if the installer somehow couldn’t properly generate a unique identifier (see image).

In any case, Jeremy describes how to generate a new GUID over here, but I couldn’t find GUIDgen.exe easily on my XP 64-bit PC, so I downloaded GUIDgen from:
http://www.microsoft.com/en-us/download/details.aspx?id=17252

  1. Generated new GUID, copy to clipboard
  2. Open offending (ie. most recent) .addin file that caused Revit to show the error on startup
  3. Paste the newly generated GUID into the ClientID field
  4. Save the .addin manifest and restart Revit
This resolved the GUID conflict.