ahoeben

PS: you are more than welcome here. No need to apologise (for your printer or your question)

The minimum value for the Z-Offset is the negative of the Initial Layer Height. If the Initial Layer Height is 0.3mm, you should be able to enter -0.3 as the Z Offset. Specifying a value lower than (- Initial Layer Height) would result in a negative Z value in the gcode. The firmware would - at best - ignore the negative value, or give you an error. The firmware assumes that Z=0 means that the nozzle touches the buildplate. A negative Z would mean that the nozzle is below the top surface of the buildplate (ie: the nozzle pushes through the buildplate). Needless to say, the nozzle actually pushing through the buildplate would be "less than desirable". PS: fieldOfView is known as @ahoeben on this forum.

You might be interested in Conical Support: https://ultimaker.com/en/resources/20426-experimental

The idea is that "Make overhang printable" changes your model so there is no more unprintable overhang. It is not always going to give usable results, depending on the model and the use of the model (even if it is printable).

I knew I had seen it before in an issue: https://github.com/Ultimaker/Cura/issues/2452

It is a font (configuration) issue. The gcode boxes (try to) use the system-defined non-proportional font.

Even on Linux? I thought the PITA was mainly Windows 32 bit.

Plugins need to be updated for Cura 4. There's an issue with Cura 4 beta 1 that makes it impossible to update the plugin without making it unavailable for the current version of Cura (3.6). This will be fixed in Cura 4 beta 2. Most plugins will become available for Cura 4 after beta 2 is released.

No, this option does not make support. In your screenshot you can see that the cube is now "supported" by a piece of wall that lies outside the original geometry (lower left).

What happens if you turn off supports?

@ghostkeeper, wasn’t fhete a similar report with an AMD GPU on github?

I think the complaint is that if you close the message box (instead of going to "More info" and selecting "I don't want to send these data", Cura will pop up the same question again on the next start. Closing the message box is not answering the question.

What version of Cura do you use? What are the specs of your computer (CPU, GPU, memory)?

Cura looks at your start gcode, and does not see you heat up your extruder(s). It then figures that extruding cold probably isn't a good idea and adds the preheating sequence before the start gcode. Try adding the following line to your start gcode (anywhere): ;M104 {material_print_temperature} Add the line EXACTLY like this; with the curly braces and the exact text (don't substitute it with the number). Note that I have put a ; before it, so it will not actually be executed. But it is enough to convince Cura you are doing something to heat up your nozzle, so it will not do it for you.

What browser is that? It does not display the page properly. I think the Solidworks integration thing is catching the click. You can try this link directly: https://ultimaker.com/en/products/ultimaker-cura-software/download-request/209

Or try the Cura 4 beta, which supposedly fixes the issue.

Yes, you can make any model a support blocker using the mesh type in per model settings.

It does not

I am not an expert on this type of thing, but that connection carries a lot of current. It is the type of connection that can cause fires when it has a bit of resistance and/or partially disconnects during use. It is something you will want to be careful with.

It helps if you are a client that's about to buy 100 Ultimaker printers 😉 More seriously though, it has been an issue for a long time, and it never got enough traction to get it fixed unfortunately. I don't know who's the "product owner" of Cura these days. The product owner has a large say in what gets fixed and what will remain open for the foreseeable future because there is too much to do. You could chime in here: https://github.com/Ultimaker/Cura/issues/4427 As another, more permanent workaround, it should be possible to write a plugin that forces Cura to always start on the primary screen. Thing is I already have 10 plugins to maintain and update between versions...

Yes, by using the correct replacement patterns in your start gcode. If Cura sees the actual use of the replacement pattern {material_print_temperature} in your start gcode, it will not add its own extruder preheating. Same with {material_bed_temperature} for the bed. And I mean that actual text, including the curly braces.

Not as far as I know.

Remember that these are beta builds of the plugins; please install the version from Marketplace instead once it is available (when Cura 4 beta 2 launches)

Sorry, I forgot about that. https://community.ultimaker.com/topic/25967-plugins-for-cura-40-beta/

Could you try with Cura 4 beta 1? I just tried with what will become Cura 4 beta 2, and at least there it seems to be fixed.