ahoeben

The plugin should work regardless of whether a model is selected. It even works when there is no model at all. Perhaps just measuring two points on an empty buildplate will make it clearer how this plugin is supposed to work. On an empty buildplate, with the measure tool selected, there should be a single dot in the center. Now first click on a few cm to the left of the center of the buildplate, and then a few cm to the right of the center of the buildplate. The plugin moves the dot that is closest to the mousepointer to the position that of the mousepointer. If you click and hold the mousebutton, you can drag the dot around.

It could be that @ftoons is a Cura Essentials user, and the plugin is not (yet?) approved for Cura Essentials.

At least we now have a culprit. I have a hunch the real problem is the combination of something in your network and the "zeroconf" (also known as bonjour, avahi) component that is used to find your printer on the local network. If you would like to experiment, open plugins/UM3NetworkPrinting/src/Network/LocalClusterOutputDeviceManager.py in a text editor and change line 62 from self._zero_conf_client.start() to #self._zero_conf_client.start(). Put the # directly in front of self._zero_conf_client.start(), not at the beginning of the line. This should disable the zeroconf discovery of printers. Effectively this means that you have to manually add your local printer by its IP address.

Can you try disabling the UM3 Network Printing and USB Printing plugins on the Installed tab of the Marketplace?

Ok, so that rules out the UM3 Network Printing plugin. Could you try the same thing with just disabling the USB Printing plugin?

There is no way to do this manually in Cura. What you can do is slice the model at different layer heights and manually (in a text-editor) combine parts of these files. But that is tedious work and easy to screw up.

CuraEngine comes with Cura. If you have Cura installed, you also have CuraEngine.

Center to center. The center of the dots "snaps" to the geometry.

Here's a good article on seams: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/troubleshooting/seam.md

The MeshTools plugin has an option to automatically scale STL files as they are loaded, if you always save STL files in inches.

This is a known issue with the OpenGL implementation in VirtualBox. See this issue for some more details: https://github.com/Ultimaker/Cura/issues/6822 (and https://forums.virtualbox.org/viewtopic.php?f=2&t=92944&start=15&sid=af29b5f389e761fb2e85feeb20d544b5)

Please check this fix: https://github.com/Ultimaker/Cura/issues/10837#issuecomment-972146096

Ahem... 2021-11-17 12:35:50,913 - INFO - [MainThread] UM.PluginRegistry.loadPlugin [426]: Plugin [SimulationView] has been disabled. Skip loading it. @Rock-princess, you have managed to disable the plugin that is responsible for showing the sliced view. Go to the "Installed" tab in the Marketplace, and make sure the checkmark in front of Simulation View is checked.

I'm not pretending, I am stating fact. I believe the official support for Ultimaker products is to contact your local reseller. Just because there are friendly people here who spend their own free time to help people does not mean that they owe you anything.

See this post: The "Line type" scheme was made the default up in Cura 4.9. Up until Cura 2.5, there was no other scheme than linetype, but between Cura 2.5 and 4.8 the material color was the default and line type was an option. Line type is a more informative scheme; of something is going wrong it often helps what parts of a layer is printed as what sort of line.

I'll ask the exact same question then:

One thing to pay attention to is that when installing a new version of Cura, it will ask you if you want to uninstall the previous version(s). If you choose to uninstall the previous version, the uninstaller will ask you if you want to remove the settings of that previous version. If you let the uninstaller remove your settings, there is nothing left for Cura to upgrade to the new version. DO NOT let the uninstaller remove your settings if you want to use your settings and profiles in the new version! READ what the installer is asking you instead of just "clicking through".

What was changed is the default setting of the color scheme. The color scheme now defaults to showing the types of lines, whereas in previous versions it was set to show one color per material by default. But you can change it back with the "color scheme" option in the top bar.

This is a community forum, not an official support channel.

Aww... I created that plugin. Then again, it was causing you this issue. Then again then again, I updated it more than 6 months ago to fix this issue, before it became an issue with the release of Cura 4.9 (ie when Cura 4.8 was the current version).

It isn't. Supports are only created as 2d lines per layer, not as 3d geometry.

You are using a fairly old version of the "Printjob Naming" plugin. Update that plugin from the Marketplace, and this issue will go away.

@Cuq will know for sure, but I think the "Copy scripts" step is no longer necessary, since the Post Processing plugin can now find the scripts in the folder of the plugin.

We're going to need to see your entire Cura.log. For some reason the GPU "shader" that draws layerview has not been loaded. We need to figure out why. See https://github.com/Ultimaker/Cura#logging-issues

Your GPU should suffice. You may have disabled the plugin that handles the layer view ("preview"). Go to the "Installed" tab of the Marketplace and scroll down to the "Simulation View". Make sure the checkmark in front of it is checked.