ahoeben

You seem to have a snapshot of the curaengine source that does not do the conditional include that I linked to. Pull in the latest version, and DON'T build tests. I think that is the default.

See https://github.com/Ultimaker/CuraEngine/blob/27cbc13cab69c24e96f7e293985893f08410695d/src/MergeInfillLines.h#L7 The file is only included if the BUILD_TESTS compiler flag is set. I don't know where you are getting protobuf_BUILD_TESTS from.

I am fairly sure that gTest (and gMock) refer to the google testing framework: https://github.com/google/googletest The header file that is failing specifically only includes the gtest_prod.h file if you BUILD_TESTS, so your initial guess is correct. This is about that optional test.

The problem seems to be that there's a fairly big darker grey area around the edge of the buildplate, and the model does not fit inside that. This darker grey area is reserved for printing a brim or skirt. If you make your brim smaller, or your skirt closer to the model, or turn off buildplate adhesion alltogether, the model should fit just fine.

There is a lot missing in your report, making it unnecessarily hard to help you. It would help if you included a link to download a model. It would help if you said *what* slicing error you get. It would help if you added a screenshot so we could see the model hashed in two colors. It would help if you said what version of Cura that came with your printer. As is, all we can do is guess. I'm just guessing that the model may load in such an orientation that it does not fit the build volume. Try making it smaller (using the scale tool), and/or moving it around so it does fit in the build volume..

I'm working on a new plugin, lets the user add settings to the Print Settings tab for materials on the Materials pane of the preferences. At its simplest, it adds the "Flow" parameter to the list of print settings for materials. The plugin also adds Extensions -> Material Settings -> Configure Material Settings. This will open a dialog that lets you configure what settings will be available, so you can add arbitrary settings such as Z Offset and Linear Advance Factor (both requiring an additional plugin already available in the Marketplace). It may not yet work with all settings, let me know. Note that a value set in the sidebar or in a profile still overrides what is set in the material. This plugin does not intend to change that. A testing version of the plugin can be downloaded here: For Cura 4.0 and 4.1: http://files.fieldofview.com/cura/MaterialSettingsPlugin-v6.0.0-2019-06-14T14_49_58Z.curapackage For Cura 3.5 and 3.6 (untested): http://files.fieldofview.com/cura/MaterialSettingsPlugin-v5.0.0-2019-06-14T14_49_58Z.curapackage After downloading, just drop the file into a running Cura window, and restart Cura when requested.

In answer to your original question: this is a different bug, and should be reported.

Without a log, there's no way of telling. Help -> Show configuration folder. Locate cura.log, upload it somewhere and post a link.

No, there is not.

Use T{initial_extruder_nr} instead of the final T0 Cura will fill in the extruder number of the first used extruder for the {initial_extruder_nr} part.

I have only had one other report of non-responsive fields sofar, but that seems to have resolved itself. Perhaps the two are related? https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues/2 If it is something I can't replicate myself, it will be very hard to fix. If you could come up with a way to reproduce it ("start Cura, click here, then do that, now the fields are locked"), that would be great.

I would guesstimate that Cura 4.2 will be released around one and a half month from now, barring any unforeseen blocking issues.

You can't. You can install a plugin that will let you scale a loaded model by 25.4 (from inches to mm), but there is no way to have Cura work in mm (nor any other unit of length other than mm).

The updated plugin (4.0.1) is now published in the Marketplace for both Cura 4.0 and Cura 4.1. When Cura 4.2 is released, I will have to make a new version.

Hmm. You covered the tools with the settings. So you use either the tools or the settings? And to show the settings after you have hidden them, you have to click in the top right to have the settings appear on the left. On top of that, you have to shift the viewport (shift drag) every time you launch Cura so the settings panel does not cover the viewport as much. If that all works for you, that's great for you. But I don't think that's optimal. Neither is my solution with the SidebarGUI plugin, but I feel it still gets closer than yours.

Sorry, I forgot to include a changed file. If you already downloaded the file in my previous post, please download the same file again. This time I actually tested it myself...

The printhead in the UM3 is much heavier than that of the UM2+. To maintain good printing quality, settings that affect the speed the head achieves are different between the two, eg the maximum accelleration. Simply put, the UM2+ is a faster printer than the UM3.

“Print as Support” seems to be broken in Cura 4.1. Not your fault (for once 🙂 )

A test-version that should work with both Cura 4.0 and Cura 4.1 is available here: http://files.fieldofview.com/cura/SidebarGUIPlugin-v6.0.0-2019-06-11T21_09_03Z.curapackage Download the file, and drop it into a running Cura application window. Then restart Cura. If this version works, it should be available from the Marketplace as an update soon.

There are two "modes" of specifying coordinates: relative or absolute. You describe absolute coordinates. In relative coordinates each time you use `G0 X1`, the head will move 1 mm. You can change between absolute and relative modes with the G90 and G91 commands respectively. http://marlinfw.org/docs/gcode/G000-G001.html http://marlinfw.org/docs/gcode/G090.html http://marlinfw.org/docs/gcode/G091.html

Putty should work. I am not entirely certain if the checksum that is normally added to every line is mandatory. In that case using Putty would require some math. If you just want to move the head around, that should work without any initialisation. If you want to extrude material, you will first have to heat up the nozzle (the firmware prevents cold extrusions)

At the heart of the UM2 is the same chip as an Arduino Mega. You should be able to talk to open its serial port (using PySerial) and send any gcode to it line by line. The default Baud rate is 250000.

The UM3 is the same type but newer than the UM2+. I don’t think Ultimaker will release a new single extrusion printer any time soon.

I don’t think Ultimaker will divulge this information before they are ready to do so, and the rest of us just don’t know.

Did you press the “Slice” button? Automatic slicing can be turned on in the General preferences, but is turned off by default.