Since version 2026, Flux 3D and Flux PEEC are no longer available.
Please use SimLab to create a new 3D project or to import an existing Flux 3D project.
Please use SimLab to create a new PEEC project (not possible to import an existing Flux PEEC project).
/!\ Documentation updates are in progress – some mentions of 3D may still appear.
Fixed Defects
| Issues | Short description of the source problem resolved in this version | |
|---|---|---|
| Data Import/Export context | SLVFX- 36704 |
In Flux 2025.1, the visualization of global forces has been corrected and provides same values than those exported in OptiStruct fem files. |
| Environment | SLVFX- 37187 |
In the F2HST export , lower and upper negatives values of a parameter are consistent in the XML with the Flux release 2025.1. |
| Examples | SLVFX- 36819 |
To comply with Altair cyber-security policy, the PEEC module of Flux 2025.1 version cannot provide anymore the ability to import ECAD geometries coming from Gerber files, whether they contain layer or via data. Consequently, the commands "Import of a Gerber layer" and "Import of Gerber vias" previously available in the "Project --> ECAD import" menu have been disabled, as well as their corresponding python syntaxes. Moreover, the basic tutorial "ECAD Import Gerber Format", which was available as an example through the Flux Supervisor, is no longer delivered. On the other hand, the Flux PEEC projects created with an older version remain functional with 2025.1 release, even if they contain geometries originated from Gerber files, because the imported ECAD data have been transformed into Flux PEEC entities: the cyber-security policy is therefore respected. Users interested in importing Gerber files are strongly invited to move to SimLab software where the electromagnetic solutions "Parasitics Extraction" and "AC Supplied Conductors" provide the same features of all former Flux PEEC applications, in a more user-friendly environment, with more powerful abilities and enhanced solving performances. |
| Physics | SLVFX- 37509 |
If the working directory contains an unreadable .DAT file, materials could not be imported. Now, the process continues correctly, allowing materials to be imported from other files. |
| Postprocessing | SLVFX- 36746 |
In Flux 2D Transient Magnetic application, two issues affected the proper execution of the Computation of Inductance Matrix post-processing command. The first issue appeared only in case of multi-core solving settings and it stemmed from a time synchronization problem between the secondary Flux instances and the main Flux process. The second issue was related to the naming of the coil conductor components of the circuit: in case the name of a component was part of the name of another component, the Computation of Inductance Matrix failed. Both issues have been resolved in 2025.1 version, and the Computation of Inductance Matrix (both Apparent and Incremental) command now runs without errors. |
| Solving | SLVFX- 36728 |
In Flux 3D projects containing solid conductor regions, the presolving algorithms did not take properly magnetic cuts into account in case the scalar and nodal vector variables were approximated by first order shape functions (option available to the user in the "Formulation Model" tab of the "Application" dialog box). As a consequence, when Flux was used as a solver within SimLab with the FAST approach option, some results (e.g. the magnetic field density B) could be wrongly computed. The issue has been fixed and now results are correct in both Flux and SimLab, even in case of first order approximation for the scalar and nodal vector variables. |
| Solving | SLVFX- 35886 |
When Transient Initialization method using FTS file was defined in Flux Skew Application menu, in case of solid conductor regions coupled with the circuit, some electrical variables were not duplicated correctly for all the layers of the Skew model. This generated an unwanted error message which blocked the solving process. Flux 2025.1 version solves this issue and now users can apply FTS Transient Initialization on a Skew project even with solid conductor regions coupled with the circuit. |
| Solving | SLVFX- 36534 |
In Flux previous versions, during the solving process of a project with periodicity and mechanical sets (fixed, mobile and compressible), an error occurred in an algorithm when trying to find image nodes linked to origin nodes due to duplication of nodes at the interfaces of mechanical sets. In Flux 2025.1, this issue is fixed by an improvement on this search algorithm (search performed on each mechanical set) and the solving process is now possible on this type of device with periodicity. |
| Solving | SLVFX- 37020 |
This defect is related to assigning duplicated information to List_facets (faces coming from a mesh import) touching the sliding zone when solving a project with mechanical set. This management is done at the beginning of the solving process. But, in previous Flux versions, if we want to re-run the solving process, it is not possible because during the "delete results" process, a merge process is done on duplicated mechanical set entities but we omit to manage these List_facets touching the sliding zone. The consequence is if we want to re-run the solving process, an error is display due to this missing management. In Flux 2025.1, this defect is fixed and it is now possible to delete results and run again a solving process. |