ahoeben

Printers generally don't read STL files. You need to feed them gcode files. Depends on the printer. Most of the time you need an "USB A to USB B" cable. You may need to install a driver on your computer. And even then, Cura may not be able to communicate with your printer. Edit: it looks like your have a CR 10, which actually uses a USB A to micro USB cable.

Increasing the flow for this is fighting a symptom, not solving the problem.

It looks like you installed the "Announcement plugin" that is not a plugin but was put in the Marketplace as a way to tell users that more plugins are coming: https://marketplace.ultimaker.com/app/cura/plugins/UltimakerPackages/Cura5Announcement It also looks like Cura 5 has an issue removing plugins. It will sort itself out with the final (or the next beta if there is a second beta), but you could remove the plugin manually by going to Help -> Show configuration folder, and removing the folder for this plugin in the "plugins" folder of the configuration folder.

Thanks, a fix for that has already been made, which will be part of the final release of Cura 5.0.

I think this has more to do with the type of model. Try enabling the "remove all holes" for this model in vase mode (but remember to turn it back off for other models).

Hurray, Mesh Tools and the Printer Settings plugins are the first two of my plugins that are available in the 5.0 plugin Marketplace.

That newest log file does not contain any new lines after 09:42. If you tried Cura 5.0, the log file for that is in a (slightly) different folder (with 5.0 in its path instead of 4.13).

Have you tried the Material Settings plugin from the Marketplace? Once installed, go to Extensions -> Material Settings -> Configure Material Settings. There you can select which settings will be available in the "Print Settings" tab on the Materials preferences pane. It looks like "Break temperature" is listed, though I have not tested if the value you enter ends up in the correct place in the XML file so it is accepted by the Material Station.

I would not call people I invite to my party "parasites", but if they start complaining I will call them "ungrateful". I do appreciate guests that (respectfully) give me tips on how I can make my cake even tastier (especially if they also bring the ingredients). But this party thing was just a metaphor to try to show you how you come across to some other people here, biting the hand that feeds you your free cake. And metaphors don't always work 100%. Off-metaphor and on-topic: Ultimaker has no interest in improving the USB Printing capability of Cura. If a third party (me, or you, or your printer manufacturer) improves the USB printing capability of Cura in a way that does not break things for other users of Cura, then Ultimaker will be glad to incorporate those changes into Cura for the benefit of other people still using USB printing.

On the Ultimaker Original board, you should be able to easily switch out two "stepper drivers" to check whether those are working (similar to how you checked the motor itself by putting it on another connector). The stepper drivers are the small PCB boards on the right, directly next to the terminals for the steppers: Note that the one for the extruder has a different orientation than the ones for the axes. This is correct; don't connect them in a different orientation.

It looks like the problem is caused by the non-ascii characters in your username on your computer. A third-party component of Cura is having troubles with that. I think that is being fixed in Cura 5 (you could try the beta), but I am not 100% sure. For now you could try creating a new user on your computer with a username consisting of just ASCII characters.

@Lupus52, it is a bit like Ultimaker is having a party, and everyone is invited. Your printer manufacturer is also giving a party, but they did not want to spend money on cake. So they tell their guests to head on over to Ultimaker because Ultimaker are handing out cake for free. You come to the Ultimaker party and are offered cake, but complain that it is not the flavor you wanted.

I think you posted to the wrong thread. This thread is about plugins, your post isn't. Having said that, make sure that your "Support Wall Line Count" is not 0.

Sing with me. "TOOOOMorow, tomorrow, I love you, tomorrow, you're always a day away"

Chitubox is just one possible (but common) cause of a crash. There are other possible causes. It is impossible to diagnose this without having a look at your logs. Go to Help -> Show configuration folder, and locate the file named "cura.log" (it may show as just "cura" if you have your Explorer configured to hide extensions for common filetypes. Upload that file somewhere (google drive, dropbox, etc) and post a publicly viewable link to it here.

Or better yet, check out this post (which also includes instructions):

Could you please be more specific than that? There's a known issue that Multiply Selected will do nothing unless you change the number. A fix for that is ready for the release version of Cura 5.0

It is always hard to know for sure from just a single screenshot, but the 0 minutes 0 material used thing has nothing to do with that the model "floats" above the buildplate. From the looks of it the model is hollow and has very thin walls, probably thinner than the nozzle diameter. Parts that are thinner than the nozzle diameter will not print in Cura 4.x. Try increasing the Horizontal Expansion, or try slicing with the Cura 5 beta which changes how thin walls are handled.

Like so? https://support.ultimaker.com/hc/en-us/articles/360011889579 On the downloads page (https://ultimaker.com/software/ultimaker-cura), click on System Requirements and then follow the link about supported operating system versions.

This is a fairly simple question that does not have a very simple answer. Here's a start: https://github.com/Ultimaker/CuraEngine/blob/5.0/src/FffPolygonGenerator.h

OpenGL 2.0 is a standard that was released 17.5 years ago. It is highly unlikely that you are using a computer with a GPU that is incapable of OpenGL 2.0. It is much more likely that the driver for your GPU is not correctly installed. It is also worth noting that running Cura via an "RDP" connection can lead to the same error message. It is something that is not supported by Ultimaker, but perhaps there is a workaround. Tell us more about your computer.

I have added some more prereleases. The last of my official plugins that still needs an update is the Material Settings plugin. I hope I'll have time to work on that tomorrow.

It would be really helpful if you could let us know what installation directory you used previously (which did not work) and what you changed it to (so it now works correctly). That way we might be able to fix issues for others who have the same issue you had...

See this post:

It should not be. I think that is a Cura bug, but I'll have to look in to that.