ahoeben

No, it can't. Perhaps this could be added at some point, though it is tricky to be exact here; there's a buffer on printers, so the line that was just sent to the printer may take a while to actually be printed.

If you are using Cura 2.3, the elliptic buildplate functionality is not yet available. It will be added in Cura 2.4 which is currently in beta and should be released "any day now".

For the record: No, I am not having this issue. The combination works great for me.

Currently you cannot load a gcode file back into Cura 2.x. Loading, displaying and printing gcode files was recently contributed by Lulzbot, and will be part of Cura 2.5. You could try Cura 15.x ("the old Cura"), or a tool like pronterface to send gcode files to your printer (I'm guessing that's why you would want to load gcode files).

I've got 99 settings but the layer height aint one! Mixing layer heights is all but trivial. Say you have a mesh with a .1mm layer height, and a mesh with a .13mm layer height. This means that these layers almost never coincide in height. Currently the CuraEngine can just take a single cross section for everything that is printed at the same time at the different layer heights. Combine this with things like combing where the printhead must avoid layers that have already been printed, and features where touching objects get a bit of extra overlap if they touch, and it becomes complicated quite quickly. TLDR: It's complicated.

Have you read its description in Cura? Have you tried it? It does *exactly* what you describe.

You may want to try the older Cura 15.04 instead of Cura 2.x, since that version is what 101hero.com mention on their site. Cura 2.x was rewritten from scratch, and is not as compatible with 3rd party printers when it comes to USB printing.

The setting for this is called "Infill Layer Thickness" (in the "Infill" category).

There is no such thing for Cura 2.x currently.

Another trick is to put the whole tube into hot water to soften the filament but not the bowdentube. It is a bit more controllable than hot air.

Ga naar de "machine settings" en verander de GCode Flavor naar Reprap. Het idee van de UM2 (zonder plus) met UltiGCode is dat je op de machine bepaalt met welk materiaal je print. Cura weet daar dus niet van, en kan niet weten wat het soortelijk gewicht is van het materiaal dat je gaat gebruiken. Vandaar dat er geen gewicht wordt vermeld als je een UM2 met UltiGCode gebruikt. Voor de UM2+ is het idee van UltiGCode een beetje achter gelaten. Het blijkt namelijk dat je voor prints met verschillende materialen echt anders moet slicen voor het beste resultaat; meer dan je in de printer in kan stellen. Dus voor de UM2+ (en de UM3) is er in Cura weer een materiaal-selectie.

The feature was left unimplemented in 2.3. Unfortunately it was forgotten again in 2.4. I have implemented the feature and created a PR on github, but it remains unmerged. Show your support for the feature here: https://github.com/Ultimaker/Cura/pull/1243

@LePaul: Have you tried the plugin I linked to?

Cura 2.4 has a dialog asking for the number of copies. To keep Cura from reslicing when you don't want it, you could use this plugin: https://github.com/fieldOfView/PauseBackendPlugin

Because it is (1) not needed for Ultimaker printers, and (2) noone with a printer that needs it is able or willing to add it to the new Cura. I am willing to add it, but I don't have a printer that does not work with the current auto-detection. If someone wants to send me a printer, or even only a controller board to test with, I will do my best to make sure that it works with Cura.

This is not true. Cura 2.x communicates over USB to Ultimaker printers and some others just fine. There are issues connecting to some other printers, but unfortunately noone who is working on Cura has one of those printers and people who have those printers can't fix the issue.

There is currently no way to enter a string. The "textfield" widget is hardcoded to validate numbers. A "PostProcessing script" (what you call a plugin) is called when writing gcode files, after all slicing is done. It does not call the slicing engine by itself. The files you see in the "plugins" folder are much more than postprocessing scripts. Almost everything in Cura is implemented as a "plugin", from the tools (move, scale, mirror, rotate) to the connection with USB and the UM3, from the model display and layer view to the connection with CuraEngine. The PostProcessing of gcode itself is also handled by a plugin.

By "Create a machine profile", they mean a .def.json file like the ones in your Cura/resources/definitions folder. You cannot create those from inside Cura, you have to use a text-editor. Official machine definitions can define many, *many* (many!) more parameters than what you can set with the Machine Settings screen. The "Custom FDM Printer" route is meant for end-users of printers for which there is no official machine definition.

I printed the ultimate holder for the Olsson Ruby nozzle (printed in copperfill): 3d printer bling!

I think the recommendation is *warm* water, not hot water. If the temperature exceeds ~60 degrees, the PLA will start to soften, and the object can deform.

Same user directory. PSA: if you are worried about leaving your stable installation, make a backup of the configuration folder before opening Cura 2.4. You can find the configuration folder by opening Cura 2.3 and going to Help -> Show Configuration Folder.

Try the new Cura 2.4 beta: https://ultimaker.com/en/community/35485-cura-24-beta-is-here There's basic support for delta printers (elliptical build plate shape) so you no longer have to create unprintable areas yourself. There are probably still issues with this, let us know if it works for you.

No, this is not required for the camera stream to be available.

We suspect a policy on your Windows installation may prevent "signed" applications from launching "unsigned" applications. The main Cura application is signed in 2.3.1, the CuraEngine is not. I believe work is underway to have both Cura and CuraEngine signed for 2.4, which would solve this (if it is indeed your problem with 2.3.1).

I believe a better solution is being worked on for Cura 2.4