ahoeben

That is the idea. At least the person who wrote/updated the definition for the printer you use thought it was an improvement. Ultimaker does not test this, neither do I (I don't have a monoprice mini).

The "another issue" is caused by the coasting option. Coasting is when the printer stops extruding before the end of a layer. When printed, there will not be holes because there is still some remaining pressure so material continues to ooze out while finishing the layer. At least, that's the idea. I would guess it makes more sense on a bowden-tube printer than a direct extruder printer.

That would suggest that Cura 4.0 never ran successfully on your computer, which means that you do not have the same problem as Swissengineer.

I think @TheSinkingMan is trying to keep the layer height to a multiple of the effective height per step of the Z stepper motor, which could improve quality due to aliasing issues with other layer heights.

Press the windows key, and start typing the literal text (including %): %APPDATA%\cura\4.0 Then press enter. This should open a new explorer window.

I think as long as you make sure Cura is on the main monitor when you close it, it should be ok.

For the first issue, check out the “Extruder 1” tab in the profile dialog.

See Help -> Show configuration folder. They are in one of those folders.

Go to %APPDATA%/cura/4.0 and remove cura.cfg

No, sorry, I don't. I know the camera can do 1600x1200 because when the UM3 was being developed I working for Ultimaker. Back then I was involved in getting the stream visible in Cura. But I know very little about the firmware (or the exact hardware, actually). Edit: I would not be terribly surprised if the camera were at least very similar to this one (since the linux board it interfaces with is an Olimex A20): https://www.olimex.com/Products/Components/Camera/CAM-GT2005/

How many screens do you have? There’s a known issue on some combinations of gpus and multiple monitors.

This is often done using a plugin in OctoPrint named OctoLapse.

You need to do libArcus before CuraEngine, because CuraEngine requires libArcus (right?).

Couldn't you do that with a postprocessing script though? Duplicate each layer, adjust the extrusion.

It depends what you want to change. If it is all frontend stuff, you might be able to just edit python files in the released version.

I’ll just quote myself, from a couple of replies above this: Also note:

Liked for the thread title

Bugs happen in Cura. I don't think you really want automatic updates. Sometimes you want to hold back on an update. Having said that, you can extract the files from the Windows installer with just about any archiving application (eg 7zip), and run Cura.exe from there without installing it to Program Files. That should make it possible to use a newer version without bothering asking your IT department for support.

Note that a new version of the plugin, which singles out Ultimaker 3 and S5 printers, is now available in the Marketplace. This fixes this issue, specifically for these printers.

If @ahoeben did not do this (to *some* of his plugins), every user upgrading from Cura 4.0 to Cura 4.1 with the OctoPrint Connection plugin installed would have been greeted with a crash dialog with the option to kill all their settings, because once again this SDK update was messed up like it has been many times in the past. Please don't suggest that I do this "out of a personal decision". Time and time again this has proven to be a necessity.

A prerelease version of the OctoPrint Plugin for Cura 4.1 can be dowloaded here: http://files.fieldofview.com/cura/OctoPrintPlugin-v6.1.0-2019-05-16T10_29_36Z.curapackage Please drop the downloaded file into a running Cura application window, and restart Cura. Unless issues are reported with this version of the plugin, it should be available as an update on the Marketplace soon.

Between the Settings and the Preferences menu. In the same menubar as File, Edit and View.

I think this would have been better suited at the OctoPrint forum (as I said in my email). This needs to be solved at the OctoPrint end first. There is currently no way to link a gcode file to a user in OctoPrint, or to add other metadata to the gcode file. If that were possible, the OctoPrint Connection plugin would be able to send this data. Currently there is nothing on the receiving end (OctoPrint) that would register this additional data, so there is no use sending it.

The gpu in the first laptop does not support the required functionality for the normal layerview, so it falls back to the compatibility mode. The gpu in the second laptop should support the required functionality. There are two possibilities why it does not work: * You may have changed the preference on the General pane of the preference to force the compatibility mode * The driver you have installed on the laptop may disable OpenGL 4.1

I can tell you how the barbarian plugin works, but other plugins work differently. Some plugins (like the Barbarian plugin) add an entry in the Extensions menu. The Barbarian plugin adds a menu item "Extensions -> Barbarian plugin -> Convert to metric". You select an object that was imported in inches and use that menu option to scale it up. Note that this thread is specifically about the list of plugins listed in the opening post, for the beta of Cura 4.0. Your post would have been more appropriate as its own thread.