The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
CuraEngine Alternatives
Similar projects and alternatives to CuraEngine
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Nodemon.io
Monitor for any changes in your node.js application and automatically restart the server - perfect for development
-
CuraEngine
CuraEngine is a powerful, fast and robust engine for processing 3D models into 3D printing instruction for Ultimaker and other GCode based 3D printers. It is part of the larger open source project called "Cura". (by ThomasRahm)
-
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.
-
emoj
Find relevant emoji from text on the command-line :open_mouth: :sparkles: :raised_hands: :horse: :boom: :see_no_evil:
-
gcode-estimator
Estimate the length/weight/cost of filament used for a 3D print by parsing the gcode file
-
pyArcus
Python bindings for Arcus communication library between internal components for Ultimaker software
-
CuraEngine
Discontinued 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. (by mashuptwice)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
CuraEngine reviews and mentions
-
Calculating extrusion for custom-generated G-code?
Here (at the bottom of the page) you can find an overview of the calculation and the git repository also holds the entire source code of the Cura Engine (which is the part of Cura that actually does the slicing and G-code creation) where the calculations happen. The repository is in C++, but the calculations are actually universal.
-
✨Cura 5.3.0-beta.1 ✨ ~ 75+ new 3D Printers available + Updated Recommended Menu + Interlocking Structures 🐊
There have been some improvements but I would not say it's fixed yet. 😕 It is my favorite 5.x seam for sure! You can read about the work done here: https://github.com/Ultimaker/CuraEngine/pull/1762
-
New Cura feature! Maximum volumetric flow rate setting!
If you can figure git and out how to compile Cura and CuraEngine from source, you can test it by using the "vms" branch on both my CuraEngine and Cura github forks.
-
maximum volumetric flow setting for Cura!
If you want to contribute by testing it you can find the necessary commits for Cura here and here for CuraEngine.
-
Ultimaker Cura 5.0 Tree Supports 2.0
There's also a pull request on the main Cura repository, seems like it's nearly ready to be merged in: https://github.com/Ultimaker/CuraEngine/pull/1282
-
Pipeline to automate the process from creating 3d objects to start a print job
I am currently developing a pipeline for creating STL files, slice them and create a print job based on it. My setup at the moment is an Ultimaker S5, which offers a simple REST-API, for example starting a job with a G-Code or UFP file. I am using the cadQuery library for creating parametrized 3d shapes and export them as a STL file. I want to use the CuraEngine CLI interface (Backend for Cura) for slicing or their library libArcus (python bindings) but there is literally no documentation or any kind of examples, except the source code. There is also the prucaSlicer, which also offers a CLI interface for creating G-Code, but no support for the Ultimaker S5.
- Ferramenta para automatizar orçamento de Impressão 3D
- Calculo de impressão 3D automático
-
Ultimatemaker Cura 5.0.0 (Problem) Vs. Creality Slicer 4.8.2. As you can see in the video Cura should have done the bridging longwise left to right rather than shortwise. What setting in Ultimatemaker Cura 5.0.0 do I have to change to fix this?
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.
-
How to set up a website to auto generate quotes for 3d printing services
You might be able to use Curaengine to provide weight estimates.
-
A note from our sponsor - WorkOS
workos.com | 25 Apr 2024
Stats
Ultimaker/CuraEngine is an open source project licensed under GNU Affero General Public License v3.0 which is an OSI approved license.
The primary programming language of CuraEngine is C++.
Sponsored