# A new PrePoMax version v2.6.0 RC1 has been released

**URL:** <https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595>\
**Category:** News\
**Created:** [August 7, 2026, 1:06pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595 "2026-08-07T13:06:34Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [August 7, 2026, 1:06pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/1 "2026-08-07T13:06:34Z")

</div>

A new release version of the PrePoMax contains the following FEM features (with regard to v2.5.2):

- new revolve mesh implementation: allows the use of Quasi-structred quad algorithm, geometry touching the axis, and creation of full 360° meshes
- added support for FEMaster solver
- improved multi-part meshing performance
- added support for vector plots of vector fields and principal tensor values, including animations
- added support for smooth color contours
- added support for Bidirectional Mesh Converter: Nastran to CalculiX and vice versa (supplied by Capgemini)
- added support for modifying existing CalculiX keywords
- added support for kinematic and distributing coupling
- bug fixes

And the following user features (with regard to v2.5.2):

- updated/added icons
- added highlighting of (geometry part) – (mesh setup item) connections in both directions
- added support for creating groups of items in all model trees (excluding Steps)
- added support for item drag & drop in all model trees (including Steps)
- added support for displaying annotations during animations
- added permanent measurement annotations (distance, angle, circle radius)
- added additional context menus for the legend widget: min and max values can be changed directly on the legend
- added support for widget context menus and highlighting
- the number format setting is now general and controls all number outputs
- added progress tab with progress and convergence diagrams to the Monitor window
- added support for displaying item IDs
- added annotation arrange command

The list of all new features can be found at: [Version 2.6.0](https://prepomax.fs.um.si/version-2-6-0/)  
Download: [PrePoMax](https://prepomax.fs.um.si/downloads/)

---

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [August 7, 2026, 1:20pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/2 "2026-08-07T13:20:59Z")

</div>

Many new features were implemented, so I decided to release PrePoMax as Release Candidate 1 (RC1). In this way, possible bugs can be fixed, and a more stable version 2.6.0 can be produced.

For the revolve mesh to work on models with a 180° geoemtry that touch the axis, a split line must exist along the axis. If a 360° full rotation is needed, the geometry must be an angle that exactly divides 360°: 180°, 120°, 90°, …

 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/d/d945f0b0de9dfccbbfd102fc676b593c7e08bcc3.png)  
 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/f/fa92b72529ab1945e5b6d278be34ed34204cc03d.png)

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 1:28pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/3 "2026-08-07T13:28:58Z")

</div>

> [@Matej](#):
>
> Many new features were implemented, so I decided to release PrePoMax as Release Candidate 1 (RC1). In this way, possible bugs can be fixed, and a more stable version 2.6.0 can be produced.

Makes sense. FreeCAD does the same and releases 2 or 3 RCs before the stable version.

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 1:34pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/4 "2026-08-07T13:34:31Z")

</div>

> [@Matej](#):
>
> - added progress tab with progress and convergence diagrams to the Monitor window

Any chance you could add horizontal lines showing the level below which the criteria are considered converged? It could be even just for the default levels of 0.5% and 1%. This would make it much easier to see how far we are from convergence.

---

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [August 7, 2026, 1:48pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/5 "2026-08-07T13:48:33Z")

</div>

I thought about it, but the dilemma was to get the correct limit values. They can be changed by the user, and I think they can be different for each step?

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 1:49pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/6 "2026-08-07T13:49:54Z")

</div>

Yeah, that’s right. The easiest way would be to ignore the custom values and add a note that it only shows the default criteria. In practice, `*CONTROLS` are rarely used (or at least should be rarely used).

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 3:53pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/7 "2026-08-07T15:53:48Z")

</div>

> [@Matej](#):
>
> - added support for vector plots of vector fields and principal tensor values

They don’t take the local directions (e.g., for shells) into account, right?

S11 plot for inclined shell compared with Abaqus:

 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/1/179e1884db1d35f0bacbb8a5408ed0d5d85ab447.png)

 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/4/4502c9f66cb4d8641b0838448fc70ea046b5eeb3.png)

---

<div class="post-metadata">

**Author:** ![Michal](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@Michal](https://prepomax.discourse.group/u/Michal)\
**Post date:** [August 7, 2026, 6:12pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/8 "2026-08-07T18:12:50Z")

</div>

I have question where are files for new solver implemented ?

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 6:20pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/9 "2026-08-07T18:20:17Z")

</div>

It’s not provided with PrePoMax, but you can download it from here: [Releases · Luecx/FEMaster · GitHub](https://github.com/Luecx/FEMaster/releases) (and just select its executable in PrePoMax settings).

---

<div class="post-metadata">

**Author:** ![Michal](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@Michal](https://prepomax.discourse.group/u/Michal)\
**Post date:** [August 7, 2026, 7:31pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/10 "2026-08-07T19:31:34Z")

</div>

is some standard approach for creating analysis in PPM wit fem solver or the same way as when using calculix solver?

---

<div class="post-metadata">

**Author:** ![SergioP1975](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/sergiop1975/32/37_2.png) [@SergioP1975](https://prepomax.discourse.group/u/SergioP1975)\
**Post date:** [August 7, 2026, 7:33pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/11 "2026-08-07T19:33:32Z")

</div>

@Michal , take a look at this post. There is another post also with some examples.

> [@FEMaster as a FEM solver](https://prepomax.discourse.group/t/femaster-as-a-fem-solver/3572/2):
>
> Well, I just using it for two weeks ago and looks amazing. The developer has changed the output to .frd compatible format so the direct integration with Prepomax is ready. There are some features that could complement very well Calculix such as inertia relief and inertial loads if I have understand well. In order to run in Prepomax, we need to define mesh, material and sections as usual, and define groups of nodes/faces/elements to write then the input cards with the deck editor included in Pr…

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 7:42pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/12 "2026-08-07T19:42:58Z")

</div>

Download and reference the executable FEMaster.exe here:

 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/f/fb24d47b36747aadb8b9a196d9d35d06c4b819b2.png)

Then set up the analysis and change the solver to FEMaster:

 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/1/1e850ec1c71be9dd2b4fe9498882f588cffaf9c4.png)

You may also need to make some keyword edits (since the step syntax is different) and use node sets and element sets to assign analysis features.

---

<div class="post-metadata">

**Author:** ![SergioP1975](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/sergiop1975/32/37_2.png) [@SergioP1975](https://prepomax.discourse.group/u/SergioP1975)\
**Post date:** [August 7, 2026, 9:13pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/13 "2026-08-07T21:13:53Z")

</div>

Don´t forget to increase the number of processors, now is unified for all the solvers

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 7, 2026, 9:16pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/14 "2026-08-07T21:16:12Z")

</div>

Yeah, I just keep it at 1 in dev versions. For testing, especially a new solver, it’s usually better.

---

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [August 8, 2026, 8:18am UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/15 "2026-08-08T08:18:34Z")

</div>

> [@FEAnalyst](#):
>
> They don’t take the local directions (e.g., for shells) into account, right?
> 
> S11 plot for inclined shell compared with Abaqus:

No, local directions are only taken into account when creating a field coordinate transform.

In normal cases, the .frd results are in the global coordinate system. So the color contours and vector fields represent the same global coordinate system. I did not test what happens when a local coordinate system is selected for the field outputs. I had enough to do to make it work 🙂

My larger concern is that it is very hard to see anything if the mesh is dense. So I am thinking of adding some kind of spatial decimation (maybe based on zoom) or definition of sets for which the vector plot should be shown.

---

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [August 8, 2026, 8:19am UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/16 "2026-08-08T08:19:48Z")

</div>

To test FEMaster, an empty PrePoMax model can be used, and a FEMaster input file can be inserted into the Calculix Keywords editor.

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 8, 2026, 9:22am UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/17 "2026-08-08T09:22:27Z")

</div>

> [@Matej](#):
>
> No, local directions are only taken into account when creating a field coordinate transform.

Ok, this can be a good enough workaround.

> [@Matej](#):
>
> I did not test what happens when a local coordinate system is selected for the field outputs.

I’ve tried with Global=Yes/No and noticed no difference in the symbol plot for shells. Supporting orientations can be problematic due to how CalculiX stores the results.

> [@Matej](#):
>
> My larger concern is that it is very hard to see anything if the mesh is dense. So I am thinking of adding some kind of spatial decimation (maybe based on zoom) or definition of sets for which the vector plot should be shown.

Abaqus has a setting for that:

 ![symbol_density](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/0/043fcd6348b5b6208655695eb3993c9345d74e6e.png)

---

<div class="post-metadata">

**Author:** ![Michal](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@Michal](https://prepomax.discourse.group/u/Michal)\
**Post date:** [August 8, 2026, 5:02pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/18 "2026-08-08T17:02:01Z")

</div>

when usage of prepomax with femaster will be more user friendly, I mean less keyword editor and so on . best regards

---

<div class="post-metadata">

**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\
**Post date:** [August 8, 2026, 5:05pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/19 "2026-08-08T17:05:15Z")

</div>

The FEMaster dev said that he could make the syntax more in line with Abaqus and CalculiX syntax: [FEMaster as a FEM solver - #13 by Luecx](https://prepomax.discourse.group/t/femaster-as-a-fem-solver/3572/13)

---

<div class="post-metadata">

**Author:** ![Michal](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@Michal](https://prepomax.discourse.group/u/Michal)\
**Post date:** [August 8, 2026, 5:08pm UTC](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595/20 "2026-08-08T17:08:37Z")

</div>

good news 🙂 I hope it will change soon

[Next page](https://prepomax.discourse.group/t/a-new-prepomax-version-v2-6-0-rc1-has-been-released/3595.md?page=2)
