Knowledge Base ​>​ ​Announcements & Release Notes ​>​ EVOLVE Electrical 9.2.2 Hotfix

EVOLVE Electrical 9.2.2 Hotfix

Updated 11 hours 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 Electrical 9.2 Hotfix contains fixes for 9.2 and minor quality of life improvements.

🎉New

  • Global Configuration enhancements
    • Global rules show their loaded from Configuration Source
  • PowerShell improvements
    • Get-ParameterValue, Choose-Value system functions
    • ignore_readonly functionality for multi-parameter processing
  • Add support for Windows Environment variables in paths

👍Improvements

  • Allow multiple versions of hangers to appear in Hanger Placement Settings
  • Improved content portal download behavior

💪Stability

  • Try Set Parameter read only parameters in group Fix
    • Fixes Revit errors triggered by EVOLVE attempting to write to read only parameters in Revit Model Groups
  • Fix Run Id being cleared when Continue Run is executed in certain scenarios
  • Fix Generate Sheets error while related title block is open
  • Fix Conduit Run Schedule editing Parallel Run Ids incorrectly
  • Fix Sleeve Alignment Locks error when view aligns with sleeve host
  • Fix old custom parameters remaining in run schedule and being overwritten
  • Fix ITM Hanger Adjustments By Run not working when ran consecutively
  • Fix Convert to Smart Bend configuring rolling offsets incorrectly
  • Fix error when importing a Toolbox Configuration
  • Fix error when hangers with only a single rod attempt clash avoidance
  • External tables fix
  • Fix Place Clearance not placing correctly when geometry is close to tolerance
  • Fix Renumber not working with default configuration on Family Hangers
  • Fix new Equipment Manager statuses not appearing until Equipment Manager is reopened
  • Fix incorrect Selection Filter evaluation when parameter value is empty
  • Fix casing on Clearance description 'Filter' text
  • Fix Sheet Manager Location assignment not being saved
  • Connector error in explode view sheet fix
  • Fix error when deleting multiple points via Point Manager
  • Fix Renumber Configuration Common Numbering settings not being saved
  • Fix Hanger Placement Hardware Size option being incorrectly disabled
  • Fix Auto Route not connecting all straights in certain situations
  • Fix Equipment Manager error when exporting panel to invalid file name

📂Content Updates

👍Improvements

  • Updated the following in the eE_Project_Template:
    • Conduit Bend Legends
    • Spool Cut List Schedule
    • Spool BOM Schedule
  • Rod Length Parameter Sync Rule Updates:
    • Updated Rod Length rule logic to account for unique rod modifiers
    • Removed Rod Length rule from system rule files
    • Added Rod Length rule to core global config file
    • Added appropriate metadata to Rod Length rule and renamed accordingly
  • System Rule Updates:
    • System rules are now a singular eV file.
    • System rules were renamed to match existing rule naming standards.
    • Element filters and system rule descriptions were added to coincide with existing standards.

💪Stability

  • Updated eE_Conduit Bends Part Size and Description to Allow Multiple Processing
  • Updated eV_Attachments Part Description and eV_Hardware Part Description to Allow Multiple Processing.
  • Fixed an issue with cached parameter groupings for various Trapeze related Parameters in eE Project template.
  • Fixed an issue with 3D model text not remaining constrained to its associated reference plane in the Equipment Disconnect Family.
  • Fixed an issue with the Powershell script for eV_Duct Bank Part Description to output parameter value properly.
  • Fixed an issue with geometry parameters for EMT and RMC Panelboard Terminal Box families being locked by formulas.
  • Fixed version number display on landing view for the eE_Project_Template.
  • Changed parameter group for eV_LBS_Id from 5 to 2 in eV_SharedParameterDefinitions_Instance so it is applied to the proper model categories.

🧠Technical Notes

API Notices

  • API Signature Changes
    • eVolve.Core.Revit.ProductInfo.API.RegisterExpansionPathMarker (method now takes in a Func<string> for realtime evaluation instead of fixed string)

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)