Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

BC are deleted or changed every time I open a model, how can I solve this?

Hi,

I use 2022.2 Altair Hyperworks version and every time I open a model, the BCs I created the last time I edited the file are changed or deleted. Constrains are deleted and forces change the application direction. Thus, I have to define them again.

Does this happen to someone else? How can I fix this?

Thanks

Find more posts tagged with

English

HyperMesh

Accepted answers

All comments

Jason_Craanen

Hello,

No this is not a typical behavior.

What solver are you using?

Can you share the model or the setup?

You might also want to try exporting a solver deck to verify your setup.

thanks

jason

Maialen

Hi,

I am using Abaqus solver.

I am afraid that for security reasons I am not sure I can share the files. But, I just created the BCs from the menu below, shown in the photo.

As I mentioned, once I close the file, when I open it again, some BCs are deleted or changed.

First picture, what I originaly created, second, what appears when I open the file again.

Thanks!

Community-Pasted-Attachment-1706163782830.png

Community-Pasted-Attachment-1706163808689.png

Jason_Craanen

Hi,

I am using Abaqus solver.

I am afraid that for security reasons I am not sure I can share the files. But, I just created the BCs from the menu below, shown in the photo.

As I mentioned, once I close the file, when I open it again, some BCs are deleted or changed.

First picture, what I originaly created, second, what appears when I open the file again.

Thanks!

Since you can't share your model, I would make sure you are looking at the input decks. That is true way to verify. Visually what I see is the difference between legacy loads and the new migrated loads. No loads should be changed or deleted.

https://help.altair.com/hwdesktop/hwx/topics/pre_processing/entities/loads_r.htm

Dan_Casey

I am having this exact same issue (with 2022.3 or also in 2025). I don't want my classic loads to be migrated. The migrated loads do not write out correctly, so that's a problem. Is there way to stop it from converting the loads?

Jason_Craanen

Hello,

We have moved away from classic loads. Default is to create as migrated. PLease refer to this article about why the changes

Also, what do you mean not written out correctly. There should be no difference between the loads from the solver perspective. Only change is how they appear in Hypermesh.

https://community.altair.com/discussion/34236/architectural-changes-in-abaqus-user-profile-from-hypermesh-2022

Dan_Casey

The *BOUNDARY constraints are grouped with the wrong values (1-6 instead of 1-3) and the *CLOADS are missing completely when exported. I understand that the migrated loads are supposed to be a visual thing only but my models are not exporting correctly with the standard.3d template.

Dan_Casey

I should note that the issue is with any/all models. It is not specific to this particular model.

Jason_Craanen

And you have verified this in the latest version? Are you able to share a simple model as I a not able to replicate the issue.

Dan_Casey

The issue is specific to 22.3. In my troubleshooting, I have found that if I use the standard.3d template from the 23.1 install, then the problem goes away. So, I think something is wrong or corrupt with the 22.3 templates locally. I could share a model with you via email if you like but I think I have a solution now, and we are scheduled to switch to 2025 later this month so it may be a moot point.