ahoeben

Unless you want to write UFP files, you don’t need that plugin and you can ignore the error. I think a warning would be more appropriate there. I think the UFPWriter plugin has a dependency on a repository named libCharon

Did you clone the fdmmaterials repository into resources/materials?

Not with the current Search & Replace script. It could be implemented in a custom postprocessing script though.

@Stefania Dinea ColorFabb now does color on demand: https://learn.colorfabb.com/color-on-demand/

Aw, yes, that’s right... Doesn’t “./cura marvin.stl benchy.stl” work?

I think the commandline argument you are looking for is —single-instance. That should connect to an already running instance and hand over the file to that.

When you change materials, Cura will ask you if you want to keep/transfer the modifications you made, or start with a clean profile for that material. If you keep them, the temperature will (and should) stay at the altered value.

These prints aren’t made to be “close to reality”. Full white is often chosen as a (culturally defined) way to communicate that the materilisation is not finalised yet (a sign so to say for the client to ignore the material for now and focus feedback on structure and form)

Editing the plugin is trivial. Adding a multi-line textedit widget to the Cura sidebar is far less so. I have already outlined a way to edit configuration files to add start gcode to your quality profiles.

But since OP is having trouble checking out the right repositories, I don't think OP has succeeded in building Arcus and Savitar (or CuraEngine) on Windows yet. (I know I still haven't, after 2.5 years of Cura development on Windows)

You need all of Uranium, not just the UM folder. The UM folder should be in the PYTHONPATH when Cura is run. I also have a "bin" folder at the same level as Cura and Uranium that contains CuraEngine.exe, Arcus.pyd, Savitar.pyd, and a bunch of runtime dlls.

As a workaround, try using the cursor-keys to navigate those menus. Doesn't make it less of a bug, but it might let you use the menu items.

There's a possible fix, could you test it? https://github.com/Ultimaker/Cura/issues/3725#issuecomment-396181967

Could be a sideeffect of that textRenderer thing (native vs qt text rendering). @catohagen, could you check the Toolbox to see if there's an update for the backup plugin?

Since the UM3 has no user-accessible USB host/serial connection (only a USB slot meant for storage devices), that won’t work.

The camera not showing is a known issue (for some users?) that I have only just been able to reproduce and am trying to find a fix for: https://github.com/Ultimaker/Cura/issues/3725

You need to upgrade (or downgrade) your Intel GPU drivers, see https://github.com/ultimaker/cura/issues/2068 This is a known issue with a certain series of drivers of Intel HD Graphics gpus.

Go to Help -> Show configuration folder. Copy all the files there to the configuration folder on the other computer. Alternatively, use the “cloud backup” plugin in Cura 3.4 which is currently in beta.

Cura releasenotes... I will never understand how they are written.

This is “by design” in Cura. Look at the printhead, and you will see it is not symmetrical. The nozzle reaches further to the left then to the right.

I have no idea. Since the launch of the beta I have submitted an update that fixes a possible crash when there is no heated bed configured in OctoPrint, and which is more specific about the version of Cura it is compatible with. But that was well after the releasenotes were written, so I have no idea what they refer to.

AFAIK, in most cases Cura behaves just as you say: 0 is a value, not the absense of a value. If this is not that case, that is (in muy opinion) a bug.

I can't help you with Cura 15.04.x (because I don't have any experience developing for it), but I recently found out how to launch CuraEngine in gdb in connection with a running instance of Cura. * Start Cura with the command-line option --external-backend python3 cura_app.py --external-backend * In the output, look for a line like this: [MainThread] UM.Backend.Backend._createSocket [242]: Listening for backend connections on 49674 * Launch CuraEngine manually in gdb, connecting on that port: gdb --args CuraEngine connect 127.0.0.1:49674

This is going to be the least constructive reply ever, but each time I see this topic I think "I don't need to know about your leaky bottom".

This should be possible as follows: * go to Help -> Show configuration folder * close cura * In the configuration folder, go to "definition_changes" * in that folder, find the *_settings.inst.cfg for your printer, and open it in a text editor * add the following line to the [values] section: machine_nozzle_temp_enabled = False * save the file * restart Cura You should now no longer be able to set temperatures in Cura, and the gcode should also not have temperatures in it anymore.