Look for the falling ball example in the bConverged CCX version (or this forum itself) Is the mother of all impact simulations on CCX. But don't put too much expectations on results, I don't feel is r
3. In Mecway version 5, the error messages are for the internal solver, not CCX. So you can still use shells with CCX but not with the internal solver. Version 6 which is now in beta has the error mes
1) I haven't looked into this much since I see it as an advanced option that you can do yourself by setting an environment variable. Is that right? Maybe for the next version.
add any new features. All licences that include version 5 are also valid for version 6. That is everyone who bought it after 2015-11-15. Just re-enter your product key to activate it.
I've added gap conductance to my list. Version 6 is nearly up to beta so probably no new features for that though. But it will have many of the common CCX pain points improved on.
No options for show origin and resolution but the next version (v6, beta coming within a couple of weeks hopefully) will store the show origin setting.
For the life of me I cant figure out the 2,2,1 syntax, although it must be a some version of notation for " constrained in x, constrained in z, and multiplier of amplitude value"
Yea TIE is probably more permissive of this kind of thing. In the next version I'll make TIE an easier option by just ticking a box. You probably know this Sergio, but for anyone else, its weakness is
Pyramids are currently a problem and I don't know a practical solution sorry. Version 6 will export them as collapsed hex elements which are OK for CCX but it's hard to do that by hand.
Not yet sorry. The next version (6) will do this though. For now, you would have to save as .inp then run CCX directly. The save step is still a manual process tough.
The PipeClip.liml example using the Calculix solver worked well. The ddfem version didn't run/install for me, but the bConverged version was easy to setup for solver association.