ahoeben

Try the Sidebar GUI plugin from the Marketplace. It is quite a labour of love, and in my opinion restores some semblance of sanity to the UI. The plugin will soon be available for Cura 4.4 too.

I don’t use usb printing much -if at all- but I think they all connect to the same one.

The current version of Cura does not have manual port selection, only automatic port discovery. If that does not work, unfortunately you can not currently use Cura to flash the firmware.

It is not necessary on all parts. It does improve stability on some parts.

You can try lowering the Support Horizontal Expansion setting. The STL format does not support multiple separate bodies in a single file. Other formats such as 3mf do. If your CAD software exports 3MF files, that might be an option to load your custom supports and print them as support using the "Per Model Settings" tool.

A .ufp file is "just a zip". You can open it in a zip program (eg 7zip), extract the actual gcode file to edit it, and put the edited file back in the .ufp file.

All third party contributions start as a pull request on github

Cura does not support curves. It only loads polygonal models which don’t have true curves; only estimations of curves by multiple flat polygons.

The logic is here: https://github.com/Ultimaker/Cura/blob/4.4/plugins/CuraEngineBackend/StartSliceJob.py#L428 Cura looks for the text "{material_print_temperature}", "{material_print_temperature_layer_0}", "{default_material_print_temperature}", "{material_initial_print_temperature}", "{material_final_print_temperature}" or "{material_standby_temperature}" in the start gcode to check if the start gcode contains extruder heating commands (so it does not actually care if you use M104 or M109 or not). Cura looks for the text "{material_bed_temperature}" or "{material_bed_temperature_layer_0}" in the start gcode to check if the start gcode contains bed heating command (so it does not actually care if you use M140 or M190 or not). I would argue that "{default_material_bed_temperature}" should be added to that list for consistency. Start gcode snippets often include priming commands. If Cura would insert its preheating before the start gcode snippet, that priming would not work. Unless it is overridden, the "material_print_temperature" setting is set to be equal to "default_material_print_temperature" here: https://github.com/Ultimaker/Cura/blob/4.4/resources/definitions/fdmprinter.def.json#L2141

There is now an updated version of this plugin available through the Marketplace, for all versions of Cura from 3.5 through 4.4.

If you use {material_bed_temperature} or {material_bed_temperature_layer_0} in your start gcode snippet, then Cura won't insert gcode for heating the bed in front of the start gcode.

That is not what is shown in the images though. The yellow top shown in the first and second image - small as they both are - show that there is a top. I cannot see the bottom in the provided images.

I think you mean sub-menus inside Cura as opposed to sub-folders on your harddrive? Unfortunately, that is not something Cura supports right now.

You should be using {material_bed_temperature} or {material_bed_temperature_layer_0} instead of {default_material_bed_temperature}.

That’s a 5 year old vrrsion of Cura you have there. It is no longer supported here. If it is still distributed by a printer manufacturer, please ask them for support. For future reference, if you want people to help you then try making it easy for them. Don’t make people hunt for problems in bad photos of your screen; Your pictures are NOT self-explanatory.

Sure, that could happen. The intent profiles are not magic. They are just a way to select a different combination of setting values that eg sacrifice printing speed for either accuracy. There are physical limitations that make it hard to eg print accurately AND fast. The profiles that ship for the UM3 are intended to be a compromise between the two. Between the UM2 and the UM3, the printhead became heavier (to allow for the printcores and dual extrusion). This made the physical limitations manifest more clearly. For the UM S5 and S3, the gantry became even heavier, which made "intent profiles" more necessary. You can already make your own profile that prints slower to be more accurate. Unfortunately I don't have an UM3, so I would not know what changes to make.

I am fairly certain there won't be profiles in the production version that are not in the beta version. It could happen that intent profiles for the UM3 will be added in a future version of Cura (4.5 or later), but I would not hold my breath.

Those companies that "forget" to share their changes violate the LGPL license. The LGPL license that Cura is licensed under fully allows you, as an enduser, to make changes to the program. Because "the company" used Cura which is licensed under LGPL, they cannot forbid you to make changes to their version of Cura. You are not obligated to share these changes, unless you distribute the changed program. If "the company" distributed their version of Cura to you, you would be in your right to demand the source of the changes. Do note that this is my reading of just part of the rules of the LGPL, and I am not a lawyer (so what do I know?).

I am not "from the team", but I think it is the shear number of profiles that need to be made and tested to support more printer, printcore, material, quality and intent profiles.

Something that is not mentioned in the opening post is that all plugins from the Marketplace need to be updated by developers and approved by Ultimaker staff again. It may take a bit of time before your favorite plugins are all available. I am still working on compatible versions of the Sidebar GUI and the Material Settings plugins. My other plugins have already been approved and are available in the Marketplace.

Cura tries to protect your printer against cold extrusion. Cura tries to see if there is anything in your start gcode that heats up your extruder(s), and bed. If not, it will insert a heatup sequence on its own.

The cause of this issue is that in your start gcode you use the {print_bed_temperature} replacement pattern. Try replacing that with {material_bed_temperature}.

From the top of my head, try this: infill_pattern = = 'grid' if infill_sparse_density >65 else 'lines' Note: “is space is”.

There are companies that take the open source, make changes and give these modified Cura versions to their clients, forgetting to share the changes. This does not make Cura any less open source, but it does make those companies arses.

Depends on what you wan to achieve