EVOLVE Mechanical 10.2.1

Updated 12 minutes ago by Jason Earl

Resources

• Downloads
• Feedback and Ideas
• Support
• Licensing
• Known Limitations/Bugs

Compatibility

• Autodesk® Revit® 2024.3.6
• Autodesk® Revit® 2025.4.6
• Autodesk® Revit® 2026.5
• Autodesk® Revit® 2027.2

Summary

EVOLVE Mechanical 10.2 improves detailing workflows with automatic tag arrangement for quick and easy tag arrangement.

Update Training Course

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

Configuration setting incompatibilities

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

🎉New

• Auto Tag Arrangement
  • Tags placed by EVOLVE during spool sheet creation are automatically arranged to improve drawing readability
  • We've also added a standalone tag arrangement feature for quickly arranging tags already placed

👍Improvements

• Allow disabling Spool and Package visual cues

💪Fixes

• Fix Fab Part Custom Data not updating when changing part type
• Fix users being incorrectly put into offline mode when logging into the product
• Prevent reporting of erroneous stats from external plugins
• Fix package related error when opening Sheet Manager
• Fix Sleeve Placement no longer properly sizing for part insulation
• Fix error when opening Project Setup or Content Portal in Revit 2025 or 2026
• Fix view position resetting after Spool and Package operations
• Fix Auto Place Sleeves placing incorrectly for small elements
• Fix invalid Content Browser configuration crashing Revit
• Fix Convert to Box Out failing silently in certain scenarios
• Fix blank PreFab Manager listing when insulation packaged
• Fix merged packages receiving invalid name and breaking PreFab Manager

📂Content Updates

🔦 Highlights

• Significantly improved the ITM Hangers report with calculation fixes, formatting corrections, additional hanger type support, and expanded rounding capabilities.
• Added automatic tag arrangement support to fabrication pipe tag families.
• Various bug fixes.

⤴️ Family Version Changes

• eV_ASM_HS_Trapeze_1_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_1_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_2_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_2_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_3_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_3_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_4_Tier_NHW_v8.rfa → eV_ASM_HS_Trapeze_4_Tier_NHW_v9.rfa
• eV_ASM_HS_Trapeze_1_Tier_v9.rfa → eV_ASM_HS_Trapeze_1_Tier_v10.rfa
• eV_ASM_HS_Trapeze_2_Tier_v9.rfa → eV_ASM_HS_Trapeze_2_Tier_v10.rfa
• eV_ASM_HS_Trapeze_3_Tier_v9.rfa → eV_ASM_HS_Trapeze_3_Tier_v10.rfa
• eV_ASM_HS_Trapeze_4_Tier_v9.rfa → eV_ASM_HS_Trapeze_4_Tier_v10.rfa
• eV_ASM_HW_Threaded_Rod.rfa → eV_ASM_HW_Threaded_Rod_v2.rfa
• eV_HW_4_Hole_Steel_Plate.rfa → eV_HW_4_Hole_Steel_Plate_v2.rfa
• eM_EQ_Terminal_Unit_v3.rfa → eM_EQ_Terminal_Unit_v4.rfa
• eM_Tag_FabPipe_Number.rfa → eM_Tag_FabPipe_Number_v2.rfa
• eM_Tag_FabPipe_Valve.rfa → eM_Tag_FabPipe_Valve_v2.rfa
• eM_Tag_FabPipe_Weld.rfa → eM_Tag_FabPipe_Weld_v2.rfa

🎉New

• Added the parameter eVolve_Version_Number to the SharedParameterDefinitions.txt file. This parameter will replace eVolve_Version in all families in a future release.

👍Improvements

• ENHANCEMENTS
  • Added parameters to the following Fabrication Part (ITM) tag families to support automatic tag arrangement:
    • eM_Tag_FabPipe_Number
    • eM_Tag_FabPipe_Weld
    • eM_Tag_FabPipe_Valve

💪Stability

• Removed redundant, old versions of the legacy strut hanger families from the hanger.
• Fixed an issue where R_Length_Minimum calculations in the threaded rod assembly and terminal unit assembly families did not correctly account for family geometry variations.
• Fixed default values in the 4-tier basic strut trapeze family.
• Fixed an issue with the 4-hole steel plate family that resulted in hole diameter referencing radius instead of diameter.
• Fixed an issue with the duct bank template part description parameter sync rule not rounding properly.
• Fixed an issue with the element filter for the packages entry in the default project tags configuration file.
• Fixed various issues with the ITM_Hangers report:
  • Resolved an issue where hanger type totals were incorrectly reset when counts spanned multiple report pages.
  • Corrected size formatting for values containing fractional dimensions (e.g., 2-1/2"). Previously, these values were incorrectly interpreted as imperial foot measurements, resulting in outputs such as 24-1/2".
  • Suppressed the Size column label and value when cal_ProductSize_Value equals zero.
  • Fixed the Bottom Elevation calculation for Type 2 (Trapeze) hangers, which was incorrectly returning zero for all records. Restored the missing cal_Elevation_BOP calculation logic and corrected the associated rounding process.
  • Corrected rod and length rounding behavior, removed a duplicate calculated field, and updated the related expression.
  • Added support for 3" and 6" rounding increments.
  • Corrected the Type2_Labels_SubReport.par_Filter_3 parameter binding, which was incorrectly mapped to par_Filter_2.
  • Fixed the cal_Display_Depth expression to ensure values are displayed correctly in all supported scenarios.
  • Added support for numerous hanger types from the Origin database.
  • Removed the Pier category from the eM_BOM data profile Element Filter and added Pipe Accessories.
  • Updated the dtFabricationAncillaries data profile to support newly added hanger types.
• Added missing support for the Trapeze Tier Offsets tag to the legacy strut trapeze hanger families.

🧠Technical Notes

Upgrade Notices

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.

Known Technical Issues

Compatibility issue with other addins

Our product uses DevExpress 25.2.5 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.

API Notices

• New API methods
  • eVolve.Core.Revit.Spooling.API.CreateSpool
  • eVolve.Core.Revit.Spooling.API.SpoolNameExists

Known Technical Issues

Compatibility issue with other addins

Our product uses DevExpress 25.2.5 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/32" in imperial
• 0.0001 m in metric

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".

Duplicate Custom Properties

When multiple custom properties with the same name are present, only the first one will be editable in the eVolve Properties grid. Additionally, the respective eM_ property with the same name will have the data type of this first entry.

In the event there is a duplicate name with a different data type this can cause issues if it is not fixed across all models (where the first property by the name is the same data type for all). These situations will need to be addressed manually.

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 on elements with a Pre-Fab Package (eV_PackageId) assigned
• Spool Modeling
  • Modification: updates association of parts merged into/added to/removed from a spool
    • Prompt to add parts cut into or added on to the end of an existing spool
    • Prompt to update sheets when a spool is modified
    • Prompt to renumber when a spool is modified
  • 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.
  • Assignment to Locations based on part assignments
• Properties
  • Fabrication Part properties sync with Revit parameters
  • Carry over values
• Working with Family Hangers may fail or produce incorrect results
• Automatic control of product specific View Template parameters
• Parameter Sync
• Workset Manager
• Macro Automation
• Gauge Manager
• 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

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.
• 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?