Seems that when the Exploded View is activated and I attempt to merge coincident nodes, the below graphical irregularity occurs.
Is it just a visual anomaly or are there practical issues ? …I will try it out anyway, but thought you should be aware.
It should be a graphical problem only and should go away once you deactivate and activate the exploded view.
But this should already be fixed in the newest PrePoMax version. Which version are you using?
I am using the latest version 2.2.0
Hmm, for me, it works. Does it go away once you deactivate and activate the exploded view?
@Matej,
Yeah, it still continues after deactivating and re-activating.
I wonder if it has anything to do with unequal number of elements on either surface,
Is it possible to share the .pmx file?
Test - I Beam.pmx (2.2 MB)
Attached.
Edit: Deleted post .
I can reproduce the problem.
First of all, the parts you merged nodes together do not have the same number of elements in the axial direction of the beam, which is why only a couple of nodes got merged. These are the nodes for which the elements get distorted using the Exploded view.
But since the parts share at least a node, they should not move apart when using the Exploded view, so this is a bug in PrePoMax.
Why do you not use one body geometry and apply the Extrude mesh feature? You can even split the front face of the beam and then select all faces while creating the extrude.
1 Like
Hi Matej I don’t it think thats a bug or wrong behaviour. In fact it has allow to expose the issue.
It helped in this case, true. But it should not happen. The idea of the Exploded view is to explode the parts that are not connected. It looks really strange if correctly connected parts get exploded.
These parts were connected by a small number of nodes, so the visual helped to show the problem, but for parts where only a couple of nodes are not connected, it does not help to see them. Some other tools would be necessary, like finding internal faces.
That is why I added a preview feature to the Merge nodes that can be used to visualize the nodes that will be merged.
Anyway, I fixed the problem.
I am changing the topic as closed.