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

EVOLVE Mechanical 8.1.4

Updated 1 week ago by Adam Heon

Resources

Compatibility

  • Autodesk® Revit® 2022.1.3
  • Autodesk® Revit® 2023.0.1
  • Autodesk® Revit® 2024.1.1
  • Autodesk® Revit® 2025

Summary

EVOLVE 8.0 Release notes:

INTERNAL ONLY UNTIL RELEASE

Upgrade Notices

🎉New:

  • New

    • RP-142 Move Straight feature
    • RP-538 Quick Tools to Extend a Run
    • RP-760 Move/Extend and Align Quick Tools
    • RP-1018 Add Create MAJ option to Pre-Fab Manager
    • RP-1077 Add halftone and transparent options to Renumber selection
    • RP-1101 Add ITM support to Connect and Insert Offset
    • RP-1158 Add support for vertically sloped duct banks
    • RP-1196 Align Run Intersection
    • RP-1235 Custom Launch Pane tool
    • RP-1240 Add option to disable Mechanical Properties
    • RP-1243 View Local Usage Stats tool
    • RP-1245 RP-1299 Video links for Quick Tools
    • RP-1259 Add ability to customize ribbon panels
    • RP-1261 Reorganize settings dropdown into separate dialog
    • RP-1269 Additional video tooltips
    • RP-1274 Add 'eVolveDocument' as PowerShell variable
    • RP-1283 Add command context to selection prompt overlay
    • RP-1302 Add CSV File, Serialized Data Table as External Data Table Source
    • RP-1303 Copy Data Table tool

    Change

    • RP-892 Add help message on family conflict error, Fix notice messages
    • RP-920 Add Size By option for individual ITM Hanger Placement rules
    • RP-1074 Notify users to reopen models opened while not licensed
    • RP-1118 Update button text on Library Configuration UI
    • RP-1278 Option to disable auto-rebuild Spool Sheets after edit
    • RP-1305 UI updates
    • RP-1318 Points Along Run ignore vertical
    • RP-1323 Settings Launcher HelpDoc update

    Fix

    • RP-142 Move Straight Valve Fix
    • RP-538 Extend Run Small Fixes
    • RP-760 Multi Align: Only align open connector fix
    • RP-784
      • Fix rotation of created Location views
      • Fix Location view sheet generation not rotating elevation views properly
    • RP-1046 Connect offset slope error
    • RP-1101
      • Fix Connect Offset allowing you to pick invalid elements to connect
      • Fix gap between pipes when using Insert and Connect Offset tools
    • RP-1188 Fix Multi-Trim showing incorrect error
    • RP-1245 Fix spacing on Horizontal Spacing Config form
    • RP-1296 Fix error when closing Revit without first opening a model
    • RP-1309 Fix Create Points error when attempting to place on host
    • RP-1334 Fix issue where internal Data Table cache clears incorrectly
    • External Data Tables sourced from Excel load significantly faster
    • Remove hardcoded product name from Spool Configuration display text

🧠Technical Notes

API Notices

Known Technical Issues

Known Technical Issues

Compatibility issue with other addins

Our product uses DevExpress 23.2.6 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
  • app.pendo.io

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 and integrity enforcement 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.
    • 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
  • 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

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, Mechanical 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)