ahoeben

Just to be sure: you can see the g-code commands or you cannot see the g-code commands? If you can see the g-code commands, then that's where the responsibility of Cura ends. If the gcode commands are there, but your printer ignores them, then that is up to your printer (firmware).

Retraction amount is a per-extruder setting, and must be queried from the current extruder stack from cura.Settings.ExtruderManager import ExtruderManager ... extruders = ExtruderManager.getInstance().getActiveExtruderStacks() line_width= extruders[0].getProperty("retraction_amount", "value")

You could try "Union overlapping volumes" in the "Mesh fixes" section.

The little star is a mark to show that there are settings changed relative to the profile you have selected. These settings were loaded with the project. So, as far as I can see, the settings were indeed saved in the project and restored when you loaded the project. Can you elaborate why you think that you have to manually keep track of settings after saving and loading back a project file? Because Cura should save the settings with the project file (and as far as I can tell from the screenshot, it seems to do just that).

That is exactly what Cura does, when loading a project file. Unless you told it to load just the models, and not to ask you again. In de General preferences in Cura, what does "Default behavior when opening a project file" say? Are you saving projects after making your tweaks? File -> Save project...

There's an extended support blocker tool available in the marketplace: https://marketplace.ultimaker.com/app/cura/plugins/5axes/CustomSupportEraserPlus

You are welcome! Note that the Sidebar GUI seems to be "addictive"; once you get used to it, Cura without the plugin is just a bit less nice to work with. The plugin always needs to be updated for new versions of Cura. I try to publish such updates in a timely fashion (normally during the beta period of a new Cura version), but sometimes you have to wait for a couple of days.

I am sorry I made you feel condescended, I will stop wasting my time by further trying to help you. Good luck with your endeavors!

To answer @Darinth's question, for the benefit of other people finding this thread, messages from UM.Logger should end up in Cura.log and the console output (with the --debug flag). If it does not, then the most likely reason is that the code is not getting executed.

In your code, the actual processing is only executed if the script is run outside of Cura. That is what that line "if __name__ == '__main__':" does. The "# Multiprocessing" is just a comment and does nothing. Change this: if __name__ == '__main__': # MultiProcessing with Pool() as p: resultat = p.map(traitement_gcode_lineaire,liste_traitement) To this: with Pool() as p: resultat = p.map(traitement_gcode_lineaire,liste_traitement) Note that I changed the indentation of those two lines. This is important in Python. It would be better if you change the functions you define into methods of the class, but that takes more modifications than I care to do right now. I have not tested your code, but at least this way Cura should try to run it. For further questions, it is probably better to start a new thread than to tack onto a non-related 6 year old thread.

There is no information in this statement that enables anyone to give you any help or advice. What are you doing? How are you doing that (post a link to code you are using). What happens when you run the code? How does it "not work"? Do you get specific error messages?

I don't think there have ever been manual extrusion controls in Ultimaker Cura, since version 2.x. At least, I can't remember adding them; I could not get my head around a good way to handle multi-extusion printers (switching active extruders, showing the currently active extruder), and ran out of time and energy. You may have been using a different flavor of Cura before (the Lulzbot edition?)

I think this is an oversight, resulting from using a low resolution display and possibly having a couple of plugins installed that add icons to the toolbar. One workaround would be to install the Sidebar GUI plugin from the Marketplace. It rearranges some UI elements, and as a side-effect it mitigates this particular problem.

There is no user-facing way to control spacing and orientation when using Arrange all, in any version of Cura sofar.

To my knowledge, neither of these issues are related to the Maximum Resolution setting.

I really cannot answer that question, because I don't know what other issues you were having with the printer.

I don't fully understand why exactly, but lowering the `Maximum Resolution` setting (under `Mesh Fixes`) to 0.2 or lower seems to fix the issue. See https://github.com/Ghostkeeper/SettingsGuide/blob/48b3c7902c6401cf43fffd14795947c74cd02275/resources/articles/meshfix/meshfix_maximum_deviation.md for more information about the setting

Use File -> Save project... A project contains the model and your settings; an exported model only contains the model (geometry).

It is always hard to be sure with just a screenshot to go from, but try setting the Hole Horizontal Expansion to 0.

Before you start installing shady dlls from "some site someone recommended", please try installing a recent driver for your GPU. For example this driver for the 840M GPU, straight from nvidia: https://www.nvidia.com/download/driverResults.aspx/84891/en-us/

Your model is "non-manifold". For more information, see this article: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/troubleshooting/missing_parts.md#non-manifold-meshes

The correct internal name of the "Connect Infill Lines" setting is zig_zaggify_infill

Speicifically, the UM 2+C uses this version of Marlin: https://github.com/Ultimaker/UltimakerMarlin/tree/Ultimaker2%2BConnect Support for the G4 "dwell" command (to pause for a number of seconds) seems to be absent from this version.

AFAIK, hidden inside each UM printer is a fork of a rather old version of Marlin. However the modern ones (Ultimaker 3 and newer, including the Ultimaker 2+ Connect) have a proprietary linux-based firmware shell around that Marlin-based controller.

There is no setting named "connect_infill_lines", so passing that is no use. I think you have to pass booleans as true or false, not as "true" or "false". -s connect_infill_polygons=true \ -s connect_skin_polygons=true \