Show HN: Hestus – AI Copilot for CAD
Why we’re doing this: Mechanical engineers excel at generating initial design concepts but get bogged down translating ideas into final designs due to tedious, repetitive tasks. Our goal is to automate these mundane processes, allowing engineers to focus on the creative aspects of design.
Having worked at multiple hardware companies—from medical devices to space launch vehicles—we know how often “trivial” components such as manufacturing rigging, get brushed under the table in scheduling conversations. These tasks aren’t necessarily complex, but they take time and still require the rigor of production components. From finding the perfect fastener to making sure mounting holes align, we aim to simplify and accelerate the design process from the complex to the mundane.
We're tackling this problem similarly to how coding copilots help programmers work faster. Initially, rudimentary coding assistants offered simple suggestions like auto-completing variables. Now, they understand complex tasks, write entire code blocks, and help fix bugs. We're taking this step-by-step approach, starting with a beta that focuses on sketching.
Our sketch helper offers design suggestions, such as applying equality constraints to similarly sized circles or adding tangent constraints between lines and curves. While designers can do these tasks manually, they often require dozens of precise mouse clicks. Our software makes suggestions that you can preview and accept to streamline your workflow. Over time we aim to improve at anticipating your needs and expand beyond sketching to other design aspects like resolving interference issues, auto-generating bills of materials with purchase links, and offering manufacturability suggestions.
How this is different from other solutions: we've heard of complete generative part design solutions, but we don't believe this top down approach is the best way to assist mechanical engineers. Engineers excel at and enjoy designing new concepts—we want to focus on streamlining the most tedious aspects. Crucially, we find that generative solutions often overlook manufacturability, a key aspect of design.
We invite you to try our sketch helper and share your thoughts! If you can think of any additional features that would make it more useful to you, we’d love to hear what they are. Any and all feedback is welcome!
s1mon|1 year ago
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/
delhanty|1 year ago
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.
jaktet|1 year ago
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.
SubiculumCode|1 year ago
lima|1 year ago
syntaxing|1 year ago
ultrasounder|1 year ago
DanTheManPR|1 year ago
Automatic drafting is something that I think might be a good target for doing some AI research on. Your prompt exists in the form of the solid model, and it's feature tree and parameters. The output is the lay out views and annotations. It's okay if the output isn't perfect, as I would expect to be reviewing it and doing some tweaks.
Helping with all of the ERP processes involved with releasing and maintaining engineering documentation would be a HUGE time saver. If I could ask a copilot program to start a change request, and give it some basic descriptions of what I'm changing, it would be massively helpful if it could start pulling relevant files, and auto-filling the right requests/forms/whatever to do that process.
kevinsane|1 year ago
blackguardx|1 year ago
2four2|1 year ago
My questions: 1) What's your CAD background? 2) What led you to realize that this was a problem that needed solving?
kevinsane|1 year ago
Animats|1 year ago
Autodesk Fusion already knows how to apply those kinds of constraints. This is an easier way to input them. The general problem is to express "what am I pointing at" in cluttered situations. Just figuring out how to do that was a huge problem in CAD. For decades, you had to have multiple views on screen just to select. The UI for doing it in one view was really tough.
It still doesn't translate well to fat-fingered devices such as tablets and phones. There are lots of construction people who could really use a tablet that has the design, knows where it is in space, and shows what's supposed to go there.
zackangelo|1 year ago
TaylorAlexander|1 year ago
alexose|1 year ago
It feels totally untrained on the step-by-step logic you need to build things in a programatic way. This is likely a problem with not having enough training data.
mc007|1 year ago
whazor|1 year ago
acyou|1 year ago
I tried to run it, but got an API Error:
Due to some internal changes made to the Fusion API, the Add-In: 'sketch_helper' from 'Hestus, Inc.' cannot be loaded. You need to install a new version of the Add-In that is compatible with this version of Fusion.
Can you just put it up on the Autodesk app store?
I struggle with this model, because of the capture by Autodesk and the other CAD providers. If you read the Autodesk EULA, I think it prohibits use of any open-source software in these add-ins. And I don't think anyone can use this software outside of Fusion 360. And if this add-in becomes popular, Autodesk can trivially release something that has the same functionality, built into Fusion 360 by default. And, as you are no doubt painfully aware, the Fusion API can be limiting.
If you can have your LLM ingest a non-parametric CAD model and spit out a parametric model with a beautiful, complete, editable feature tree full of Extrudes, fully defined parametric sketches with these nice constraints, all tied to the sketch origin, now that's something.
I think Autodesk BIM is $5000/mo/user, Fusion is $500/mo/user. I have thought that means the money is in architectural/structural.
As a side note - one other tip I have, for all CAD users everywhere: avoid Tangent relationship wherever possible! Stick to vertical/horizontal on the lines and arc endpoints, and you will be golden. The Fusion sketch solver is badly compromised, it can't do more than two or so simple successive Tangent relations without bugging out. And, my experience with Solidworks is the same, not sure if this is still true.
Curious if you dealt much with the Fusion constraint model, and have any insights into why it works so poorly, or even how it works? Many times, you click on a line, and it turns from blue to black, and back to blue again.
delhanty|1 year ago
In my experience of building a sketcher at D-Cubed for a consultancy client (1995-2000) on top of D-Cubed's DCM, this is because DCM's curves (which are unbounded BTW) are not directed so that there are lots of erroneous solutions to attempting to constrain G1 chains of tangent bounded curves. For example the Apollonius Problem [1][2] of 3 tangent circles/lines has 2^3 = 8 solutions. IMO if John Owen had chosen directed curves for DCM then dragging configurations of tangent circles would be more stable.
I'll end with a quote from the Preface of Julian Lowell Coolidge's 1916 "A Treatise on the Circle and the Sphere" [3]:
> Among the cartesian theorems there is a sharp sub-division between those where the radius is looked upon as essentially signless and those where a positive or negative radius is allowed.
[1] https://mathworld.wolfram.com/ApolloniusProblem.html
[2] https://observablehq.com/@d3/apollonius-problem#
[3] https://en.wikipedia.org/wiki/A_Treatise_on_the_Circle_and_t...
hobofan|1 year ago
That would have surprised me, as most add-ins I am using are open source and the most popular Fusion apps state that they are open source in their store listings and shouldn't have passed reviews if that were the case.
I took a look at the publisher agreement and it does have this section:
> no Open Source Software is or will be included, incorporated or embedded in, linked to, combined, distributed, or made available with or used in the delivery or provision of Your App in a manner that could cause any Autodesk Assets to be subject to any Open Source License.
There is also a definitions section about this that specifically goes into detail about copyleft licenses, so it seems like they just want to stay very clear of the issue of "copyleft poisoning" and exotic licenses, and ensure that if there is any breach of software license terms that liability is on the add-in author.
delhanty|1 year ago
This is always the problem with add-ins like this as a business - you're essentially doing free market research for the application vendor.
kevinsane|1 year ago
acyou|1 year ago
Script Error
The message you received results from an add-in loaded on your machine that has compiled Python code that will be incompatible with the next update of Fusion or is incompatible with the current version of Fusion. This message is displayed when Fusion upgrades to a newer version of Python, and add-ins compiled against the previous version will no longer work.
If the message says, "The script will not be supported in the next version.", this is a warning telling you Fusion will no longer be able to load this add-in with the next Fusion update. When you get the update and the add-in quits working, you'll need to get an updated version of the add-in from the Autodesk App Store or directly from the app developer. Unfortunately, you can't preemptively get a newer version because the new version of the add-in will not function with the current version of Fusion, you will need to wait until after the update.
If the message says, "The script is not supported in the current version.", this is an error indicating Fusion could not load the add-in. You need to get an updated version of the add-in from the Autodesk App Store or directly from the app developer. App developers are contacted to let them know they will need to update their apps to be compatible with the new Python version, and the updated apps should be available as soon as the Fusion update goes out. If an update is not available, you should contact the app developer. App Developers
If you're a developer of an add-in for Fusion, use Python, and deliver any pre-compiled modules (.pyc files) with your add-in, this update will break your add-in. It will be broken because pre-compiled modules are tied to the version of Python used to compile them. Add-ins compiled with the current version of Python (3.7) will not be compatible with the updated Python (3.9) and will fail to load. This change DOES NOT affect any add-ins that do not deliver any pre-compiled modules and the.py source code is available. For detailed information about what you need to do to update your add-in and have it available for your customers at the time when the Fusion update goes out, see this forum post with the latest information.
Then it links to this, which is talking about Python 3.7 vs. 3.9.7, but that's from 2022: https://forums.autodesk.com/t5/fusion-api-and-scripts/import...
Would you need to release the source code then? Would there be the same problem with C++? How can people develop these sorts of apps without having to release the source code?
I'm on Fusion 2.0.19994 x86_64
mianos|1 year ago
This said, it sure looks cool.
What would be good would be something more like "I want to make a shape centered on this object on this other complex object, what's the best way to do it with the simplest constraints". With Fusion there are many ways to do anything and I often watch videos whose producers are way less experienced than me but they often have some really good hints, they have come across themselves or from others.
Like when you ask ChatGPT: "What's the best idiomatic way to do XXX in C++", or similar, say in a language I don't use every day, like TypeScript.
kevinsane|1 year ago
delhanty|1 year ago
Does the current add-in use AI at all?
What is your plan when, in the event of you getting some traction, Autodesk etc. copy you innovations into the main product?
As per my other comments [1][2], I worked on this area at D-Cubed and Solidworks from 1995 to 2002. Feel free to connect with me via twitter DM @delhanty [3].
[1] https://news.ycombinator.com/item?id=41440016
[2] https://news.ycombinator.com/item?id=41440150
[3] https://twitter.com/delhanty
kevinsane|1 year ago
ricudis|1 year ago
donfn|1 year ago
raffraffraff|1 year ago
I always wondered if there's a VR app (or market for one) that can map out an area and let you virtually model your project within it using standard building components (9" solid blocks, cavity blocks, lengths of timber in standard sizes, various sheets materials etc). It should be able to do basic calculations (rafter spans, roof pitch etc). Once you're done, it spits out CAD files, bill of materials etc. Bonus points for looking up local suppliers and offering to order everything for you, or even modifying the design to accommodate what's available.
It's a completely different project and target audience to OP's app, so sorry for the tangent.
jaredmclaughlin|1 year ago
I've thought about this for decks, because they are so often so poorly done, yet the design space is almost entirely constrained by code that essentially boils down to looking things up in a table.
71bw|1 year ago
Very interesting. Where are you located? I guess the US.
Animats|1 year ago
[1] https://impresamodular.com/design-modular-home-plan-using-in...
smcleod|1 year ago
turnsout|1 year ago
[0]: https://glyphsapp.com/features#plug-ins
baq|1 year ago
progbits|1 year ago
Honestly the demo is both convoluted and not convincing, but also trivial and I don't see where AI comes in. The HV feature can literally be `abs(angle-90deg) < 1deg`. And randomly adding constraints without deeper understanding is how you end up with poorly constrained geometry that won't work once you change design parameters.
graypegg|1 year ago
ned_at_codomain|1 year ago
I met a bunch of aerospace engineers a long time ago -- thinking about working on a software product in contract manufacturing or PDM -- and a common theme was the struggle to optimize the design for cost of manufacture.
Seems like something you guys are thinking about if focused on manufacturability.
hulitu|1 year ago
? As someone said: the most expensive is the microcontroller. If you remove it, you save a lot of costs.
kevinsane|1 year ago
mmmaggio|1 year ago
jaredmclaughlin|1 year ago
Feasibility I think can be done by rules checking / constraints but cost has a lot to do with the specific supplier capabilities in several dimensions.
As a machinist , yes, let's have AI do drawings, please. Getting rid of professional drafters was a huge mistake. Modern GD&T is complicated - which brings up an inherent problem. Our system of drafting a6GD&T doesn't have an explicit mathematical model - it's just based on practice. Therefore, you need some form of systemic approximation. There's one from Arizona University that NIST seems to prefer.
The other problem with automatic drawings is design intent. Consider that you may have several ways to dimension a hole, but one of them may more clearly express design intent. Pretend we drill a hole in a cube block. For the centerline of the hole, we have two different surfaces to dimension from in each direction. Depending on how the component assembles, it can make a difference given the assumption that the machining is done correctly.
If the dimensions go left - down, when the part is in the machine, it should be setup and programmed with the references on top and left. Correctly done, the tolerancing constrains not only the size of the component but also the best practice machining strategy. Tolerancing for manufacturability isn't something I hear discussed but should be. The other question is - can that tolerance be directly measured, or will it need to be calculated on the shop floor?
saintradon|1 year ago
saintradon|1 year ago
singularity2001|1 year ago
albumen|1 year ago
christkv|1 year ago
chadnorvell|1 year ago
spc476|1 year ago
bhouston|1 year ago
luastoned|1 year ago
kevinsane|1 year ago
kevinsane|1 year ago
owenpalmer|1 year ago