ahoeben

Ok, thanks for testing. Something must have gone wrong while signing the patched application. I’ll create a new build tomorrow.

That looks like a clone, not an Ultimaker-produced model. As a result, it is hard to know what firmware would work on that printer.

@wildjokers, you could still do me a favor and test if my build works correctly on your new computer. Specifically, I would like to know if it correctly shows the advanced Layer View (with the horizontal "play" slider as well as the vertical layer slider)

See this thread with a link to a test-version that hopefully fixes the slow performance in Cura 4.0

I have created a repackaged build of Cura 4.0 with my fix for the slow rendering on Macs that don't support the newer OpenGL features that Cura uses for the advanced layer view: http://files.fieldofview.com/cura/Ultimaker Cura-4.0.0.dmg Other than the change in the OpenGL context, it should be axactly the same as the original build, and work with your existing configuration. Please let me know if the build works, and if it is indeed faster.

Because I can make a plugin that fixes some of your issues, but I have no say about the UI of Ultimaker Cura? Would you rather I don't make an alternative GUI? I don't understand responses like this. Note that what the plugin does would not have been possible with a plugin in previous versions of Cura. Ultimaker have made the Cura UI more plugin-friendly. Now you have a choice, even if you don't like the default option.

The Sidebar GUI plugin available from the Marketplace fixes most of your points.

I looked up the D600 Pro, but it looks like the dual nozzles are very close together. How do you think this will work if you print two of the same models simultaneously?

Cura has no native way to do this, but I am sure it can be made to support it (for example with one or more postprocessing scripts). The problem is that I have no idea how "ditto printing" is implemented for the D600 PRO creatbot in gcode.

Cool. But that still has nothing to do with the Sidebar GUI plugin.

Autosave cannot currently be disabled easily. You can make it happen less frequently, by adding a preference in cura.cfg. Open it in a text editor (while Cura is not running), and add the following line in the [cura] section: autosave_delay=1000000 This makes the period between autosaves 1000 seconds (ie: fairly long). The default is 10 seconds.

How about after a restart? I am mostly interested in the often-recurring freeze, and if it is less often with the "Automatically discover local OctoPrint instances" option unchecked (and after a restart, to be sure).

The Connect to OctoPrint dialog has a checkbox to "Automatically discover local OctoPrint instances". Could you check if the delay also happens with that checkbox unchecked? You would have to add your printer manually (but I think you already did).

Interesting that it also happens without the OctoPrint plugin (but less frequently?) Unless there is something freaky with your network/drive setup, I don't see how autosave could be the problem.

For now it would help if you could post your cura.log somewhere so I can see if something strange is going on. It should be in your configuration folder (Help -> Show configuration folder)

The Support Blocker tool can be found in the toolbar on the left. The Sidebar GUI plugin does not change that.

I created that plugin. I did not know about this issue. I’ll try to reproduce it. Can I ask you to do some more testing?

Can you go to the Marketplace, Installed tab and disable the OctoPrint Connection plugin and restart Cura, to check if it also happens without that plugin?

When Cura is starting to become unresponsive, how much memory is it using (according to Task Manager?) Are you using any plugins? What printer do you use, and how is it connected?

This thread is about the Printer Settings plugin though, which is available.

The Anycubic definition specifically says that the printer does not support different materials. The fact that you can see/create/activate materials is actually the bug here.

Note that a .pyd file would only work on Windows.

What do you want to achieve by converting the plugin to a pyd file? All plugins are distributed as .py files. You may be able to get it to work with .pyc files instead if you want to obfuscate your code.

Yes! No? I don't know... Can you rephrase the question?

I gave you enough time 😉