922986a3f9
It turns out that we have another bug in Uranium: Transformations from 3MF files are not applied to the platform mesh. This makes sense because UM.Scene.Platform takes the mesh data (without transformations) from the node that it read and squashes that into the SceneNode for the platform. This SceneNode already has a transformation for the platform offset. The 3MF node also has a transformation from the 3MF's convention to have the origin in the front left. The 3MF reader then squishes the transformation from the node into that. To fix this we'd need to either: * separate the transformation of the 3MF file from the transformation from the 3MF convention to have the origin in the front left, so that we can pick and choose, or * remove the transformation from the 3MF convention and apply it only on loading normal printed meshes, and then modify all of the 3MF platform files. Both require significant effort. So instead I applied the transformation directly to the vertex data. To do that I imported the file into Blender using my own Blender plug-in, exported to STL and imported that STL again to apply the transformations, and then exported the file from Blender again. In Blender I also combined a lot of flat faces together, which reduced the file type losslessly. Contributes to issue CURA-7534. |
||
|---|---|---|
| .github | ||
| cmake | ||
| cura | ||
| docker | ||
| docs | ||
| icons | ||
| plugins | ||
| resources | ||
| scripts | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| .pylintrc | ||
| build.sh | ||
| CMakeLists.txt | ||
| contributing.md | ||
| cura.appdata.xml | ||
| cura.desktop.in | ||
| cura.sharedmimeinfo | ||
| cura_app.py | ||
| Dockerfile | ||
| Jenkinsfile | ||
| LICENSE | ||
| pytest.ini | ||
| README.md | ||
| requirements.txt | ||
| run_coverage.py | ||
| run_in_docker.sh | ||
| run_mypy.py | ||
| screenshot.png | ||
| test-in-docker.sh | ||
Cura
Ultimaker Cura is a state-of-the-art slicer application to prepare your 3D models for printing with a 3D printer. With hundreds of settings and hundreds of community-managed print profiles, Ultimaker Cura is sure to lead your next project to a success.
Logging Issues
For crashes and similar issues, please attach the following information:
- (On Windows) The log as produced by dxdiag (start -> run -> dxdiag -> save output)
- The Cura GUI log file, located at
%APPDATA%\cura\<Cura version>\cura.log(Windows), or usuallyC:\Users\\<your username>\AppData\Roaming\cura\<Cura version>\cura.log$USER/Library/Application Support/cura/<Cura version>/cura.log(OSX)$USER/.local/share/cura/<Cura version>/cura.log(Ubuntu/Linux)
If the Cura user interface still starts, you can also reach this directory from the application menu in Help -> Show settings folder
For additional support, you could also ask in the #cura channel on FreeNode IRC. For help with development, there is also the #cura-dev channel.
Dependencies
- Uranium Cura is built on top of the Uranium framework.
- CuraEngine This will be needed at runtime to perform the actual slicing.
- fdm_materials Required to load a printer that has swappable material profiles.
- PySerial Only required for USB printing support.
- python-zeroconf Only required to detect mDNS-enabled printers.
Build scripts
Please checkout cura-build for detailed building instructions.
Running from Source
Please check our Wiki page for details about running Cura from source.
Plugins
Please check our Wiki page for details about creating and using plugins.
Supported printers
Please check our Wiki page for guidelines about adding support for new machines.
Configuring Cura
Please check out Wiki page about configuration options for developers.
Translating Cura
Please check out Wiki page about how to translate Cura into other languages.
License
Cura is released under the terms of the LGPLv3 or higher. A copy of this license should be included with the software.