So,

Is anyone else having the issue i am? After some more focused hunting for an alternative in the tools available, i figured out that i needed to project the curve to a surface to obtain what turned out to be a spline, and then remove the original line/s from the filter. I was then able to select and cut the surface with the spline without VCP summarily blowing up.

However, having the app blow up when i have 7 other files open in various states of zoom, orientation, and being used as references and not have some "atomicity" of a database is not just "disconcerting". The user should not have to self-train that horrible geometry might cause a crash today, but not tomorrow. In retrospect, felt like i was ice skating near a chasm, working for days on end without a crash, getting complacent and extending the time between saves. Can some pre-action checking for this scenario be done so the app will gracefully display error messages? ACIS gives me plenty of nags that i'm doing something wrong when i'm really doing something wrong.

If it's any consolation, i do admit that i'm cringing when i look at the unfaired lines i hand-built in DelftShip (free version) being displayed in a very expensive marine engineering program. It shows my lines to be embarrassingly un-faired. I presume that if i built the lines directly in VCP, such noisy jaggies would not be there. On the other hand, VCP doesn't export to GHS file format, and DelftShip free does. I'm going to have to pony up some 175 Euros for DelftShip Professional which has automatic fairing, so my next hull is dramatically free of jaggies.

Fixed in 945.

Tim