Trying to model a 3 dimensional Plate. Using a basic mesh. Whenever I use the parametric models feature to create a mesh, the program freezes then crashes. Attached I have a photo of the mesh I am trying to create and the error I receive. The gusset plate is a standard mesh and works fine, but the automatic mesh feature for basic and standard does not work for the bottom plate. Let me know what I can do.
Here is another photo of the program mid crash after trying to make a basic mesh in the selected area shown on the left. Crashes whether I use a large mesh size or a small mesh size.
Can you please upload the model. Also are you using the latest STAAD.Pro 22.04.00.40 ?
Running into the same issue even when removing the single duplicate node.
Yes I see the crash. I am looking into it and will revert back.
I will have our development team look into the crash and get that fixed. In the meantime as a temporary workaround, you may have to mesh the model in parts using the parametric model. For example, I started with the portion below, merged the mesh, saved the model and then moved on to generate the meshing for the other regions one by one. You will find all of the mesh models in the parametric model and would be able to see how these were meshed. It is critical that you merge the mesh each time after generating every mesh as that is how the nodes of the current mesh will be part of the model and the next mesh that you would generate, would consider the nodes of the current mesh. This would ensure proper connectivity between the adjacent meshes. Also I would suggest that you save the model after each merge mesh operation so that you retain the data up to that point, in case there are further crashes.
I have assigned some arbitrary properties, supports & loading as I wanted to run the analysis to make sure that there are no issues down the line. It worked. You may remove these and reassign as appropriate.
A modified file with the mesh is attached for your reference P3-RS-V010-2 16 in_rev.STD
For the records, a defect#1104892 has been logged for the crash and will be addressed.
Thank you. Hopefully the full issue can be resolved.