ahoeben

Sorry, I forgot the “other” category was decommissioned in 4.2

The "Mark2 for Ultimaker2" printer can be found in the "Other" catagory.

The red is intended to show areas that need support. The fact that the sphere shows red on top means that the normals of that part of the mesh are reversed.

For Ultimaker printers, the estimations that Cura makes are fairly accurate in my experience. For other printers, Cura may be missing information about how fast these printers are configured to move. That makes accurately predicting print-times impossible.

Ok, if the web interface won't work, then neither will the OctoPrint Connection plugin in Cura.

Thanks. I have reproduced the orange triangle, and will see how to make it behave. The orange triangle is supposed to show when there are no quality profiles for the chosen combination of material and nozzle size. In this case there clearly are profiles, so the warning should not show.

* In Cura: File -> Save... * Upload the resulting file somewhere (eg dropbox, google drive, one drive, etc) * Post a link here

About that orange triangle, that's a feature of the Sidebar GUI plugin that seems to be misbehaving. Could you post a link to a Cura project file?

In Preview, change the View type to X-Ray. I think you will see parts of the geoemtry highlighted in red. This means there is "internal geometry". I think you did not properly "boolean"/"union" the tabs to the housing. This throws off the slicer.

How about if you manually upload and print the gcode file via the browser interface? I would like to know if it is my plugin, or OctoPrint itself.

Unfortunately the reality is probably more complicated than a fixed percentage. Try printing a 40x40x10 block, and you'll likely get a different percentage. Print your 20x20x20 mm block at a different speed, and the percentage also likely changes (though more subtly). The difference is probably mostly due to what is called "die swell". The material that gets extruded from the nozzle does not have the exact same diameter as the nozzle; due to pressure in the print head and in the bowden tube, the material expands outwards (horizontally) as soon as it leaves the nozzle. This expansion isn't constant either; it depends on the pressure and the pressure depends on print speed, and more parameters. In most cases, you can use the "Horizontal Expansion" setting to get closer to the original measurements, but getting them exact is the holy grail of 3d printing.

Cura stores a configuration per version, so you can always go back to a previous version if a new version doesn't work for you. When there is no configuration folder for the version you are running (eg when you run Cura for the first time), Cura will see if there is an older configuration that it can copy over and upgrade so you don;t have to reconfigure everything. I think in your case it picked up a configuration from an older version that you did modify (you added a Creality CR10 definition). That old configuration points to a printer definition that does not exist in the new Cura. This causes an error. Removing the upgraded configuration will only result in having the same old configuration with the reference to the missing definition being copied over and upgraded again. By removing the contents of the folder, but leaving the empty folder in place, you trick Cura into believing there is a configuration for this version of Cura in place (there's just nothing configured). So this is the way to start fresh without copying an older configuration.

Glad you are laughing, but I'm not an Ultimaker employee, so I don't get those logs. Neither do most people on this forum. Did you modify the Cura 4.2.1 files in any way (eg to install the Creawsome mod)? Or have you done so in the past? Creawsome mod is now integrated into Cura. I'm guessing you have tried the "Backup and reset configuration" button and restarted Cura? Something to try is to press the "Open configuration folder" button. Close Cura, and then remove all the files from the configuration folder, but leave the empty folder in place. Then restart Cura.

I can only tell what we’re missing: the contents of the detailed crash report. Without that we can only guess.

Your question starts out very reasonable, but I wonder what you wanted to achieve by adding the "(better)" there. It makes me want to answer with "you may want to get a different (better) printer". Cura supports printing over USB. Ultimaker does not offer support for it though. It may work, it may not. If it doesn't for your printer, Ultimaker is not going to fix it for you. Perhaps you can ask your printer manufacturer to contribute a fix. My personal advice would be to get a Raspberry Pi (model 3 or 3+) and install OctoPrint on it. Then you can use the OctoPrint Connection plugin to send the gcode to your printer, and your Mac will not have to stay connected to the printer during the print.