Frequently Asked Questions#
Installation & Setup#
The Performance Rigging ribbon tab does not appear after installation.
Verify that the add-in is enabled in Revit → Add-Ins → External Tools → Add-In Manager. If it is listed but disabled, enable it and restart Revit. If it is not listed, confirm the installer completed without errors and that you are running a supported Revit version.
Most commands are grayed out.
The lineset commands run only in a project (model) document. They are disabled while you are editing a Revit family. Open a model and try again.
Linesets Not Recognized#
A command does nothing, or my rigging is not selected by the tools.
The instance must be in the Specialty Equipment category with the "Is Lineset" type parameter set to Yes. If either is missing, the add-in ignores it. See Linesets.
My family has the parameters but is still not recognized.
The add-in matches shared parameters by GUID through the parameter mapping file. If your family carries parameters from a library the mapping does not cover, the values will not be read. Contact Performance BIM to add support for your library rather than editing the mapping by hand.
Reference Planes#
A command reports "No Lineset Reference Plane Stored."
The current reference plane is remembered only for the session and is forgotten when Revit closes. Run Select Reference and pick the plane again before running the sync commands.
Some linesets were not associated when I used Select Reference.
With nothing pre-selected, only linesets within 50 feet of the plane that do not already have a reference are associated. Linesets farther away, or already linked to another plane, are skipped. Pre-select the specific linesets and run the command again to associate them explicitly. See Selecting a Reference.
Distances look wrong after I renamed a reference plane.
The link between a lineset and its plane is stored by name. Renaming the plane breaks the link. Run Select Reference again to re-establish it. See Reference Planes.
Duplicating#
Duplicate Lineset says the lineset has no reference plane.
Associate the lineset with a plane first using Select Reference, then duplicate.
My duplicated linesets landed on top of existing ones.
Copies are offset from the lineset you selected. If you duplicate from a lineset in the middle of a run, copies can overlap existing linesets. Duplicate from the last lineset in the run, or review and adjust afterward. See Duplicating Linesets.
Numbering#
Renumber changed numbers I did not expect.
Renumber applies to every lineset in the model and sorts purely by distance from the reference plane. If your model has more than one rigging system, they share one continuous sequence. See Numbering Linesets.
The renumber order looks wrong.
Renumber sorts by each lineset's stored distance. If linesets have been moved but their distances not updated, run Sync Schedule first so the sort reflects real positions.
Synchronizing#
Sync Schedule / Update Locations report nothing to do.
Both commands act only on linesets that are out of sync. If every lineset already matches, there is nothing to change — this is expected.
A lineset is ignored by the sync commands and the updater.
Only linesets with Use Dynamic Scheduling enabled are processed. Legacy linesets — older families without that parameter — are always skipped. Associating a lineset with Select Reference while it is pre-selected turns dynamic scheduling on.
Update Locations did not move pinned linesets.
Pinned elements cannot move. Run UnPin Linesets first, then run Update Locations.
Automatic Updates#
Linesets move unexpectedly while I work.
This is the automatic updater reconciling dynamically scheduled linesets. If it is not what you want, click Enable Lineset Updater again to turn it off. To investigate what it is doing, enable verbose logging and review the log.
Logging#
Where is the log file?
C:\Users\[username]\AppData\Roaming\Performance BIM\PerformanceRigging.log
Enable Verbose Logging in the About dialog for step-by-step detail when reproducing a problem.