# A developer/preview PrePoMax version v2.0.10 has been released
**URL:** https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735
**Category:** News
**Created:** [May 12, 2024, 10:09am UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735 "2024-05-12T10:09:02Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Matej](https://prepomax.discourse.group/u/Matej)
#### Post date: [May 12, 2024, 10:09am UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735/1 "2024-05-12T10:09:02Z")
In this version:
- Step controls editor was added (Right click on the step → Edit controls)
- The op parameter for loads was changed to a separate keyword. This enables the user to insert op=mod parameter before the default op=new parameter to overwrite it during CalculiX analysis and have a step with op=mod active.
- bug fixes (material unit converions)
To use the op=mod parameter, one must insert op=mod before op=new in the Keyword editor:
Download: [Downloads – PrePoMax](https://prepomax.fs.um.si/downloads/)
---
### Author:  [@Matej](https://prepomax.discourse.group/u/Matej)
#### Post date: [May 12, 2024, 12:22pm UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735/2 "2024-05-12T12:22:11Z")
I considered adding support for the op parameter in the Step controls editor. In CalculiX, the step controls are meant to set the solver parameters during incrementation. So they have a special purpose. But in PrePoMax, I could add an additional control parameter called Op, which would have entries as Boundary, Cload, Dload, Temperature … and the possibility to switch from the default “new” value to a “mod” value.
The problem I see is that these op settings would not be visible in the FE Model tree. The user could easily forget about them.
What do you think?
I am still looking for an example where the op=new settings cannot perform the required task…
---
### Author:  [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)
#### Post date: [May 12, 2024, 12:43pm UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735/3 "2024-05-12T12:43:10Z")
> [@Matej](#):
>
> What do you think?
Would be nice to have an option to change this somewhere without having to edit the keywords manually. Maybe when editing a load/BC ?
> [@Matej](#):
>
> I am still looking for an example where the op=new settings cannot perform the required task…
Like this ? [Wrong results in a multistep analysis with shells and \*BOUNDARY, OP=NEW · Issue #13 · Dhondtguido/CalculiX · GitHub](https://github.com/Dhondtguido/CalculiX/issues/13)
---
### Author:  [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)
#### Post date: [May 12, 2024, 12:54pm UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735/4 "2024-05-12T12:54:50Z")
> [@Matej](#):
>
> Step controls editor was added (Right click on the step → Edit controls)
Perhaps support for `*CONTROLS` should come with a warning like in Abaqus:
We’ve seen too many cases of misuse of this keyword.
---
### Author:  [@Matej](https://prepomax.discourse.group/u/Matej)
#### Post date: [May 12, 2024, 6:07pm UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735/5 "2024-05-12T18:07:36Z")
> [@FEAnalyst](#):
>
> Would be nice to have an option to change this somewhere without having to edit the keywords manually. Maybe when editing a load/BC ?
I don’t think this would be the best place. Imagine having a concentrated load and a surface traction load in the same step. If the op parameter is changed to op=mod for the concentrated force, it is automatically changed for all other \*Cload keywords, as is surface traction internally (at least that is how I understand it). So, I considered adding this setting to a step instead of to the load.
> [@FEAnalyst](#):
>
> Like this ?
I went through topics on this forum, but I still feel that op=new is more powerful and can do everything the op=mod can do. While the op=mod cannot do everything the op=new can do - like disable a load. So if I add it, I would like to keep its setting hidden somewhere deep - not to the Step editor. That is why I was thinking about Controls editor.
> [@FEAnalyst](#):
>
> Perhaps support for `*CONTROLS` should come with a warning like in Abaqus:
I can add a warning like this copied from the Calculix manual to when opening the Controls editor.
---
### Author:  [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)
#### Post date: [May 12, 2024, 7:27pm UTC](https://prepomax.discourse.group/t/a-developer-preview-prepomax-version-v2-0-10-has-been-released/1735/6 "2024-05-12T19:27:32Z")
I was thinking that the other loads/BCs of the same kind could automatically adapt to the new setting but it’s not a perfect solution either. The step controls editor might be a good place because this setting wouldn’t be changed so often. In the future, BC/load manager could be the best location.