Show HN: Nasscad – local-first 3D CAD for browser and Windows
Posted by Nasser-13 17 hours ago
Comments
Comment by Mashimo 16 hours ago
* Mouse over text takes too long, it should be visible instant. When I'm searching for a tool I don't want to wait 500ms for each symbol
* Even empty it feels more laggy then onshape on same device / browser.
* When I did a boolean operation there is no popup or similar where I can choose the tool and target. It's all based on selection order? How do I choose 2 tools and one target, or the other way around.
And it's all based on a single 16 000 large c++ file? https://github.com/Nx-Nass/NassCAD/blob/main/MEDUSA_SOURCE/n...wut? That whole repo seems a mess.
Comment by gkhartman 1 hour ago
Comment by fedpost 15 hours ago
That leaves cloud only options like on-shape which means they get to hold your project files hostage. I'm not sure why any business has ever come to the conclusion that losing control of their design work is acceptable but here we are.
Comment by WillAdams 15 hours ago
- FreeCAD --- exactly what it says on the tin, and making huge improvements, so that I am quite hopeful of 26.3
- SolveSpace --- surprisingly capable/nimble/lightweight
- Dune 3D --- the new kid on the block, it is quite workable, and has quite good documentation: https://docs.dune3d.org/en/latest/simple-part.html
(and for the hardcore programmers there are OpenSCAD and derivatives such as PythonSCAD)
Wouldn't the compute from the tokens for these projects be better used improving existing projects? (there are more of these new 3D CAD tools than I can count: Cadivari, Layerling, OpenSketch, &c.)
Comment by YuechenLi 14 hours ago
SolveSpace is still fairly limited on what it can do in terms of features such as fillet/chamfers, so it's not really suitable for pro work right now
For projects like SolidCraft, the SMLib kernel they are currently porting to Rust from Nvidia is currently about a decade behind OpenCascade, nevermind Parasolid/ACIS as they are still converting all geometry to NURBS instead of preserving analytical geometry, which means that their initial development is easier but it creates a near infinite amount of edge cases once they start going heavy into booleans and fillet/chamfers.
Comment by tixylix 6 hours ago
Where are you getting this information from? Booleans and fillets at least use analytic geometry:
Analytic fillets:
https://gitlab-master.nvidia.com/omniverse/solidmodeling/-/b...
Analytic surface intersection (example of sphere/cone) used by booleans:
https://gitlab-master.nvidia.com/omniverse/solidmodeling/-/b...
Comment by YuechenLi 2 hours ago
Comment by tixylix 2 hours ago
Fillets: https://github.com/NVIDIA-Omniverse/usd-brep/blob/main/sourc...
Intersections: https://github.com/NVIDIA-Omniverse/usd-brep/blob/main/sourc...
Comment by aothms 14 hours ago
Comment by YuechenLi 13 hours ago
For your application in IFC, the architecture difference between OpenCascade and SMLib doesn't matter as much, but a geometric modeling kernel for mechanical CAD has much stricter requirements in terms of geometric correctness, which is the reason that Rhino, despite being BRep and widely used in architecture, isn't used very much in mechanical CAD at all.
Comment by aothms 12 hours ago
Comment by WillAdams 12 hours ago
Comment by YuechenLi 11 hours ago
Comment by Mashimo 15 hours ago
One of those new *craft apps that try to clean room copy well known commercial solutions. Though apparently it's currently in a very early stage (buggy)
Comment by cassianoleal 15 hours ago
Comment by syntaxing 13 hours ago
Comment by RobotToaster 16 hours ago
Comment by SoKamil 17 hours ago
Comment by YuechenLi 16 hours ago
Comment by taylor-tg 16 hours ago
Comment by Mashimo 16 hours ago
Comment by WillAdams 16 hours ago
>Download the Source code ZIP below and extract it. It includes the application, its libraries and the OpenCASCADE WASM/data files.
Comment by jqpabc123 17 hours ago
Comment by moymoteapp 10 hours ago
Comment by Forsaken_Parfai 17 hours ago