I didn't take any offense or even read that you questioned my motives. I do market Roshaz. It has been around for a few years, but back to your question.
All software packages have ways of handling boundary conditions. In some, you apply conditions to entire surfaces. In others, localized constraints away from areas of critical interest. In some, balancing forces as much as possible and letting single node boundary conditions "clean up" the round-off error in the calculations is chosen.
Load path follows stiffness. This is often why stresses are higher in corners of cut-outs...corners are geometrically stiff. Most softwares apply a very high stiffness to boundary conditions (1e9 whatever units, for instance). These virtually rigid hardpoints insure that your model doesn't "drift off in to space", but it may also alter your load path if applied incorrectly.
Take the chair example from my previous post. With even one leg fully fixed, try to push the chair across the floor. What happens? Well, instead of the chair sliding like it probably would in "real life", it is bound at that one leg and all the load goes in to bending that leg, so it has a high stress. Fix all four legs and the load is carried by all four. Apply springs approximating friction and your analysis results may be closer to accurate.
In this case, there is a rigid body mode...translation across the floor. Linear analysis probably wouldn't be the most accurate, and using a hard constraint instead of Greg's springs probably would show the best result either.
You have to have a variety of "weapons in your arsenal" and understand how to properly employ them. Each of these methods provide speed, accuracy, precision, all of the above, none of the above...
Garland E. Borowski, PE
Engineering Manager
Star Aviation