4 ms·
I don't get why a new polygon data format is needed at all. Sculpted models are always on polygons, and that's good, but almost as much bulk of 3D models are CA
by numpad0 5y ago
I don't get why a new polygon data format is needed at all. Sculpted models are always on polygons, and that's good, but almost as much bulk of 3D models are CAD models "rasterized" into triangle polygons and that's just pain. Aside from patents and/or rights reasons, why can't we just pass around CAD data to feed CNC machines?
- Const-me 5y agoSome parts of the 3MF are actually good. I like the spec documents winding order of the meshes. The format includes units, and these optional 4x4 transformation matrices — both are useful. As for need of the new formats, for one, modern CAD formats are insanely complex. These IGES/STEP/BREP files require many megabytes of very complicated code to deal with, such as this library https://github.com/tpaviot/oce https://github.com/tpaviot/oce These formats may even contain proprietary extensions. Also, they need non-trivial processing power to handle. Many people wouldn’t want a Core i7 with gigabytes of RAM in their 3D printers, inflates hardware cost and software complexity. Besides, we now have high-resolution 3D scanners, and CAE software which algorithmically optimizes models by running numerical simulations. They both output triangle meshes instead of CAD files. Scanners often output point clouds one can convert into triangles, but hard to convert into CAD formats. I just don’t like the 3MF implementation too much. XML is fine for kilobytes of data, but not many megabytes. If I would be designing that format, I would probably made it binary. Maybe EBML https://en.wikipedia.org/wiki/Extensible_Binary_Meta_Language https://en.wikipedia.org/wiki/Extensible_Binary_Meta_Languag... would work for that; it does fine for MKV videos, which is also a huge pile of structured data with non-trivial performance constraints for producers and especially parsers. Another minor thing, it was not the best idea to make name start with a digit. Most programming languages forbid identifiers like that for their classes / functions / namespaces / modules.
- mch82 5y agoThere are a few goals for 3MF. One is to have a common format that is portable across tools made by the big companies participating in the consortium. Another is support for specifying material in addition to shape. STL can represent a part, but can’t distinguish it as a specific metal or plastic. STL also can’t specify color. Those properties can be used in engineering software to simplify analysis and visualization. 3MF also supports multiple parts, which is useful in a multi-material build. For example, when a dentist 3D prints a mouth model they might use white for the teeth, red for the jaws, and a removable support material. With STL each of those sub-models would be a separate file, meaning the 3D printer operator would need to properly position them and choose appropriate materials at build time.
- ddingus 5y agoI've not seen it used too much, but STL does represent multiple parts.
- himinlomax 5y ago> why can't we just pass around CAD data to feed CNC machines? CAD data for products like Fusion360 or SolidWorks depend on a geometric modeling kernel, which is a complex piece of software. To do anything with that data, you need to run the kernel, and you need to run it the same way the software package does. While there is an open source kernel (OpenCascade), it's not as fully featured and in any case not compatible as the industry leader Parasolid. To use CAD data in a printer or CNC, you'd possibly need to pay a license for the kernel, but also have the exact version available and therefore dozens of versions for compatibility, you'd have to support and debug running all those complex kernels, handle compatibility upgrades, have enough storage CPU/RAM/disk and so on. And then subtle bugs in different versions/kernels would result in different results. Imagine the support nightmare.