Why doesn't NoviPath always detect over-constrained setups before the solver runs?

This check currently runs only when you select faces for both loads and restraints. Face counts are typically small (tens of faces), so the check is inexpensive.

The same check is not yet implemented for Shape-based boundary conditions. It would require testing every surface node of the finite-element mesh to see whether a load and a restraint occupy the same nodes, which is significantly more expensive. That check may be added in a future release; it is not implemented in the current version.

Workaround: Prefer Face selection whenever the geometry allows — NoviPath then rejects adding a restraint face that already has a load. If you must use Shape-based boundary conditions, place shapes so a load shape and a restraint shape do not cover the same surface nodes. When a fixture must constrain the loaded region, add a Load constraint on the load instead of a second overlapping restraint shape. After the solve, treat all-zero (all-blue) displacement or stress results as a possible over-constraint from overlapping shapes.