-
-
CuraEngine
Powerful, fast and robust engine for converting 3D models into g-code instructions for 3D printers. It is part of the larger open source project Cura.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Nah. For Prusaslicer is the same, you even have to enable a specific setting for it to show up. It's considered an experimental feature in most slicers, not only in Cura. Autodetetction is still pretty sloppy. The only slicer that has a reliable feature and angle recognition is Simplify 3D. But that's not an option anymore.
Bridges are hard to detect because of the workflow of the slicing engine. To put it simply: a bridge cannot be detected until the perimeter is layed down. But since both in the Cura Engine (which btw is now also at the core of the perimeters in PS) and in the Slic3r the Area generator operates simultaneously on periters and skin, it's impossible to inject in the pipeline and change the skin orientation. For two reasons: -First, they cannot detect a bridge because the start and end point are arbitrary and not static. It does make sense for us, but not for the algorithm. -Second, they cannot define an orientation. It cannot see that is a rectangle, and that therefore it should be best to lay the skin following a path parallel to the longest side.