>The FluidCAD engine did not start within 30s.
which is an open issue: https://github.com/Fluid-CAD/FluidCAD/issues/80
> closed this as completedon Oct 5
Hmmm?
I tried it again a few days later on a Mac and went through a couple of the tutorials without any major issues.
So yeah, definitely some rough edges at the moment, but once I got past those, the overall experience was surprisingly good.
Yea, especially more so with ArtCraft cloning the more expensive stuff.
It would not surprise me to see ArtCraft versions of DS CATIA/MatLab/Wolfram that can compete with the originals.
Freecad never really worked for me well would get stuck frequently and not be able to figure it out.
The authors have this custom process where humans pick yes/no on features/commits without looking at the code at all. The are abusing many claude 200usd subs and the tokens costs are apparently close to 100k usd.
But still this is very bad news for traditional software.
I’m now using Solidcraft as a daily driver and it’s great. Some areas seem perhaps a bit ‘fragile’ (filleting, possibly surfacing) but overall it’s very stable and usable.
That said, I am working to transition to Solidworks as the noncommercial license is only $24 a year, while Fusion continues locking more and more basic functionality behind the paywall, and their first paid tier costs way too damn much for hobby work.
Took a lot of effort. I was certainly supervising, but I don't know enough CAD to replicate an industrial designed video game controller. It made something that would have been outside of my skillset, and it did indeed hold a real controller on the first print.
https://helios-cad-wasm.yuechenli.chatgpt.site/
Be warned though, the Firmament DSL used is designed to be LLM friendly, so it's a language that's way easier to read than it is to write, and it has a very nontraditional constraint system.
It's easier if I show you some sample code.
https://github.com/yuechen-li-dev/Aetheris/blob/master/fixtu...
However now everything has changed. I personally believe that the days of designing by hand are numbered. I think the current apps are a bit like the early days of AI assisted coding - autocompleting certain manual steps. Compared with full agentic "solve x" prompts.
I've been working on my own AI-First CAD ( and CAM! ), thinking about everything from first principles for AI - is it easier to think in terms of operations? or start with the finished product? I'm pretty happy with the engine ( and kernel ) I've (+agents) built, it can do full assemblies, including interactive sliders to move them etc, and then do the 3 axis CAM ( or export to STL for printing). I'm really interested in genuine feedback if anyone has a few minutes to try it out www.zelm.ai.
I checked out your project but was a bit disappointed to see that it's closed source. As you're probably aware in the last 6 months there have been a ton of new OSS B-Rep kernels and CAD programs hitting the ground, many of them working towards the same goals that you and I have.
It's my personal opinion is that in this new age of AI coding, the best way for a project like this to gain momentum and user base is to make it free and open for other users/contributors to work on and with.
Just my 2c.
I've contributed to open source, and ran my own open source projects in the past, but when everyone can have the software exactly they want it's just a different ballgame. I think the value of Zelm isn't so much the code, but the infrastructure around it to make it a seamless experience.
If there is a feature you want, just ask for it in the chat or via MCP, and it will be added to the backlog automatically.
Open source was never about free as in beer, but in this case Zelm is pretty close to free if you use it as a MCP server.
I think that many tools, services, and programs will be more personalized, and maybe less shared. But that the core building blocks of the tools will stay open and continue to be refined by the community.
When I'm coding with AI, one of the main reasons it's so capable is the ability to build off of languages, packages, and frameworks that are battle tested across many deployments. The end result is better if my (+ my agents) focus is on what's new and different about what I want to create, not reinventing the wheel. So I'll import a proven serial library rather than writing my own, pick the right programming language for my use case rather than writing in assembly.
With regards to your project and CAD, I think it's a clean and efficient interface, and part I generated looked good. Personally I need more traditional CAD features for my day to day (drawings, multi part assemblies, hand editing) but it looks like a good tool for the right use cases.
To finish my open vs closed source thought - have you considered open sourcing your b-rep kernel? Your app may be the secret sauce, but the kernel is boring but vital core. Parasolid has been developed over the last 35 years and is the reference point. NVIDIA open sourced SMLib but it is buggy and incomplete. OCCT exists but doesn't handle fillets well. Zoo spent two years with tens of developers building their kernel from the ground up (also unfortunately closed). There are a dozen new kernels written in Rust on github but none are complete.
I really think that if all of the smart people trying to roll their own kernel worked together and put effort into really completing a good open source kernel, it would be the start of a cambrian explosion of CAD tools and AI enabled hardware engineering tools. Food for thought.
I don't really know much about CAD kernels, and so I really don't think I should be running a cad kernel open source project/community ( which is what successful open source is about ) I wouldn't be able to decide if we should do feature x or not.
> Personally I need more traditional CAD features for my day to day (drawings, multi part assemblies, hand editing)
Zelm supports drawings ( including custom drawings, see Download button ), assemblies ( with movement interfaces, click on Features ), and while it doesn't support hand editing ( i.e. with a mouse ), designs are parametric so you can tweak them ( click on Params down the bottom ).
This is an example: https://www.zelm.ai/p/v8nzvHBhz7?share=Kis1TuAUtwn7nR3VNx-rj...
Is this some kind of joke I'm not getting? People use AI to do things so far outside their competency to the point where they have no idea about anything? I mean, who exactly would trust such a project? I'd rather do it myself.
yes, if you want to do things far outside of your competency
> I mean, who exactly would trust such a project?
Depends how it can be verified. In this case there are potentially easy solutions, print it on a 3d printer and measure it. Is it 30mm across?
And how would iteration look like? It's a million times faster and easier to just navigate around a 3d model, click on the feature to edit, start editing. Describing which feature for the AI to change seems like a nightmare.
I was able to (eventually) get a working file by laboriously describing the geometry of each part and its joinery in exhaustive detail:
https://community.carbide3d.com/t/a-simple-cnc-box-in-depth/...
Next up is adding a hinged lid to the existing sliding and no-lid options.
To be honest, I did not expect it to reach this level of interactivity when I first started it. I only wanted to add few interative features to make CAD by code more enjoyable. Now it has become more of UI driven CAD with the code there when you hit a wall.
I'm going to add tools for surface modeling + tech drawings soon then I'll lock features for v1.
> Model with the mouse. Control it with code.
sounds like what I loved about Flash when I first got into making things. Definitely wanna try FluidCAD now!
Is there a preferred way to discuss with other users (or you) at the moment?
There's one key thing I want to be able to do that doesn't appear to be supported but possibly it's already there but not documented - I haven't investigated properly yet.
Maintainer here. We just merged the long-wanted named parameters capability, so you can try it in the "nightly" builds on github. Not only that, but relation constraints (arbitrary equations on a sketch) and fully parametric parts - regenerated per-instance each with own parameters. Also in the works but not in yet are linking STEP files in assembly (up to the capability of our NURBS kernel) and a fillet and chamfer tool. All that on top of a huge number of geometry kernel bug fixes. We are still not using OCCT, but bringing all this capability to the same few megabyte executable. Oh, and the single-window interface is in. Still looks the same but the next release will be incredibly more complete.
fluidcad appears to be a remarkably good option now - particularly for something that only started development about a year ago.
I have used freecad, solvespace and onshape for at least a hundred hours each to make some reasonably complex parts. Fluidcad resolves pretty much everything I found painful about those options.
I have some more limited experience with Build123d which is also nice, but just not as easy and interactive as Fluidcad.
Fluidcad generates editable code backed on normal 3d cad gui interactions and it works remarkably well.
It’s far easier to manage constraints in Fluidcad where they’re there written explicitly and can be edited vs the experience in Onshape where it “helpfully” adds constraints you didn’t actually want (like if you’re playing around with a semi-constrained sketch to understand some kinematics).
Have only spent about 5 hours using Fluidcad but it looks remarkably useful. It’s actually pretty much what I wished Onshape or Build123d were before I tried Fluidcad.