EVOLVE Electrical 8.0.0
Resources
Compatibility
- Autodesk® Revit® 2022.1.3
- Autodesk® Revit® 2023.0.1
- Autodesk® Revit® 2024.1.1
- Autodesk® Revit® 2025
🧑🎓EVOLVE University 8.0 Update Training Course
EVOLVE 8.0 Update EVOLVE 8.0 Update - EVOLVE
If not registered for EVOLVE University, please contact your sales representative. If you are registered for EVOLVE University and cannot access the course, please contact Alex.Siebert@evolvemep.com
Summary
EVOLVE 8.0 Release 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.
🎉New:
- Allow create new run id during assign run
- Add Hanger Family Rod Adjustments
- Enhancements to Create Points
- Add the ability to place points along grids
- Add the ability to place points along runs
- Add the ability to place points at the ends of elements or runs
- Add ability to renumber multiple runs at once
- Add option to let the user be prompted for the name for each spool or package definition
- Add additional error messages to sleeve placement
- Add support for providing an exploded view of a spool
- Auto Route Cable connect between devices with same XY
- Add Description Builder
- Prefab Manager: Selection Scope dropdown
- Add User and Project Annotation Tags and various tagging features
- Add hotkeys
- Add tag all / tag selected via element filter
- Add Hanger Placement option to select multiple directions before placement
- Add TFLX extension to Point Manager export
- Add 'eVolve Product Name' as a Special Parameter in Data Profiles
- Add option to toggle between current and legacy spooling and packaging restrictions
- Description:
When the Spooling option "Disable EVOLVE spooling restrictions" checkbox is checked spools cannot be selected when using the feature Modify Package.
Work Around:
Uncheck the checkbox for the spooling option "Disable EVOLVE spooling restrictions".
- Include hotkey when importing and exporting Element Filters
- Add Revit 2025 Support
- Remove Revit 2021 Support
- Add Estimate Point Loads
- Add specific error message when using Standard Schedule with Sheet Generation
- Customized CSV Point Export Columns
- Allow Report Manager to temporarily override Data Profile selection scope
- Add Revit Groups support for Family Browser
- Apply Conduit Run information to actual conduit run elements
- External Data Tables
- Prompt users to refresh cable data after modifying cable schedule settings
- Profiling Tool
- Capture local usage statistics
- Report stat on opening report designer and preview
👍Improvements:
- Enhanced Sheet Creation Method
- Tooltips Update - Prefab Manager
- Sheet Creation: Option to ignore empty schedules
- Add undo event per Quick Dimension operation
- Alert when "View Template applied to new views" parameter is set
- Use standard error message for family load error when creating a location
- Allow Continue Run to work on runs of different sizes
- Disable controls in unselected placement modes in Add / Remove Union
- Remove concurrent product support
- Add ability to Round Conduit Runs in Run Schedule Options
- Notify user when no empty filters available during Sheet Schedule generation
- Add Bulk Update to Data Profiles
- Expanding on Point Family Naming Options
- Add specific error message when using Standard Schedule with Sheet Generation
- Additionally export DWG when using Export Grid in Point Manager when enabled
- Compare Data New Columns
- Various Auto-Route on Pathway enhancements
- Support for more placement scenarios
- UI updates
- UI updates to Workstation Settings
- Expand Hanger Placement family naming requirements
- Icon updates to support light/dark mode options
- Update to DevExpress 23.2.6
- API Updates
- Update behavior of selection file browser default path
- EULA displays acceptance terms for third party libraries
- Add smaller icons for settings dropdown on ribbon
- Updated default configs for parameter sync and data profiles
- Log model path and worksharing info
- 8.0 Content Changes
- Updated French Translations
🔧Changes
- Display error instead of crashing when creating a Location and unable to load family
- Convert Sleeves to Box Out Alignment Fixes
- Fix 'Evaluate Insulation' option not populating from predefined profile in Convert To Box Out
- Update top margins of forms to fit help and settings buttons
- Fix Item Number tags not being placed in a Standard View Plan view
- Restrict results of Selection Filters in linked models to view when applicable
- Fix Modify Spool removing elements from spools unintentionally
- Display message instead of crashing when selecting computed points in Point Manager
- Fix Data Profiles allowing saving with non-uniquely named fields after hitting the duplicate button
- Fix hanging issue on Revit startup
- Remove runs with invalid parameter data from Auto Route on Pathways
- Fix controls being incorrectly enabled in Insert Offset UI
- Fix Smart-Bend Multi-Trim Errors
- Offset Mark 1 not going to 0 when less than minimum value
- Utilities API 'PublishToExporter' method fails if Export Utility config does not exist
- Location Manager sheet creation - delete redundant msg box
- Hanger Placement Delete only created Views
- Clearance Tools delete pinned elements fix
💪Stability
- Removal of legacy code
- Remove Amazon library dependencies
📂Content Updates
- Updated eE_Project_Template.rte
- Removed eE_TitleBlock_11x17_Basic_Spool.rfa
- Removed eE_TitleBlock_11x17_Advanced_Spool.rfa
- Added eE_TitleBlock_11x17_Spool.rfa
- Added eE_TitleBlock_36x48_Spool.rfa
- Added schedule eE_Spool BOM
- Added schedule eE_Spool Conduit Bend All With Labels Advanced
- Added schedule eE_Spool Conduit Bend All With Labels Basic
- Added schedule eE_Spool Cut List
- Added view template eE_Spool BOM
- Added view template eE_Spool Conduit Bend All With Labels Advanced
- Added view template eE_Spool Conduit Bend All With Labels Basic
- Added view template eE_Spool Cut List
- Updated eV_View_Window with v3
- Added an option in the transformer family to extend the front clearance to the floor
- Removed CableTrayFittings.eVBatch file and merged its entries into the DefaultConfigurationEntries.eVBatch
- eV_Window enhancements
- Updated to v3
- Parameters and section headers reorganized to support friendlier user experience
- Added selection to Assign or Apply the specified View Template
- Added new View Types section – a selection is required here before proceeding to select a more specific view type
- Added an option to explode 3d Ortho views
- Added an option to specify the distance to explode 3d Ortho views
- Added an option to ignore specific CIDs when exploding a 3d Ortho view
- Added support for Plan Detail Assembly Views
- Added a 3D Orientation section with (9) options – Input is required for Standard 3D Views and 3D Ortho Assembly Views
- Added an option to specifqy a Viewport Type
- Added Crop Region Height and Width options in the View Extents section
- Added a new J-Hanger family to the Family Browser
- Added new Trapeze Hanger Assemblies to the Family Browser
- Metal stock trapeze assembly with support for 1 or 2 tiers
- 1-Tier steel channel assembly
- 1-Tier back-to-back steel channel assembly
- Trapeze Hanger Assembly Features
- Compatible with the Hanger Placement tool
- Support for (9) hardware sizes, up to 1-1/2”
- Contain a nested generic parametric mounting attachment with a customizable Part Description
- Support for parametric sizing of nested steel channel and metal stock
- Rod length rounding calculations are nested within the new families
- Support for customization of the Part Descriptions and inclusion of nested parts (ancillaries) within the assemblies
- Added Anvil product data for new hangers
- Updated the nested angled steel family with new parameters to support different leg widths (Stock_Width1 & Stock_Width2)
- Added a custom thickness option to the nested angled steel family
- Added new Parameter Sync Rules to the DefaultConfigurationEntries.eVBatch file
- eV_Hardware – Creates an eVolve_Description for hardware families
- eV_Attachments – Creates an eVolve_Description for attachment families
- eV_U-Channel – Creates an eVolve_Description for u-channel metal stock families
- eV_Angled Channel – Creates an eVolve_Description for angle channel metal stock families
- Removed Dura-BlokAssemblies.eVBatch file and merged its entries into the DefaultConfigurationEntries.eVBatch file
- Removed ContentError.eVBatch file and merged its entries into the DefaultConfigurationEntries.eVBatch file
- Reorganized entries within the DefaultConfigurationEntries.eVBatch file with standard Groups and Subgroups
- Updated existing hanger Family Browser images
- Updated annotation tag Family Browser images
- Added sample detail groups to the family browser
- Added sample model groups to the family browser
API Notices
- New API methods
eVolve.Core.Revit.ProductInfo.API.UserConfigurationFolderPath
eVolve.Core.Revit.ProductInfo.API.GlobalConfigurationFolderPath
eVolve.Core.Revit.Reporting.API.ClearTableCache
eVolve.Core.Revit.Reporting.API.RegisterExternalDataTable
eVolve.Core.Revit.Reporting.API.UnregisterExternalDataTable
eVolve.Core.Revit.Reporting.IExternalDataTable
(interface)
- API signature changes
eVolve.Core.Revit.Reporting.API.GetTableNames
(adds optional parameters)- enum
Integration.DataProfilesConfigurationData.ProfileDirection
was moved toIntegration.API.ProfileDirection
- Removed API methods
eVolve.Core.Revit.Integration.IsLicensed
(useeVolve.Core.Revit.ProductInfo.API.IsLicensed
)eVolve.Core.Revit.Reporting.IsLicensed
(useeVolve.Core.Revit.ProductInfo.API.IsLicensed
)
🧠Technical Notes
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/16"
in imperial0.001 m
in metric
Conduit Size units must be set to a precision of at least:
1/8"
in imperial0.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
- Update of
- 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 Spool 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):
- Configuration exists within the model (i.e. the project template the model was created with contains configuration information)
- Default configuration is defined within Network Default Configuration of Workstation Settings
- Default configuration exists in the local machine's user profile folder for the product the feature was opened under
- 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
- For example, if Revit Project Units define numbers using the
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 language123.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 an empty space within the view to clear the grid and then select the target element.
Misc
- Family content, Parameter Sync, Workset Manager, Colorizer, Macro Automation, Part Encoder, and Automatic Renumber 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.
- PowerShell is used for the execution of scripts. In versions of Revit below 2025, PowerShell version 5.1 is used, otherwise version 7.4.2 is used.
- 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.