ahoeben

I would rather focus on getting Cura (or my plugin) to work than on what Github does or doesn't do. Have you had time to check if the Materials page of the preferences works with the Material Settings plugin disabled?

Yes please. I just checked and I cannot replicate the issue with version 3.6.2 of my plugin with version 5.6 of Cura, so it must be related to specific configurations.

Ok, then I have work to do...

I find that unlikely. You just have to attach them in the github webinterface, not as attachments in email replies. In your log file, I see that you have installed the Material Settings plugin, of which I am the author. Since that plugin extensively patches the Materials page, it is a likely culprit for issues like this. Can you try disabling that plugin, restarting Cura, and see if that fixes the Materials preference page?

I am a community contributor. I - and many others who can help you here - have no access to crash reports. In your log file, I see that you have installed the Material Settings plugin, of which I am the author. Since that plugin extensively patches the Materials page, it is a likely culprit for issues like this. Can you try disabling that plugin, restarting Cura, and see if that fixes the Materials preference page?

We can't say much without logs. Cura.log can be found via Help -> Show configuration folder.

Pro-tip: If you install the new script in the "scripts" folder inside the configuration folder instead of in the application folder/bundle (where the default scripts are), the new script will be automatically copied over when you install a new version of Cura at some point in the future.

Either do steps 2-3 or do step 4. No need to do both.

An update in the backend of the Ultimaker Marketplace has caused an issue with who gets to "see" all plugins (regardless of the type of account being an Essentials/enterprise account). The workaround is to log out of your account inside Cura, and then go to the Marketplace inside Cura. You can install the plugin(s) you want without being logged in via the Marketplace dialog in Cura. Then, when you have installed the plugin(s), you can decide if you want to log in again.

I agree. Ultimaker is aware of this. The official workaround is to log out in Cura and then install the plugins from the Marketplace inside Cura. Yes, you can install plugins from the Marketplace dialog inside Cura without being logged in in Cura, just not via the Marketplace website. Finally, it is up to you if you want to log back in again in Cura. Personally I am never logged in in Cura.

Some will say that the print quality of the UM2+ is even a small step above the UM3. The UM2+ gantry is lighter than the UM3 gantry, which means the printer can accelerate faster without ringing and other "mass-induced" artifacts. They are very good printers, and on top of that they are still quite hackable and fully open source. However, the UM2+ does lack some "quality of life" features that the UM3 has, such as much easier hotend swapping, dual extrusion (as you already mentioned), auto leveling, printing via the network/cloud. Note that there's a difference between the Ultimaker 2+ and the Ultimaker 2+ Connect, which is a much more recent printer.

If you install the Startup Optimiser plugin (available from the Marketplace inside Cura, though you may need to log out in Cura before you can install that plugin), you can use the option to "Load only 'generic' and custom materials" option. Then restart, and all the branded materials will be gone. Edit: with @Alain_D's screenshot, and my description, you should be able to figure it out 😉

Oops, sorry, the one I linked to is a type-c cable which will not plug in to the UM S5 board. I removed the link to prevent confusion.

Your local Ultimaker reseller will know for sure, but they are probably much more expensive than finding a "panel-mounted USB OTG cable" NB: I am actually not 100% sure it is a USB OTG cable (or what the exact difference is between a USB cable and a USB OTG cable) but all the micro-USB to USB-A cables that I have seen of this gender are USB OTG cables.

This is a bug. Please report the bug at https://github.com/ultimaker/cura/issues Cura 5.6 introduced the functionality to have simple math inside the {} patterns, and apparently that broke existing functionality to get a value for a specific extruder.

It is unnecessary to abuse the settings system for that. Instead, just hook into the outputdevicemanager writestarted signal like eg the postprocessing plugin does (or another place where you can access the "gcode_dict" attribute of the scene). Settings should be used for things that users can put a value in, which affect printing. def __init__(self): super().__init__() self._application = Application.getInstance() output_manager = self._application.getOutputDeviceManager() output_manager.writeStarted.connect(self._filterGcode) def _filterGcode(self, output_device): scene = self._application.getController().getScene() gcode_dict = getattr(scene, "gcode_dict", {}) if not gcode_dict: # this also checks for an empty dict Logger.log("w", "Scene has no gcode to process") return for plate_id in gcode_dict: gcode_list = gcode_dict[plate_id] if len(gcode_list) < 2: Logger.log("w", "Plate %s does not contain any layers", plate_id) continue ... calculate/get used materials, insert them into gcode_list[0] ... setattr(scene, "gcode_dict", gcode_dict)

Yes, because you cannot do block statements. Yes, and Cura specifically allows for that, and it is used throughout many printer definitions.

Note that that method was a specific answer to a specific issue that the installer did not work. It is in no way a solution to get Cura itself to start. What OS do you use? On Windows, only Windows 10 and Windows 11 are supported.

You may need to log out of your account in Cura to see all the plugins in the Marketplace inside Cura. Then you can install the plugin(s) you need, and optionally log back in again.

The easiest solution is to log out of your account in Cura, install the plugin, and (optionally, if you need it) log back in to your account in Cura.

It is good to have you back though, even if just for a little while.

Actually, you need to create a "fork" of the Cura Github repo, create a new branch on that fork, and then submit a pull request from that branch back into the "main" branch on the Ultimaker Cura repo. You cannot create a branch on the Ultimaker Cura repo directly. Also, just to get the version terminology correct: The version scheme is Major.Minor.Patch. This is called "semantic versioning". So the current version is major version 5, minor version 6, no bugfix release. New machines definitions are included in new minor versions of Cura, so the first update that could include a new machine definition is Cura 5.7.0.

I think the reason behind that extra level of folders is that the "top" folder is the name of the "package" and the subfolder with the same name is the name of the "plugin". Theoretically a package can contain multiple independent plugins. In most - if not all - cases, a package contains only a single plugin, and they both have the same name. AFAIK, it is not actually necessary to keep the folder structure, but I admit that I have not tested that recently.

Deleting cura.cfg as a blanket solution is potentially throwing out the baby with the bathwater. If it is not necessary, then don't do it.

It is NOT NECESSARY to delete the cura.cfg file if you disable all except one display! Removing that file will cause Cura to go through its initial setup wizard when you start Cura again.