Knowledge Base ​>​ ​Announcements & Release Notes ​>​ EVOLVE Mechanical 9.2.0

EVOLVE Mechanical 9.2.0

Updated 2 days ago by Jason Earl

Resources

Compatibility

  • Autodesk® Revit® 2023.1.8
  • Autodesk® Revit® 2024.3.4
  • Autodesk® Revit® 2025.4.4
  • Autodesk® Revit® 2026.4

Summary

EVOLVE Mechanical 9.2 summary

Update Training Course

To learn all about the new update complete the training course below on EVOLVE University

INSERT LINK HERE

Upgrade Notices

The following configurations require migration updates to their format. Updates should be performed in order to ensure configurations will continue to work as expected in future releases.

Unless otherwise noted, the required migration can be performed simply by opening the respective configuration dialog and clicking OK/Apply. After updating, these changes should be checked in via Worksharing Sync.

  • Renumber (per project per user)
  • Smart Bends (per project)
  • Workset Manager (per project)
  • Location Sheet creation has been moved to sheet manager and the corresponding settings will need to be configured in the sheet manager settings from version 9.0 forward.

Configuration setting incompatibilities

Some feature's project configurations may not be compatible with previous versions. To prevent compatibility issues, all project members should be on the same version.

🎉New

  • #1584 Add support for load count parameter on family hangers
  • #1747 Add filter to Location settings to allow exclusion of Clearances and other elements
  • #1811 Utility methods have been exposed publicly
  • #1849 Add Location column to Point Manager
  • #1881 Add Find and Replace to Bulk Update
  • #1890 Add the ability for verified trusted PowerShell rules to run without prompt
  • #1944 Add enhancements for Restore Configuration
    • Add feature name and project or user scope as grid columns
    • Add ability to specify source directory for configurations
  • #2014 Add the ability to set multiple parameter values from a single Parameter Sync rule

👍Improvements

  • #1826 9.2 Content Changes
  • #1827 Rename Family Browser to Content Browser and make UI updates
  • #1842 Annotation improve tag speed in large models
  • #1847 New User Experience Enhancement
  • #1870 Stop Modify Package merge mode repeating until canceled
  • #1885 Change Renumber options into a radio group with a default automatic option
  • #1971 Make Configuration Exchange overwrite existing entries on import
  • #1972 Update reports 'Split' function to support sorting
  • #1974 Remove Language option and always run in English
  • #2008 Remove Roles from current version
  • #2023 Allow Data Profile multiple column sourcing scripts
  • #2025 Sheet Manager - Update Location Column to Location Id
  • Do not flag analytics feature use for signed/trusted rules

🔧Changes

💪Stability

  • #1687 Fix orientation of Box Outs differing between primary and linked models
  • #1713 Fix Toolbox and Custom Ribbon Tabs ordering incorrectly when editing
  • #1721 Fix missing validation on User and Project Tags
  • #1732 Fix for Add/Remove Union when a Flange is defined in the routing preferences
  • #1743 Fix P-Trap size error
  • #1746 Fix elements not being aligned properly in sheets after sheet generation
  • #1761 Make Connect Offset Orientation Independent
  • #1782 Batch Exchange select dependencies multi-group Bug Fix
  • #1797 Fix Part Encoder "Refresh Current View" processing entire model
  • #1802 Fix Select by ID not working when used from Toolbox
  • #1846 Fix Project Tags validation including Global Configuration items
  • #1857 Fix Import from Excel showing overwrite warning even when only adding new entries
  • #1858 Add MEP Fabrication Pipe/Duct categories to Insert/Connect Offset Selection Config
  • #1860 Fix Sleeve Settings linked model warning appearing incorrectly when loading existing configuration
  • #1865 Fix Insert Offset leaving elements slightly angled in certain scenarios
  • #1869 Fix PowerShell disabled message appearing multiple times in certain contexts
  • #1871 Fix Add Fitting not merging created parts into existing spools
  • #1875 Fix Extend and Align not working on certain geometry
  • #1886 Operation Canceled Exception for Pick Objects catch update
  • #1891 Fix Spools incorrectly asking to save changes before generating sheets
  • #1913 Fix default Point Family not loading when overload not defined
  • #1915 Fix Multi-Trim not working on very slightly unaligned elements
  • #1923 Fix sleeves being placed incorrectly after moving linked document
  • #1925 Fix error when using an Element Filter via hotkeys
  • #1927 Fix Insert Offset not working on vertical elements
  • #1937 Fix interaction between spools and packages locking up Revit
  • #1939 Fix crashes and temporary views when using Renumber
  • #1942 Fix error when View Template updater processes a template applied to too many views
  • #1946 Fix Hanger Configuration not updating Hardware Size selections when changing type
  • #1947 Fix incorrect or missing help and video links
  • #1957 Fix behavior of Login Dialog when 'Stay Signed In' is unchecked
  • #1970 Fix sleeves failing to place when linked model is stored in cloud
  • #1977 Fix Assign Level copying Fab Parts to the incorrect elevation
  • #1986 Fix UI elements being cut off in Selection Configuration dialog
  • #2005 ITM Hanger Placement - Elements with a slope greater that 1/4"
  • #2010 Fix Hanger Placement seeing couplings as a change in direction
  • #2015 Point Manager duplicate point on auto renumber Fix
  • #2022 Global Config closing causing error fix
  • #2032 Worksharing config fix

📂Content Updates

🎉New

  • Added support for Cast Iron No Hub:
    • Added eM_Cast_Iron_No_Hub_Sch_40 to eVolveSystemFamilies.rvt.
    • Added (19) Cast Iron No Hub pipe fittings.
  • Added eM_Tag_RFA_Pipe_Angle tag.
  • Added eV_ASM_HW_Threaded_Rod.
  • Added Point Load Shared Parameters:
    • Added eV_Point Load Count shared parameter to the shared parameter file in \Resources\Content.
    • Created new Point Loads group.
    • Added eV_Point Load Estimate to eM shared parameter file in Point Loads group.
  • Added seismic support Evolve Tools shared parameters.
  • Added Nested_Seismic_Plane.rfa.
  • Parameter Sync:
    • Added eV_Rod Length Rounding to the eV_DefaultConfigurations.eVGlobal file.
      • Replaces the (4) previous rod length rounding rules.
    • Added eV_Rod Length to system rules.
  • Added eM Global Signature File.
  • Added eV Global Signature File.

👍Improvements

  • Channel trapeze hanger updates:
    • Added seismic support.
    • Added auto-place strap support.
  • Hanger family updates:
    • Added eV_Point Load Count.
    • Additional additional customization options for the mounting attachment.
    • Default rod length rounding value set to 1".
    • Added support for the new Rod Length and Rod Length Rounding rules.
    • Affected families:
      • Angled Channel Trapeze
      • B2B Channel Trapeze
      • Single Channel Trapeze
      • Trapeze Template
      • Cable Hanger
      • Clevis Hanger
      • Clevis Roller Hanger
      • J-Hanger
      • Saddle Duct Hanger (Cable)
      • Saddle Duct Hanger (Rod)
      • Swivel Ring Hanger
      • Trapeze Roller Hanger
  • Updated the Terminal Unit equipment family to support the new rod length and rod length rounding rules.

💪Stability

  • Added missing nominal size validation to saddle duct hanger (Cable).
  • Fixed an issue with the Spot Slope Arrow Tag & Spooling Configuration:
    • Updated Family Name in DefaultSpoolingConfiguration.xml to match Tag prefix.
    • Added Tag prefix family into folder.
    • Updated 11x17 Pipe Spool Titleblock SubCategory from Locations to Spools.
  • Fixed an issue with eM_Tag_RFA_Pipe_MultiTag:
    • Updated family label to use new spot_elevation_bottom and eVolvePartSizeText parameters.
    • Updated family in Primary \Resources\Families folder.
  • Fixed an issue with the project template file including EVOLVE configurations.
  • Deleted eVolve_Version from Project Parameters in the project template file.
  • Updated the cached parameter group for the following parameters to Construction:
    • Trapeze_Rod_Center
    • Trapeze_Rod_Offset_1
    • Trapeze_Rod_Offset_2
    • Trapeze_Rod_Offset_3
    • Trapeze_Rod_Offset_Bottom
  • Fixed an issue with part sizes and part descriptions by changing the rounding of Pipe Size in Project Units in the project template file to 1/16".
  • Parameter Sync fixes:
    • Added support for the parameter eVolve_Parameter_Sync to the element filters for Attachment Part Description and Hardware Part Description.
  • Updated Channel Trapeze families to use current standard of Trapeze_Rod_Center for future usage.
  • Changed the center rod parameter in Channel Trapeze families from Type to Instance.

🧠Technical Notes

API Notices

  • New API methods
    • eVolve.Core.Revit.ProductInfo.API.ProductConfigurationFolderPath
    • eVolve.Core.Revit.ProductInfo.API.RegisterExpansionPathMarker
    • eVolve.Core.Revit.ProductInfo.API.GetExpansionAwarePath
    • eVolve.Core.Revit.ProductInfo.API.GetExpandedPath
    • eVolve.Core.Revit.ProductInfo.API.RegisterGlobalConfigurationPath
    • eVolve.Core.Revit.ProductInfo.API.UnregisterGlobalConfigurationPath
    • eVolve.Core.Revit.ProductInfo.API.ReloadGlobalConfigurations
    • eVolve.Core.Revit.Spooling.API.GetSpoolStatusParameterName
  • API signature changes
    • eVolve.Core.Revit.Spooling.API.GetSpoolStatus (optional parameter to allow providing the known status parameter name)
  • Removed API methods

Known Technical Issues

Compatibility issue with other addins

Our product uses DevExpress 24.2.7 for it's UI components. Any other Revit addin (regardless of vendor) installed on the client also using DevExpress but on a different version may cause crashes and/or unpredictable behavior with our product and/or the other addin. When this is the case, the user must either uninstall the other addin or contact the vendor to issue a new release with updated DevExpress references.

External communication

Access to the following must be allowed and unfiltered on all client machines:

  • api.evolvemep.com

Revit Project Units

Unit precision

Content and/or default configurations shipped with the product use measurements of a set precision level. Revit projects must use (at a minimum) this precision level otherwise content and/or configurations may produce errors, incorrect results, or behave unpredictably.

Length units must be set to a precision of at least:

  • 1/16" in imperial
  • 0.001 m in metric

Conduit Size units must be set to a precision of at least:

  • 1/8" in imperial
  • 0.001 m in metric

Cable Tray Size cannot use imperial notation. Fractional values should be used when imperial measurements are used.

Rounding

Configuration data will be saved against the precision level at the time of save, regardless of the precision level of the previous value.

For example, assume a configuration value is currently set to 2 1/32" and the current precision level is 1/16". When the user opens the configuration form, the value will show as 2 1/16". Upon the user clicking OK or Apply, the value will be saved as 2 1/16" even if the user did not explicitly update this particular value. The value will remain 2 1/16" even after the precision level is changed to 1/32", however at this point the user can update and save the configuration value as 2 1/32".

Licensing

When a license is disabled, the following automatic processes will not run which can cause the elements they update to become "stale" and/or lead to data issues:

  • Data protection prompts and integrity enforcement on elements with a Pre-Fab Package (eV_PackageId) assigned
  • Conduit Schedule (Parameter Push) run assignment and updates on modifications during modeling
  • System Families/Content
    • Update of eVolve_Description on modeled content
    • Working with Bends, Offsets, and Kicks may fail or produce incorrect results
    • Working with Family Hangers may fail or produce incorrect results
  • Clearance change monitoring
  • Spool Modeling
    • Deletion: disassociates parts, deletes generated spool sheets
    • Change monitoring: assists in monitoring spools on the document
      • If this is re-enabled in a session where spools have been modified then this must be rebuilt by either closing/reopening the model or by opening Prefab Manager. Failure to do so can cause incorrect behavior with the execution and/or detection of spooling events.
    • Reset on Copy: when a spool is created via a copy from existing, associations of the "source" spool (packages, status, etc.) are removed from the new spool
    • Assignment to Locations based on part assignments
  • Automatic control of product specific View Template parameters
  • Parameter Sync
  • Workset Manager
  • Macro Automation
  • Colorizer
  • Part Encoder
  • Automatic Point Status updating
  • Automatic Renumber

Default Configurations

Default feature configurations (what is applied when a feature is first used within a model) is applied in the following order (first match wins):

  1. Configuration exists within the model (i.e. the project template the model was created with contains configuration information)
  2. Default configuration is defined within Network Default Configuration of Workstation Settings
  3. Default configuration exists in the local machine's user profile folder for the product the feature was opened under
  4. Factory defaults are used

Localization

On startup, our product will set the Revit process' localization/culture according to the language settings configured. If the auto detect setting (which is the default) is used the culture will be set to the language which Revit was launched in.

Examples:

  • Auto detect is set and Revit is launched in English. The culture will be set to "en-US".
  • Auto detect is set and Revit is launched in French. The culture will be set to "fr-FR".
  • French is set as the language and Revit is launched in English. The culture will be set "en-US".

When the environment is in a hybrid setup where all of the following localizations are not consistent: Windows, Revit, and eVolve - the following inconsistencies can occur:

  • Some dialog messages may display in a different language
  • Numeric formatting may be inconsistent
    • For example, if Revit Project Units define numbers using the #,###.## format and the culture is set to use French, some numeric values may appear as # ###,##
    • Certain input fields may require for data to be entered in the format of either the Project Units or the culture
Number Formatting

The following are supported number formats for decimal values. If the settings below are not used, some features may not work as expected.

  • 123,456,789.00 when running in the English language
  • 123.456.789,00 when running in the French language

Revit Limitations

In Revit versions prior to 2023, eVolve Properties and Compare Data may not update when selecting similar elements. To refresh the data displayed in this situation, click on a empty space within the view to clear the grid and then select the target element.

Misc

  • Some features which utilize background processes and data caches may not work correctly until a project is saved with a unique RVT file name.
  • If a Revit Workset referenced in a Workset Manager rule is deleted then Workset Manager configuration must be addressed immediately, otherwise elements may continue to be assigned to the deleted Workset.
  • A licensed version of Microsoft Excel must be installed on the local machine for some import/export functionality to work.
  • Background processes required for successful operation of the product are flagged as optional within Revit. If Revit fails to load them for any reason, the user will not be notified.
  • The PowerShell version used for the execution of scripts depends upon the host Revit version:
    • Revit 2025+ uses 7.4.2
    • Prior versions use 5.1
  • Some file operations may not work as expected when using either a network path, mapped folder location, or a directory which utilizes Windows symbolic or junction links. When this is encountered, it is recommended to use a local user path (such as the user's desktop) to perform the operation.
  • Due to Revit's internal workings, Revit should be set to open on your primary monitor. When Revit is initially opened on a monitor other than the system's primary, unexpected/unpredictable behavior can occur with the initialization methods.

How did we do?

Powered by HelpDocs (opens in a new tab)