EVOLVE Mechanical 8.0.1 Hotfix

Resources

Compatibility

  • Autodesk® Revit® 2022.1.8
  • Autodesk® Revit® 2023.1.6
  • Autodesk® Revit® 2024.3.1
  • Autodesk® Revit® 2025.3

Summary

EVOLVE Mechanical 8.0.1 Hotfix fixes issues found in the 8.0.0 release and includes content improvements

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.

🔧Changes

  • Location Settings: brings back sheet settings
  • Report Manager relationship validation uses on-demand
  • Remove reporting 'login' stat to Pendo as a requirement
  • Profile message box prompt display time as Revit Selection
  • Modify Package - Disabled Package Restrictions Selection Mode
  • EULA updates

💪Stability

  • Fix Connect Elements causing debug log in some versions
  • Fix sheet creation error when encountering duplicate sheet numbering
  • Fix Plane created too far from Origin error when tagging
  • Fix conduit run length calculation for standalone conduit bends
  • Fix Sleeve tools using wrong diameter for placement
  • Fix conduit Auto Route not extending to equipment in all cases
  • Fix incorrect unit conversions in Spacing and Alignment dialog
  • Parameter Push Fix
  • Sleeves Settings error
  • Fix PowerShell setting getting reset when not opening a model
  • Fix error when creating a custom library via Family Browser
  • Conduit Run Schedule - Segment QTY Error

📂Content Updates

  • Fixed an issue related to the layout point within the new Cable Hanger family (eM_ASM_HS_Cable_Hanger).
  • Removed the Pipe Hanger (“Minerallac”) from the Family Browser and content library.
  • Fixed an issue with nested families within the new trapeze hangers (eV_ASM_HS_Angled_Channel_Trapeze, eV_ASM_HS_B2B_Channel_Trapeze, eV_ASM_HS_Single_Channel_Trapeze).
  • Added a tooltip to the parameter “CID(s) to not Explode” within the View Window family.
  • Corrected various Groups and Subgroups of rules within the DefaultConfigurationEntries.eVBatch file.


How did we do?


Powered by HelpDocs (opens in a new tab)