# V2.1.3 - Problem with FE mesh based selections

**URL:** <https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894>\
**Category:** Bug Reports\
**Created:** [July 22, 2024, 7:49pm UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894 "2024-07-22T19:49:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gunnar](https://avatars.discourse-cdn.com/v4/letter/g/ed655f/32.png) [@Gunnar](https://prepomax.discourse.group/u/Gunnar)\
**Post date:** [July 22, 2024, 7:49pm UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/1 "2024-07-22T19:49:03Z")

</div>

In v2.1.3 it’s currently not possible for me to select individual nodes for creating reference points or coordinate systems, as long as they are not referenced by geometry vertices:

![213](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/f/f38ba78b0077a6161d7e4d30ebc044bf04bcf993.gif)

previous versions:

![211](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/d/d1ff16096d7241beb5cb5ca6175a959466b5c2ea.gif)

I think it’s clear because now in v2.1.3 we have the new window for geometry based selection and guess we need to click on “More” to open the FE based selection window, but unfortunately this button is greyed out.

Same problem when trying to create sections (or BCs/loads) with region type “Selection” for imported mesh files:

![section](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/f/f231552a4f75639d6452c4ad1f9dc7d304835b53.gif)

Switching between “Selection by location” and “Selection by ID” does not help.

---

<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:** [July 23, 2024, 8:42am UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/2 "2024-07-23T08:42:24Z")

</div>

Thanks for the report. There is a nasty selection bug in this version. I will fix it as soon as possible and release a fixed version.

---

<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:** [September 11, 2024, 6:48pm UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/3 "2024-09-11T18:48:01Z")

</div>

Can you confirm this problem is gone in the latest PrePoMax version?

---

<div class="post-metadata">

**Author:** ![Gunnar](https://avatars.discourse-cdn.com/v4/letter/g/ed655f/32.png) [@Gunnar](https://prepomax.discourse.group/u/Gunnar)\
**Post date:** [September 12, 2024, 6:06pm UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/4 "2024-09-12T18:06:53Z")

</div>

Yes I couldn’t find a problem. I just wonder, why from all constraint types only for Rigid body the “More” button to mesh based selection is still greyed out. A feature? 🙂

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

---

<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:** [September 13, 2024, 5:37am UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/5 "2024-09-13T05:37:53Z")

</div>

Well, it is not a bug.

I will try to explain. The rigid body constraint operates on a node set in CalculiX. So it would be sensible that PrePoMax would use a node-set selection for it. A node set based selection is graphically represented as highlighted nodes as can be seen if a Point Spring is created:

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

I did not like this graphical representation for BCs when I was adding them, so I changed the selection to a geometry-based selection. Later, when I was adding rigid constraints, I adopted the same setting. The geometry-based selection is graphically represented as geometry items (surface, edge, vertex):

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

If I would internally operate on node-sets, I would not be able to show geometrical items as they were selected by the user graphically. So, for these items to use mesh-based selection, a node-set must be prepared previously.

---

<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:** [September 13, 2024, 5:38am UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/6 "2024-09-13T05:38:20Z")

</div>

Since the bug is fixed I am closing this bug report.

---

<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:** [September 13, 2024, 5:38am UTC](https://prepomax.discourse.group/t/v2-1-3-problem-with-fe-mesh-based-selections/1894/7 "2024-09-13T05:38:23Z")

</div>


