ahoeben

Not as far as I know. The CuraEngine is what creates the gcode, and it does not have a pluggable architecture. Cura 15.x does not get developed anymore, so don't expect new changes to be backported.

Did you install the OctoPrint Connection plugin? It is available in the Marketplace in Cura 3.5 and up.

Loading Solidworks files depends on a plugin. That plugin needs to be updated for Cura 4.0. You can find it in the Marketplace, which is accessible through the button in the top right corner of the Cura window.

It looks like the model warped itself so much that it came free from the builtplate during printing. The head then sort of dragged it along while printing. One thing's for sure: your techer (or the person operating the printer) did not check if the print was off to a good start. The bed may not have been level, or the glass plate may be very dirty/oily. Hard to tell from just this one failed print.

Note that support blocker blocks are not simply subtracted from the support. The idea is that where they overlap a model, that part of the model does not get support. The issue here is that the support from higher up in the model extends all the way down to the buildplate, instead of stopping at the lower part of the model. This is a bug (which last I heard was "mostly fixed" in Cura 4.0).

The OctoPrint plugin that is available in the Marketplace can just be installed with Cura 4. There is no need to manually download files! Do not use the files linked in this post. Those are prerelease versions. The versions in the Marketplace should be used instead!

Quick tip: If instead of removing the folder named "4.0" you make the folder empty (so remove the files inside the folder, but leave the folder there), you will get a "clean" Cura 4.0 but leave your older Cura configurations in place for older versions of Cura to use.

Just installing the stable version over beta 2 should work.

I don’t understand your reply. How can Marketplace not be there? It is part of the application.

Once a release is in beta, no new features are allowed, to decrease the chances of new issues being introduced. A printer definition is seen as a new feature.

Use the version that is in the Marketplace.

Also, relevant XKCD: https://xkcd.com/1172/

What I mean is that you can add an Ender3 to Cura twice. Just name them differently. You can then easily switch between these two configured printers, and the settings/material selections you make on one printer don't affect the other printer.

The "contacting surfaces" as you name them are called "support interfaces" in Cura. In the advanced settings, you can set the "Support Extruder" to your main extruder, check the "Enable Support Interfaces" setting and then set the "Support Interface Extruder" to your secondary extruder.

Ha, I see what you did there with the blog post title...

There is no command line option to deal with these dialogs. Loading projects just isn't meant for this usecase. Is there a reason you can't just set up two printers in Cura, and switch to the appropriate one in each instance you launch? The option to remember your choice should work. If it doesn't that's a bug.

Perhaps we can help you if you tell us what two dialogs you get.

Note: first make sure you are comfortable editing files with “vi”. It is a text editor. Google it, fear it.

How about using a skirt instead of a brim, and using the skirt settings to make the skirt wider and the distance between the skirt and the model very small?

Note you can load any shape you want, and use the Mesh Type in per model settings for “masking”.

"Initial Layer Height" does not affect squish. The "Initial Layer Height" setting is meant as a workaround for not-quite-flat buildplates. If you lower the initial layer height, Cura will tell the printer to extrude less material so you effectively get the same amount of squish. It is recommended to keep the initial layer height higher than the normal layer height. The "Z Offset" setting will let you move the entire print closer to the buildplate with the same amount of material extruded, thus squishing the print into the buildplate.

This is simply untrue. Cura Connect is not Cura. Cura Connect is a print queueing system, and runs entirely on the Olimex board. Cura (the desktop application) can talk with Cura Connect to send printsa and show progress, but you can do much of the same from a browser. The Olimex board does more though, like managing materials and switching active cores.

Did you see there’s a plugin called Z Offset Setting in the Marketplace? It allows you to shift the entire print up or down a little, for this purpose. After installing the plugin (and restarting Cura), a new setting is added named Z Offset (use the Search on top of the custom settings to find it)

Yes, "Ultimaker 2" should be named "UltiGcode" in that list.

Move the core to the left slot before running the gcode.