ahoeben

No, there is no setting for this. It would be fairly trivial (for someone who knows how to create plugins) to make a plugin that strips all comments before saving, but quite frankly I am starting to become a bit weary of writing plugins that I will never use myself and only benefit a handful of people. So, try to convince me it is worth my effort.

It is now called Marketplace. It will probably have another name in a version or two...

Cura has a setting called Material Flow, which does exactly the same as an extrusion multiplier in the slicer.

Unfortunately, executing a postprocessing script adds... a comment to the gcode file to indicate that it has been postprocessed

The red on top (instead of on the bottom) in solid view means that the normals of your model are reversed. It should by itself not influence slicing (because CuraEngine does not use the normals). If you install the Mesh Tools plugin from the Marketplace, it will add a function that will let you fix the normals. It will also tell you when there's a problem with your mesh.

See https://github.com/Ultimaker/Cura/issues/4583 It does not look like it has been fixed yet.

I think what op is seeing is a regression in Cura 3.6 that has been reported before; supports extending all the way to the buildplate instead of stopping on the first upward facing mesh it encounters.

Have you tried the Z Offset plugin?

Er is een hele handige website voor het uploaden van videos. Ik weet niet of je hem al kent, hij heet Youtube. 😉 Maar dropbox, google drive, wetransfer, en allemaal van dat soort services om bestanden te delen werken ook.

I don't quite get the request. You can use this in your start gcode: M900 K{material_linear_advance_factor} W{line_width} H{layer_height} D{material_diameter} Type the actual text, with the curly brackets, and the values will be filled in.

Kan je er niet een videootje van maken? Want nu is het de geavanceerde versie van Het Geluid van Q-music, waarbij je niet het geluid krijgt te horen maar een omschrijving.

Hard to tell without further information about your set-up. What OS (version), what GPU, how much RAM, harddisk or SSD etc. There are reports of Cura being unreasonably slow on some OS X systems, but sofar this has not yet been reproduced at UM making this hard to fix.

Have you read the thread linked above? Hint: Materials pane of the preferences, or install the Printer Settings plugin from the marketplace.

In the current version of the plugin, this line is automatically added if it is not in the start g-code. I don't know if the second line is required or not. If it is, it does seem that this would be an issue with adaptive layer height. I admit I have never used to plugin beyond testing (or adaptive layer height for that matter). I think the plugin could also be improved for multiple extrusion; currently there is one "global" linear advance constant, but since its value is material dependent I would say that it should be possible to set this per extruder, and the M900 lines should actually (also) be in the extruder start gcode. PS: in case you had not put 1 and 1 together, I'm the author of the Linear Advance Setting plugin.

The plugin adds a setting to the sidebar, which can be added to profiles and such. Also you don’t have to go into Machine Settings to change it.

You don't give us much to work with. What printer do you use? Can you attach a project (File -> Save...)?

UM.Backend uses subprocess.Popen(): https://github.com/Ultimaker/Uranium/blob/3.6/UM/Backend/Backend.py#L134

See LocalFileOutputDevice.requestWrite() You can access the LocalFileOutputDevice using the OutputDeviceManager (OutputDeviceManager.getOutputDevice("local_file") You can access the OutputDeviceManager from the CuraApplication class (CuraApplication.getInstance().getOutputDeviceManager() So, in short: CuraApplication.getInstance().getOutputDeviceManager().getOutputDevice("local_file").requestWrite()

That would make it "0 things missing from Cura 3.6", which I know isn't true 😉

See the setting "Horizontal Expansion" in the "Shell" category. Setting that to -0.2 should help get you closer to the intended dimensions.

That's what the Z Offset plugin is supposed to do. It makes it so that all the subsequent layers are also offset. Someone from the UM S5 firmware team is going to have to chime in why G92 does not work as expected on an S5.

Have you turned on the option to show travels in the layer view legend?

Because of the bed clips, you can have a model that is 20 cm wide (but not as deep) or 20 cm deep (but not as wide). Also if you print with a skirt or brim, that needs space on the buildplate too.

The Toolbox changed name to Marketplace. Go to the Marketplace, see the Installed tab and find the USB Printing plugin. Disable it and restart.

I'm the creator of the Z Offset plugin. I'll admit I have never tested the plugin with an S5 (or an UM3 for that matter). Could you try saving the gcode to a file, and inspect the first move on the first layer?