unselectable Node-Sets in Hypermesh 2020.1.1 with OS (only SET_GRID is selectable)
Hi !
Regarding Hypermesh 2020.1.1 with Optistruct-Profile.
Up to Hypermesh 2019 it was possible to select any Nodeset (without cardimages) as output-request.
In 2020.1.1 I found, that only Nodesets with CARDIMAGE = SET_GRID are allowed to be selcted as output-request.
Now all my old .hm-modells have to be updated ? is this a feature or a bug ?
I created a simple test-modell with 2 free nodes to show it to you :
SET #1
Set #2
output-request selector : only SET #2 is selectable
Same example in Hypermesh 14.0 / 2017 / 2018 / 2019 => both sets where selectable.
Best regards,
Klaus
Answers
-
They've implemented these built-in filters that automatically filters the SET Type according to the output request.
Although I think it's not mandatory for the solver, it is always nice to point to the right set type.
Maybe if you go to the old 'control cards' panel, you should probably be able to pick whatever you want.
0 -
Thanks for your answer. I undertand.
Unfortunately th old 'control cards' panel also doesn't help, because the filter also works here (Set #1 will not be accepted).
So there is no other solution for thousands of old .hm-files than updating thousands of nodesets manually to that card-image (when needed) ? Unfortuntaley when updating the cardimage the information of the nodes belonging to tahat set gets lost (must be saved and retrieved). That's nasty.
Best regards,
Klaus0 -
I want you also to know, that if someone tries to do the optistruct tutorials, then there are also nodesets used without cardimage. The tutorials wonÄt work anymore.
As old hypermesh-guy, I also did itaccording to the tutorials (which didn't change in 10 years), and that's is the thankful answer form Altair ? Oh come on...0