Warning Message G3057

[milani]

I updated nastran at 2018 version.

Since when I updated it, in my analysis I obtained this warning message.

I'm sure that the indicated property is referred to a material with a density.

The same model running with autodesk 2017 don't take me this message.

In the nastran .nas file the property referred correctly to the uinque material model.

Can anyone help me?

Best regards

Stefano

[John_Holtz]

Hi Stefano,

Thanks for noticing that the message is occurring with Nastran 2018. I have noticed that message when using In-CAD (which uses the same Nastran solver), but I did not pay too much attention to it. I did not make the connection with 2018.

Have you noticed if the message occurs in all models? Or maybe the warning only occurs when there are certain element types (like rigid connectors or something). I will see if I can locate one of my models with the warning, but any insight would help.

[John_Holtz · Accepted solution]

Sorry, I should have checked ALL of our internal information before posting instead of just checking SOME of it.

It looks like development is aware of the problem, and that it occurs with beam or line elements. So we are "working" on a fix.

[milani]

Thanks,

in my model I have a beam element.... However, the property 14 is referred to a solid property, and this message removed if I set partgeomout=off

Best regards

Stefano

[GerryJDail]

I have noticed this error message coming with solid element properties as well. It does not always occur, however. I solved a simple problem with no such warnings, but other, more complex models always displays this warning. I assume that unless I am employing gravitational force, this is not an issue? Please confirm. Cordially, Gerry J. Dail, PE

[milani]

I notice that if I use gravity load the warning occurs but the results include this load.
I however would like to have a confirm from Autodesk

Best regards
Stefano

[costanzofa]

Is there still a fix in the works for the 2018 version of Autodesk Nastran to take care of this issue, or has this already been implemented?  If not, will there be a patch coming soon to address this?  Thanks!

FAC

[KubliJ · Accepted solution]

Hi FAC,

I am sorry, the issue has not been resolved yet and I do not have an ETA for when the fix will be released.

Sorry for the inconvenience.

Thanks,

James

[costanzofa]

Thanks for the response . I'll keep an eye out for a future fix.