Simsolid vs. Hypermesh + Optistruct: When You Actually Need a Mesh
When meshless SimSolid is enough, and when HyperMesh and OptiStruct earn their time.
Simsolid and Hypermesh now also appear under the Simcenter brand; the product names below match the way they are listed across our product pages.
What meshless actually changes
Simsolid does not discretize your part into elements. It works on the original CAD solids and builds local approximation functions over the geometry itself, then refines those functions adaptively until the solution stops moving. In practice, that means no mid-surfacing, no defeaturing, no cleanup of sliver faces, and no equivalencing between assembly components. You import the assembly, define the connections, apply loads, and solve. Small fillets, bolt heads, and stamped features that would each cost you meshing time simply stay in the model.
Hypermesh and Optistruct take the opposite approach, and that is exactly the point. You control element type, size, order, and quality, which means you control where the solution is accurate. That control is pure overhead when you do not need it, and irreplaceable when you do.
When Simsolid is the right call
While these are not hard and fast rules, these are best practices from when our customers are finding the most success. Reach for Simsolid when speed and breadth matter more than local precision:
- Concept and trade studies. Comparing six bracket variants for relative stiffness, where you care about the ranking rather than an absolute stress number.
- Large assemblies. Frames, weldments, and enclosures where meshing hundreds of components is the entire cost of the study.
- Design-in-the-loop checks. A designer who needs to know whether a change made things better or worse, the same day.
- Global load paths and modal behavior. The first few natural frequencies, gross deflection, and how load travels through an assembly.
- Geometry you did not create. Supplier CAD that arrives dirty and would otherwise need hours of repair before it is meshable.
When you actually need a mesh
Move to Hypermesh and Optistruct when the answer has to survive scrutiny at one specific location:
- Durability and fatigue. Life prediction is driven by local stress gradients at notches and welds. You need controlled element size through the notch, typically four or more elements across the radius, and a mesh you can defend in a review.
- Nonlinear material and large displacement. Plasticity, hyper-elastic seals, and post-buckling response all depend on element formulation choices.
- Composites. Ply-level layup, orientation, and failure indices are element-based by definition.
- Optimization for manufacture. OptiStruct topology and gauge optimization with draw direction, symmetry, minimum member size, and extrusion constraints remains the benchmark.
- NVH and frequency response. Element size has to resolve the shortest wavelength of interest, usually six to ten elements per wavelength.
- Certification and test correlation. When the deliverable includes a documented mesh convergence study, you need the mesh.
Acceptance criteria to hold yourself to
Neither tool protects you from an unconverged answer, so set the bar before you solve. In Simsolid, run successive adaptive passes and accept the result only when peak displacement and the stress in your region of interest change by less than roughly five percent between passes, and when the reaction forces balance the applied load. In Hypermesh, keep element quality inside the usual gates: Jacobian at or above 0.7, warpage under about 15 degrees, aspect ratio under 5, and at least two second-order elements through the thickness of any part loaded in bending. Then refine once more and confirm the peak stress has stabilized within five percent. If it has not, you do not yet have a result.
The two-stage workflow most teams settle on
The mature answer is rarely one tool. Use Simsolid early to explore the design space, eliminate weak concepts, and find where the load actually goes. Then mesh only the region that survived, drive it in Optistruct with the boundary conditions the Simsolid study identified, and spend your meshing hours on the one area that decides the design. Teams that adopt this split usually report the same outcome: they run far more studies, mesh less often, and the meshes they do build are better targeted.
Common pitfalls
- Reading a singularity. A sharp reentrant corner produces an unbounded stress in both tools. Model the real fillet, or evaluate away from the corner.
- Accepting default connections. SimSolid bonds contacting faces automatically. If a joint slides or separates, define it, otherwise your assembly will be stiffer than the hardware.
- Feeding SimSolid stress into a fatigue calculation without correlating one case against a meshed model first. Correlate once, then trust it within that class of parts.
- Meshing out of habit. A week of meshing to rank three concepts is a week spent buying precision nobody asked for.
- Mismatched boundary conditions. When the two tools disagree, the loads and restraints differ more often than the solver is wrong. Check those before you blame the physics.
- Skipping convergence entirely. A single pass in either tool is an opinion, not a result.
Getting the split right for your team
The short version: if the decision is comparative, structural, and needed soon, SimSolid is almost certainly enough. If the number goes into a fatigue calculation, a certification package, or a manufacturing-constrained optimization, mesh it in HyperMesh and solve it in OptiStruct. TrueInsight is an Altair and Siemens channel partner, and we help engineering teams set this threshold deliberately, including benchmark runs on your own geometry, onboarding, and training. Talk to our engineering team about a workflow review.
