Fixed Defects

Issues	Short description of the source problem resolved in this version
Examples	SLVFX-33401	In the Flux Supervisor, in the Open example context, for the 3D example Brushless IPM motor - Step Skew, the test name displayed in the Example tree was wrong: Torque vs position and current instead of Back electromotive force computation. This issue has been fixed in Flux 2025.
Flux e-Machine Toolbox	SLVFX-35170	FEMT Regression: Inputs provided by FluxMotor in command line are not set in inputs table. With FEMT 2025, Input properties are well taking into account now when opening FEMT with project and input properties by command line.
Mesh	SLVFX-35552	For Flux projects coming from CAD imports where CAD faces exist, Flux calls the external geometric kernel ACIS to give us by using the (u,v) parameterization the nodes coordinates on these faces in order to mesh them. A bug existed in previous versions of Flux 2025 where the (u,v) representation of certain conical faces was treated incorrectly, which, due to the periodicity in one of these spaces, made continuity in u or v impossible to ensure. A shift of 2 PI occurred along one or more lines of these faces in this (u,v) space, making the mesh of these faces impossible. A correction was added in Flux 2025 and it is now possible, when such Flux projects are reopened, to remesh the complete device without any failure.
Parallel Computing	SLVFX-36146	In the 2024.1 version of Flux, topology optimization processes running through parametric distributed computing encountered - in the results collection phase - an issue which unexpectedly stopped the computation. This issue is now fixed and the topology optimization processes work as expected even with parametric distributed computing.
Parallel Computing	SLVFX-34080	The names 'TIME' and 'TEMPS' for a parameter were wrongly considered as reserved keywords even in Steady State AC applications, thus preventing Flux to distribute parametric computations which were solved sequentially. The issue is now fixed and distributed computations can be run whatever the names for parameters are.
Postprocessing	SLVFX-35323	In previous releases, using streamer criterion with non-planar faces, may compute streamlines on the wrong faces. The corrects faces are now used to compute streamlines in SimLab 2025.
Solving	SLVFX-36219	In a Flux 3D Steady-State AC application with solid conductors coupled circuit, when iterative solver (PETSc) was used for pre-solving, the results could be wrong. The settings of the solver has been improved and the results are now good.
Solving	SLVFX-35242	Flux giving an error due to "No exist" line in in fixed and moving mechanical sets. The issue is coming from the line extending from the Origin to the Stator slot in this case. This line has been built by reference line, so "no exist" type" and not meshed. this line is in both mechanical sets. The correction done in Flux 2025 has been to not take into account the "no exist" line during the solving of scenario or multi scenario.
Solving	SLVFX-34886	When launching a Shape or Topology optimization with two constraints that each one has its own Compose file and function, the optimizer looked for the second function in the first Compose file and the optimization process stopped. This issue has been solved in Flux 2025.
Solving	SLVFX-35471	In case arc-type lines were involved in a free-shape optimization process in the sense that they belonged or touched one of the faces selected for the optimization, the successive command "Create geometry with free-shape optimization results" could fail due to these arc-type lines. The issue has been solved in version 2025 of Flux, which is now able to take this kind of lines into account when reconstructing the geometry after a free-shape optimization.
Solving	SLVFX-34763	Prior to 2025 version, when distributed computing was activated for solving parametric scenarios, in case one or more steps could not be solved due to wrong geometrical or physical definitions, all other steps which should have been processed by the same secondary Flux instance did not appear in the selection list when the solved Flux project was closed and reloaded afterwards. As a consequence, the user could not be aware of the status of all the parametric steps. The issue has been fixed in Flux 2025 version where all the steps are listed in the step selection with their status.
Solving	SLVFX-23953	In some specific situations, when deleting the results of the project (without deleting the post-processing part) and then changing any of the geometric parameters (after deleting the mesh), meshing the model again and starting the solving process generated an error. This issue has been solved in Flux 2025.

Examples

SLVFX-33401

In the Flux Supervisor, in the Open example context, for the 3D example Brushless IPM motor - Step Skew, the test name displayed in the Example tree was wrong: Torque vs position and current instead of Back electromotive force computation. This issue has been fixed in Flux 2025.

Flux e-Machine Toolbox

SLVFX-35170

FEMT Regression: Inputs provided by FluxMotor in command line are not set in inputs table. With FEMT 2025, Input properties are well taking into account now when opening FEMT with project and input properties by command line.

Mesh

SLVFX-35552

For Flux projects coming from CAD imports where CAD faces exist, Flux calls the external geometric kernel ACIS to give us by using the (u,v) parameterization the nodes coordinates on these faces in order to mesh them. A bug existed in previous versions of Flux 2025 where the (u,v) representation of certain conical faces was treated incorrectly, which, due to the periodicity in one of these spaces, made continuity in u or v impossible to ensure. A shift of 2 PI occurred along one or more lines of these faces in this (u,v) space, making the mesh of these faces impossible. A correction was added in Flux 2025 and it is now possible, when such Flux projects are reopened, to remesh the complete device without any failure.

Parallel Computing

SLVFX-36146

In the 2024.1 version of Flux, topology optimization processes running through parametric distributed computing encountered - in the results collection phase - an issue which unexpectedly stopped the computation. This issue is now fixed and the topology optimization processes work as expected even with parametric distributed computing.

Parallel Computing

SLVFX-34080

The names 'TIME' and 'TEMPS' for a parameter were wrongly considered as reserved keywords even in Steady State AC applications, thus preventing Flux to distribute parametric computations which were solved sequentially. The issue is now fixed and distributed computations can be run whatever the names for parameters are.

Postprocessing

SLVFX-35323

In previous releases, using streamer criterion with non-planar faces, may compute streamlines on the wrong faces. The corrects faces are now used to compute streamlines in SimLab 2025.

Solving

SLVFX-36219

In a Flux 3D Steady-State AC application with solid conductors coupled circuit, when iterative solver (PETSc) was used for pre-solving, the results could be wrong. The settings of the solver has been improved and the results are now good.

Solving

SLVFX-35242

Flux giving an error due to "No exist" line in in fixed and moving mechanical sets.

The issue is coming from the line extending from the Origin to the Stator slot in this case. This line has been built by reference line, so "no exist" type" and not meshed. this line is in both mechanical sets.

The correction done in Flux 2025 has been to not take into account the "no exist" line during the solving of scenario or multi scenario.

Solving

SLVFX-34886

When launching a Shape or Topology optimization with two constraints that each one has its own Compose file and function, the optimizer looked for the second function in the first Compose file and the optimization process stopped. This issue has been solved in Flux 2025.

Solving

SLVFX-35471

In case arc-type lines were involved in a free-shape optimization process in the sense that they belonged or touched one of the faces selected for the optimization, the successive command "Create geometry with free-shape optimization results" could fail due to these arc-type lines. The issue has been solved in version 2025 of Flux, which is now able to take this kind of lines into account when reconstructing the geometry after a free-shape optimization.

Solving

SLVFX-34763

Prior to 2025 version, when distributed computing was activated for solving parametric scenarios, in case one or more steps could not be solved due to wrong geometrical or physical definitions, all other steps which should have been processed by the same secondary Flux instance did not appear in the selection list when the solved Flux project was closed and reloaded afterwards. As a consequence, the user could not be aware of the status of all the parametric steps. The issue has been fixed in Flux 2025 version where all the steps are listed in the step selection with their status.

Solving

SLVFX-23953

In some specific situations, when deleting the results of the project (without deleting the post-processing part) and then changing any of the geometric parameters (after deleting the mesh), meshing the model again and starting the solving process generated an error. This issue has been solved in Flux 2025.