ahoeben

Please post your Cura.log (see Help -> Show configuration folder).

Can you post a link to the model, so we can try with your exact model?

The material station is not meant to switch materials mid-print to create multimaterial prints. There isno way to set this up in Cura

Are you absolutely sure about that? This is normally only used for delta-style printers.

Rule #1: see rule #4

The Geforce 9500, a 12 year old GPU, supports up to OpenGL 3.3. For its simulation view, Cura requires OpenGL 4.1 or newer.

In all probability, the GPU you use does not support the necessary features for the advanced layer view, so Cura falls back to using compatibility mode which does not support the print simulation.

There are many settings in Cura that can not be made visible, but they can be specified in a printer definition. These include things like the maximum speeds and accelerations your printer can handle. The "Printer Settings" plugin makes these settings visible in Cura, but it is much better to push Monoprice to update their printer definitions and have them included in Ultimaker Cura.

The red here visualises overhang that would normally need support. But because the bottom layer touches the buildplate, no support is needed.

Yes there is. cura.CuraApplication subclasses Um.Application. To oversimplify: CuraApplication has all of the functionality of Application and more.

With some printers (eg with a bowden tube) and materials (eg more flexible), when extruding material there will be a built-up pressure, which means that if the printer stops extruding there will still be residual pressure causing material to be extruded from the nozzle. Coasting tries to “use up” that residual pressure.

Yes. You upload a zip containing the source of your plugin, and before you submit it for approval, you can download a curapackage.

That sounds oddly racist. But I guess that's not how you meant it 😉 (to be perfectly clear: that was meant as a joke)

Cool. Don't give too much credit to lokster; his plugin is 98% my work on the Support Blocker. What you are doing is already much more interesting.

See my pull request here: https://github.com/5axes/CustomSupportCylinder/pull/1

I think you are talking about what is commonly referred to as "elephant's foot". See the "Initial Layer Horizontal Expansion" setting: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/shell/xy_offset_layer_0.md

This does not seem to have anything to do with your (Cura) configuration. Cura crashes very early in the start sequence while trying to set up "sentry", which is ironically a tool for reporting crashes. I can probably fix the problem for you, but the method is an ugly hack, and it will probably cause the module to make and restore backups not work. Go to C:\Program Files\Ultimaker Cura 4.6\ and copy the file python35.zip to your desktop. Open the zipfile, and remove the folder named "sentry_sdk" from it. Move the zipfile back to its original place.

Thanks for testing it.

If you put the whole thing up on github, I can help you later this week.

Cura has many included plugins that you could use as an example. The translate tool has numeric input fields: https://github.com/Ultimaker/Uranium/tree/master/plugins/Tools/TranslateTool

Why would you want this to be a setting though? Couldn't it just be a numeric input field in the tool panel?

This leads me to believe you have added an Ultimaker S5 to Cura when it asked you what printer you have. I don't blame you; in the dialog, where you selected a "non-networked printer", only Ultimaker printers seem to be listed. But you can scroll that list to reveal more printers.

You can scroll the list. There is a scrollbar, but it is of the type that hides itself when it is not used.

The "Wait for user input" thing happens when there is a buffer overrun in Marlin. Cura somehow sends gcode commands (such as eg temperature update requests) while the printer has not yet processed previous commands.

We can say more if you can tell us what type of connection Cura tries to make to other devices in your network.