Ask HN: Best Graphics libraries to build CAD solutions?
I am building custom CAD software for electrical and mechanical design. Which Graphics libraries or solution do you recommend? And is Java 3D API viable?
Some helpful links:
http://www.publicworksgroup.com/blog/2012/02/will-gaming-eng...
https://www.unrealengine.com/en-US/spotlights/meshmatic-opti...
https://www.researchgate.net/figure/Unity3D-Game-Engine-and-...
The other options I considered were: - pixi.js (very popular and active, very high performance, too low level for my needs) - fabric.js (also very popular, similar to konva but does not support layers functionality)
Konva seems to be very actively maintained, and has been around for several years. Users in forums seem mostly happy with it. Very simple to use too (I'm just starting with it, so not much experience).
If you're looking more of a Constructive Solid Geometry based web solution jscad/CSG.js.
If you want something more turnkey with a BREP kernel look at what the folks at https://www.autodrop3d.com/parametric-cad.html and https://buerli.io/ are building. Super interesting.
Not affiliated with the above companies, I just do dev on related software.
Here are some more CAD apps using Qt: https://en.wikipedia.org/wiki/Category:Engineering_software_...
(Although Fusion 360 was launched June 2013, nobody edited the wiki page to include it yet.)
With Blender you get advantages of open source, game engines and a fairly extensible 3d toolkit.
[1] https://github.com/dmsurti/reynolds-blender
[2] https://github.com/dmsurti/reynolds
Disclaimer. I am the author of [1] and [2].
- 1) C++ : I think many, if not most 3D graphic libraries are based on C++ language. I am no specialist here.google it.
- 2) java : I use java3D but I believe there are now other more active 3D apis .Like JMonkey.
- 3) javascript/typeScipt : If you use the web as your target, I think the best-and-easiest 3D API is clearly BabylonJs. I use it and I think it is super easy to begin wih.
Thierry, https://free-visit.net
I’ve built a couple of moderately advanced CAD/CAM/CAE apps with WPF + Direct3D 11. Both me and my clients were happy with the software.
You don’t want C++ for 2D GUI parts, or other higher-level pieces like disk I/O or networking. It’s too low-level, and too unsafe which inevitably gonna cause issues once your code grows complex enough. If you only want to support Win10, UWP might be even better because easier to integrate with Direct3D, for WPF you’ll need to write a page of C++ code to make sense of DXGI surface sharing (WPF renders with DirectX9 not D3D11, but it’s possible to pass frames in VRAM by sharing a texture).
On Windows, you want Direct3D for the GPU API. If you have a good PC with a recent nVidia card all of them gonna work great. However, as your install base grows, you’ll inevitably have to deal with Intel and AMD GPUs (Intel only supports VK since Skylake), GPUs older than a few years, outdated GPU drivers, and other shenanigans. Direct3D is way more reliable than GL or VK in these cases, because supported by MS (GL and VK are only supported by GPU vendors), better integrated into Windows (major parts of D3D are in dxgkrnl.sys kernel mode driver), and used a lot by the OS itself (since Vista, desktop compositor uses D3D to render desktop; in Win10, all UWP apps like calculator render with D3D 11).
You do want C++ in the backend. Not just because D3D (that alone is solvable with SharpDX and others), because too many C++ libraries useful for CAD were written over the course of decades. The 3 most useful for me were DirectXMath, Eigen, and Geometric Tools. Fortunately, interop between C++ and C# in the same process is both simple and efficient. On Windows I usually use COM interfaces created by C functions exported from a native DLL.
Game engines are huge, and designed for different use cases. They are trying to render stuff at refresh rate of the display; you don’t want that in a CAD app, your only want to render frames when things change. They assume most things are immutable once loaded from disk and rely on offline pre-processing for a lot of things, while CAD apps need to import whatever, and many things are user-editable. Game engines often strive for photorealistic rendering. You probably don’t need deferred shading or volumetric lightning in your CAD app, let alone water, vegetation, day/night cycle or character animation. All these features complicate a lot of things in game engines.
If you want to be able to port to non-Windows, look for a GPU abstraction library as opposed to a game engine. For example, I have positive experience (unrelated to CAD) with this library http://diligentgraphics.com/diligent-engine/ It has “engine” in the name but I don’t think that’s an engine, it’s a GPU abstraction library which was exactly what I wanted.
[a] While getting a “Hello, world” GUI working with GTK-rs on Windows is an exercise in frustration, Qt on Rust is harder as it requires generating bindings due to the C++ API.