The following imported loading condition enhancements were made at Release 2026 R1:
Imported Load Mapping Improvements.
Processing Time Enhancements. Now, depending on the number of source and target nodes and the number of time/frequency sets being mapped, the processing time required to import and map load data to your model has been reduced by at least 10% and as much as 50%. To accomplish this, the imported load must be specified with the following property settings:
Mapped Data = To Binary File.
Weighting = Triangulation or Distance-Based Average, or this property set to Shape Function and Transfer Type = Volumetric.
Given these settings, the processing improvements occur automatically.
Imported Velocity Mapping. In addition, to improve performance and reduce resource usage when mapping Imported Velocity load data, the application now automatically sets the Weighting property to Triangulation whenever the Mapping Control property is set to Program Controlled. Previously, the application used Shape Function as the default setting for the Weighting property. Unlike Shape Function, Triangulation uses point cloud-based mapping on nodal data. As a result, it avoids mapping data from interior nodes, which reduces both mapping time and resource consumption.
Progress During Load Import and Mapping. Also, when you are using the To Binary File option of the Mapped Data property to import a load, the application now displays a progress bar that indicates the current frequency or time set being interpolated, along with the total number of sets to process.
Parallel Processing for Binary File-Based Imported Loads. To improve the data mapping process on Linux, you can now set the maximum number of cores using the Workbench Maximum Number of Cores preference (Tools > Options > Mechanical). By default, the application uses all cores. This capability requires the following settings:
Mapped Data = To Binary File
Weighting = Shape Function
Transfer Type = Volumetric
Specifying Source Bodies for Imported Loads. For Imported Velocity and Imported Body Temperature loads, when Mapped Data = To Binary File, the Source Bodies property now includes a new drop-down option: All Available Result Nodes. This option automatically identifies and selects all bodies in the upstream system that contains result data. This enhancement eliminates the need to manually define Named Selections when the upstream result is filtered, simplifying setup and improving data mapping efficiency.
Imported Heat Generation from Maxwell. You can now import Imported Heat Generation loading conditions from the Maxwell application to a downstream Coupled Field Static or Coupled Field Transient analysis.
Imported Body Temperature. When importing data for an Imported Body Temperature load with Mapped Data set to To Binary File, the application now updates only the modified Scale or Offset values (as adjusted in the Data View window). It no longer remaps all load data. This targeted update significantly reduces mapping time for Scale or Offset changes, especially when working with moderate to large source datasets.
Importing Body Temperature Using External Data. For Static Structural and Transient Structural analyses, you can use External Data to import temperature results in H5DPF file format and define an Imported Body Temperature load. This file type is created using ANSYS Data Processing Framework (DPF) and is based on the Hierarchical Data Format version 5 (*.h5).
Grouping Loads Imported from Maxwell. Now, when importing remote loads from the Maxwell application, use the Grouping Default for Imported Remote Loads (Options > Import > Imported Remote Loads) preference to change the default setting for how the application groups the load data using the Grouping property. Options for this preference include By Location, To Binary (default), and No.