The following list highlights the enhancements and changes to EnSight in 2025 R2. This list is very short due to significant reallocation of effort towards internal integration of our technologies into other tools. In addition, we have several major enhancements that have reached Beta state and can be utilized under the guidelines of a beta feature.
Improved DVS Exports from Fluent
EnSight can now receive both user defined zones as well as volume and surface parts during a single export from Fluent. EnSight also receives report definitions and residuals information in the form of queries in EnSight. A collection of bugs/gaps in the DVS export from Fluent were fixed as well. As we move forward, we are striving to make the DVS data transport from Fluent to EnSight the suggested method.
Polyflow Users in Workbench
Users can now utilize EnSight for post-processing Polyflow datasets within the Workbench environment. There is now an option when post-processing Polyflow datasets in Workbench to launch EnSight to view the results.
Ansys Results Reader Improvements
We have resolved several outstanding bugs in the Ansys Results reader.
GLB Export Efficiency Improvements
Transient with constant topology, when written to the single file format of GLB, now only writes a single array for the geometry (rather than 1 per timestep). This improvement only applies to single file GLB.
AVZ & JT Export with Vector Component Colors
You can now correctly color their AVZ and JT Export with components of a vector directly. Previously, the color for vector coloration was only the magnitude of the vector. Now, if you select to color by a component of a vector, that color is correctly respected in the AVZ and JT Export.
Internal Library Updates
Countless number of internal libraries have been updated (e.g. Qt, Python, FFMPEG, VTK, etc.) to maintain consistency with other applications and corporate wide requirements.
Removal of the XDMF2 and XMDF3 Readers from Installation Package
These were removed due to incompatibility with a required update in our application binary interface. Should you require these readers, you will need to either continue with 2025 R1 or earlier packages, or provide updated ABI versions for us to include.
Save CSV Results from the Performance Tool
The Performance Tool (In UserDefinedTools) no longer pushes results directly to the performance website. Rather, you can save the CSV form of that performance graph locally.