ahoeben

If you are using the Cura 5 beta, read this post: For other recent versions of Cura, the plugin is available in the Marketplace.

Please stop screaming, and allow people some time to respond to your post.

what version of Cura blablabla what OS blablabla logs blabla. I understand that you are getting frustrated, but please understand that leaving out details will not result in getting you help. If you are using the Cura 5.0 beta, have you tried if the regular version of Cura works better for you? Beta software may have bugs; that's the whole reason why beta releases are done, so the bugs can be identified and fixed.

See this post, which has a link to a prerelease version of this plugin too:

There's a test build that seems to fix this issue here: https://github.com/Ultimaker/Cura/issues/11896#issuecomment-1114661108

@squodeler, sorry I missed your question a couple of months ago. It is only with the latest release that I started offering releases with .curapackages via github. What you could have done in the mean time (if I had responded in time) is check out the files in the "plugins" subfolder in the configuration folder on the computer that has the plugin installed, and transfer the files from there to the same folder on your non-connected computer. To find the configuration folder, see Help -> Show configuration folder...

Have you tried changing the Slicing Tolerance setting?

If you read further in the post, you will find that this is a bug and it has been fixed for the final release of Cura 5.0.

If you dislike the unused import, you could use the Cura version instead: cura_version = Version(Application.getInstance().getVersion()) tool_panel_path = "resources/qml/MeasureTool.qml" if cura_version < Version("5.0.0") and cura_version.getMajor() > 0: tool_panel_path = "resources/qml_qt5/MeasureTool.qml" But then you need to import UM.Version and UM.Application. Choose your poison. (good to see that you have decided to update your plugins afterall)

A prerelease of the OctoPrint Connection plugin can be found here:

You can add anything you want to the start of the gcode in the Machine Settings (see the Printers pane of the preferences) This page has a list of all the parameters you can include in the start gcode snippet: http://files.fieldofview.com/cura/Replacement_Patterns.html

Are you using Windows 7? The last version of Cura that officially supports Windows 7 is Cura version 4.10.

Then the result you get is exactly what you need; the extruded material will expand by "foaming" a bit, thus filling up the gap between the extruded walls. Also see how your brim looks (in both versions). typo Another thing I got incorrectly is that I thought the 45% flow was set in the Artillery definition, whereas it is set in the profile for LW-PLA. My bad.

This is because the artillery printer definition has the flow set to 41% (50% for your first layer). I don't know why they would do that.

Unfortunately, there is not. The "simplest" way I can think of to achieve this is with a custom postprocessing script.

@milcent, with reports like this project files are indispensable. Please use File -> Save project... to save a project and post a link to it here.

It looks like this is an extremely thin model. Cura 4.13 will not create toolpaths for things that are thinner than twice the line width. You can try the Cura 5 beta, which handles thin walls in a superior way, you can try lowering your line width, or you can use the "horizontal expansion" setting to make the model thicker.

It hasn't That sort of thing is what I was referring to as being fairly easy to patch.

That one is the most work 😉 First you have to "unpack" the AppImage: ./Ultimaker-Cura-5.0.0-beta+1-linux.AppImage --appimage-extract Then you can make the changes to the file(s) you want to change. After changing them, you run Cura with the following command: squashfs-root/AppRun

Either by trying, or by asking specific questions. The interface shows all the placeholders it supports.

The first two screenshots look like you may be using a dark-gray material. Have you tried selecting a different color material? For the preview tab, it looks like you are in "compatibility mode". Either the "Force layer view in compatibility mode" in the General preferences in Cura got checked, or your GPU driver is denying Cura an OpenGL 4.1 context.

There are not. It is fairly easy to "patch" your local install though. What OS do you use?

The plugin has changed name to just "Printjob naming". See Extensions -> Custom Printjob Naming -> Set name options

Are you using Cura 5? In that case, see this post, which contains a prerelease of this plugin:

Most people find out that you can easily "lie" that you included a log file and not include one. Other people find the reference to the dxdiag log in the "Logging issues" section of the readme here: https://github.com/Ultimaker/Cura/#logging-issues The dxdiag log would actually be very helpful to diagnose your issue, because it will show what driver(-version) is installed on your computer. The HD Graphics 3000 GPU should suffice for running Cura, albeit in "compatibility mode" (ie: with some limitations, mainly in the Preview tab). It is however not someting that gets tested regularly AFAIK, so your feedback (and logs!) are welcome.