ahoeben

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.

That's because your layerview is in compatibility mode. This happens because of two reasons; You either selected this in preferences or your graphics card doesn't support opengl 4.1. Note that in the first screenshot, the Sidebar GUI plugin is used to rearrange the UI. This made the vertical slider move to the left of the settings.

Not before a Cura 4.1 beta is available.

The article you link to is for multi-extrusion printers. On single extruder printers like yours, you have to "manually" insert material change gcode with postprocessing scripts. The article does include how to "merge" your models after importing. I'm not familiar enough with Blender or Fusion 360 to tell you how to export multiple objects with the same origin.

It has been reported by another user here: https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues/2 I have yet to look in to the issue. Does it also happen when you don't switch to the monitor tab? How do you connect to the printer? USB, OctoPrint, Cura Connect?

No, it isn't.

Sounds like it has the wrong firmware. The Ultimaker 2+ has an additional gear in the extruder, which means that the extruder needs to be inversed. If you have an Ultimaker 2+ (or upgraded Ultimaker 2) with Ultimaker 2 firmware, or vice versa (an Ultimaker 2 with Ultimaker 2+ firmware), the extrusion will be inversed.

You can open a gcode file to inspect it, but you can not change parameters and reslice it. This is because the original information of the 3d models is missing in the gcode files.

That’s pretty much what my therapist told me.

The gcode you posted is properly postprocessed to include the M117 gcode commands mentioned by @tinkergnome. If when printing this gcode file your printer display does not show "Layer # layer: 1" on the first layer (and so on), then this functionality is apparently not supported by the firmware of your printer. There is some evidence to support the latter theory: https://www.google.com/search?q=wanhao+duplicator+i3+plus+m117

No, I meant a whole sliced gcode file. Just slice something small. I am telling you, it isn't.

Ok, then it should work. Can you post a small gcode file somewhere for me to have a look at?

Ah, it seems that postprocessing scripts don't work when printing over USB in Cura 4.0 https://github.com/Ultimaker/Cura/issues/5589#issuecomment-481822914 Are you printing over USB, or saving files to an SD card?

Have you tried leaving it empty?

If the software that comes with the printer is so great then why do you want to use Cura?

Please check if this guide will allow you to run Cura with either the Intel or the NVIDIA gpu: https://www.addictivetips.com/windows-tips/force-app-to-use-dedicated-gpu-windows/

Can you force Cura to run on the Intel or on the nVidia GPU? Does the same problem occur with both GPUs?

Post processing script state is now stored between sessions. Has been so since Cura 3.3

What if you remove the cura.cfg altogether?

It is not a plugin causing this, it is a conflict between your GPU(-drivers) and Cura. I think you can get Cura running again by pressing (and releasing) the windows key, typing (exactly, without the quotes) "%APPDATA%\Cura\4.0" followed by enter, and then editing the file named "cura.cfg". From the [general] section, remove all lines that start with "window_"

It could be that the teflon (PTFE) coupler has been deformed over time. This is the white part between the PEEK part and the bowden tube. The head is fairly easy to disassemble. Take out the white part and inspect it. Use a small screwdriver to (gently) feel if the channel is still straight or if it has a bulge or severe discoloration. It may need replacement, it is a $15 - $20 part.