True - I implemented the first Solidworks Autodimension sketch as a contractor around 2002 based upon earlier work that I'd done for a consultancy client at D-Cubed in the late 1990s. I'm sure it could be improved with AI and a large data set of sketches though.
> Solidworks tries to help with this in the form of cycling through what it thinks are the most likely constraints to remove and then re-solving the sketch. It's OK, but that sort of tool could be better.
I agree it could be better. The behavior with under-constrained sketches depends on D-Cubed's DCM, and I seem to recall they were rather floppy. It seems kind of ridiculous to make users jump through the hoops of making sketches fully constrained once they've added the constraints they care about.
Does "fully constrained" mean the simplest set of constraints that yields a shape (volume/hypervolume)? Or something rather more complicated? A simple yes or no, with a pointer to a paper will do!
It's very intuitive if you play around with a CAD program for a bit. There is a free (GPLv3) 2D and 3D CAD program called Solvespace (https://solvespace.com/) that is probably easiest one to obtain and learn. There are detailed tutorials on the website, and you could probably download it and finish the first tutorial in an hour.
the Github page of which has the following footnote:
>I ended up directly using solvespace's solver instead of the suggested wrapper code since it didn't expose all of the features I needed. I also had to patch the solver to make it sufficiently fast for the kinds of equations I was generating by symbolically solving equations where applicable. ↩
Which really impressed me because it was the first graphical and interactive 3D program I tried which felt sort of comfortable and understandable (which is why I mostly use OpenSCAD and similar programmatic approaches).
DCM then chooses one valid solution that it believes is "close" to initial supplied positions/directions/radii etc for the geometry.
For a quick example, see slide 10 in https://docs.google.com/presentation/d/1TiVoKF7mLlF360Oxy8hN... This is just a quick doc I made to show a friend how to use Fusion 360.
I was wondering if AI might help with writing FeatureScript. I’ve only scratched the surface but have leaned heavily on what other people have written for documentation.
A number of popular CAD systems use the D-Cubed 2D sketch constraint solver [0]. Siemens owns this and the Parasolid kernel, along with NX. All have been in constant development since the 80's. I really question what major new problems a startup is going to fix in 2D sketching constraints. I'm sure there a bunch of small quality of life things which may be out there, but most of the hard issues are more 3D or spline related, not finding things which could be tangent or equal.
Probably the biggest paradigm shift with constraints that still hasn't really taken off is what Siemens is doing with SolidEdge. It allows for defining the 3D equivalent of constraints between surfaces, holes, edges, etc. and then using direct modeling techniques to modify solids. Perhaps adding more intelligence to that approach would make direct modeling more popular.
Onshape has innovated in the way that it's brought Google Docs-like collaboration and GITHub like versioning, branching and merging to parametric CAD. Nothing else has these capabilities at the moment. To me that has been one of the most innovative changes in the mechanical CAD industry.
Onshape also has FeatureScript, which is the programming language which describes all the parametric features. Right now, none of the LLMs know FeatureScript well enough to be the least bit useful. They hallucinate wildly. I'd be very happy to have a Copilot for FeatureScript.
[0] https://plm.sw.siemens.com/en-US/plm-components/d-cubed/