# PrePoMax testing feedback - suggestions

**URL:** <https://prepomax.discourse.group/t/prepomax-testing-feedback-suggestions/2370>\
**Category:** Feature Requests\
**Created:** [January 7, 2025, 10:45am UTC](https://prepomax.discourse.group/t/prepomax-testing-feedback-suggestions/2370 "2025-01-07T10:45:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [January 10, 2025, 8:31am UTC](https://prepomax.discourse.group/t/prepomax-testing-feedback-suggestions/2370/2 "2025-01-10T08:31:48Z")

</div>

> [@Sound\_Spinning](#):
>
> I’m lost for words on how good a job you’ve done, impressive!

Thank you!

> [@Sound\_Spinning](#):
>
> 1.- Import part names into the tree from STEP assemblies.

I am currently using Netgen to open the geometry, and I think that part names are not read while the geometry is loaded (I might be wrong). However, the decision not to use the part names comes from regeneration. Regeneration can regenerate the model from another .step file, but if the names of the parts in the .step assembly change, some regeneration commands will fail. However, I might look into that since I would also like to have named parts in the assembly.

> [@Sound\_Spinning](#):
>
> 2.- Implement 2-node springs:

There were other requests for this feature so that I might give it a higher priority.

> [@Sound\_Spinning](#):
>
> 3.- Both couplings types:

True, rigid connections are not the best connection type. The distributing connection is already on the request list.

> [@Sound\_Spinning](#):
>
> 4.- Allow for node sets with RP points:

If I understand correctly, there is a need to create a node set shown in the model tree containing a reference point. Is it enough to contain a single RP?

---

_[View the full topic](https://prepomax.discourse.group/t/prepomax-testing-feedback-suggestions/2370)._
