Parameter Mapping#
Performance Rigging recognizes linesets and reads their data through shared parameters. Because different rigging family libraries name those parameters differently, the add-in does not hard-code parameter names — instead it maps each piece of data it needs to one or more shared-parameter GUIDs through a mapping file.
The mapping file#
The mapping is stored in:
C:\ProgramData\Autodesk\Revit\Addins\[version]\PerformanceBIM\RiggingParameterSettings.json
It is installed with the add-in and does not normally need to be edited. Each entry maps a logical name the add-in uses (for example, Lineset Distance) to a shared parameter definition — its GUID, display name, and data type — grouped by a parameter set.
Why it works this way#
The mapping lets one add-in support linesets built to several conventions. The file ships with multiple parameter groups so that families authored against different shared-parameter standards are all understood:
- A Performance BIM standard set (parameter names prefixed
PB_). - A TCC set (names prefixed
TCC_). - A public set using plainly named parameters.
When the add-in inspects a lineset, it looks up each value it needs across the mapped definitions, so a family that carries any one of the recognized parameter sets will work.
Data the mapping covers#
| Logical value | Data type |
|---|---|
| Is Lineset | Yes/No |
| Lineset Name | Text |
| Lineset Number / Designation | Text |
| Lineset Distance | Length |
| Use Dynamic Scheduling | Yes/No |
| Reference Plane Name | Text |
| Type flags — motorized, static, counterweight, stage drape, acoustic drape | Yes/No |
See Linesets and Lineset Types for how these values are used.
Edit with care
The mapping file is maintained by Performance BIM. Editing it incorrectly can cause the add-in to stop recognizing your linesets. If you need to support a custom family library, contact Performance BIM rather than editing the file by hand.