GAD

Every print since upgrading to 4.12.1 has ended like this: This is an S5 that's never done anything like this before. The noise is startling and it knocks over any tall prints when it does this. 3MF file for this particular print is attached. UMS5_Small_clasp.3mf

Huh - I didn't even known "Print via Cloud" was a thing. Neat! 🙂

Came back to report that the problem is still there, but I guess that isn't important now. 🙂 Changed to this: 53 def start(self) -> None: 54 """Start the network discovery.""" 55 #self._zero_conf_client.start() 56 for address in self._getStoredManualAddresses(): 57 self.addManualDevice(address) 58 59 def stop(self) -> None: 60 """Stop network discovery and clean up discovered devices.""" 61 62 self._zero_conf_client.stop() 63 for instance_name in list(self._discovered_devices): 64 self._onDiscoveredDeviceRemoved(instance_name) Will restart and report back tomorrow.

Assuming plugins is /Applications/Ultimaker Cura.app/Contents/Resources/plugins, I have done this: 61 62 #self._zero_conf_client.stop() 63 for instance_name in list(self._discovered_devices): 64 self._onDiscoveredDeviceRemoved(instance_name) 65 I will restart Cura and let you know how it goes. FWIW my favorite text editor is vi and I've been programming since '1981 and using Linux since Redhat v 0.9. 🙂

Cura has slowed to the point of uselessness twice more since my last post, so I definately agree that it's the UM3 Networking plugin that's at fault.

Thank you all.

Just got back into Cura after three days with only the UM3 Network Printing plugin disabled and it's still quick and responsive, so I do think the UM3 Network Printing plugin is the culprit. I will re-enable and report back, but I'm now convinced that's it.

Also just a note - not being able to resize the Marketplace window is infuriating. 🙂

This afternoon (I was out all day) Cura is slow and unusable. I'm going to re-test having the Networking plugin disabled because when I tested that Cura had locked up entirely and it's never done that before, so I'm not convinced it was the same problem.

Cool - thanks!

The USB Printing plugin is now disabled

From here: This material is NOT COMPATIBLE with the material station Seems like it was and then was removed: Release notes Version 1.0.1 Version 2.0.1 changed marketing text and brand name version 2.0.2 changed name on cura slicer version 2.1.0 change material station temperature version 2.2.0 take out material station Why?

Right - but why?

Another question - slicing seems to be single threaded. On complex objects slicing takes forever but CPU never goes above 100% meaning it's only using one core. Why?

11 hours later and Cura is locked up hard. Can't do anything and have to kill it and restart.

I have enabled all above listed disabled plugins except for UM3 Network Printing. I'll report back in a day with results.

OK so I turned off the plugins listed above and even just doing that I daresay it was immediately faster than it's ever been. I left it overnight because usually by the next day Cura is unusable, but this afternoon it's just as quick and responsive as it was yesterday. These are the plugins I disabled: - Firmware Update Checker - Firmware Updater - UM3 Network Printing - USB Printing (optional) - Ultimaker Digital Library

I should note that the CPU behavior is the same after restarting Cura so I guess it's not CPU causing the problem. I can't disable networking because that would completely break my workflow.

Here's an update. I've upgraded Cura to 4.11.0 System is still a 2019 Mac Pro with 24 Xeon cores, 2TB SSD system drive, and 176GB of RAM currently running Big Sur v11.5.2 I have to quit and restart Cura every day because it becomes unusable. If I quit and restart it works fine for a few hours, but I WILL have to restart it eventually. Last night I restarted, printed this little spinner, then went to bed and let Cura sit. Here's how it's behaving this morning - all I'm trying to do is reposition the place with command-mouse-movement. Here's a video link of the issue:

Thanks, all. I hate prime towers because they're wasteful and my other 2-color prints haven't needed them, but they've all be short and squat. I tried one last night and it was a disaster. I have no idea what happened since I don't usually have adhesion problems, but I'll give it another go.

This is an Ultimaker S5 Pro Bundle (though it wasn't ordered that way). The black filament is Ultimaker Tough-PLA, and the blue is MatterHackers PLA-Pro. Settings are default Cura "Normal" 0.15mm layer height. The stringing (if that's what it is) is only in the direction of the Print Core Switch. In other words it only seems to be happening when the printhead moves to switch between colors. The rest of the print is nice and smooth. The stringing is happening with both colors/materials and appears to be happening both on the inside and the outside of the object, which is a "dragon egg" that's hollow. Actually looking at the second pic I can see one string on the left side, but on the last one of these I printed the entire thing is smooth except for about a 45-degree arc. . This does not happen at all on single-color prints. I haven't noticed it on PLA/PVA prints, but then PVA is usually pretty messy anyway and the PLA would be encased in the PVA most times I've done that. Any ideas?

Now that's a cool post. Thanks for sharing!

OK. My printer sat unused all night which means Cura was sitting unused in a window all night as well. This evening I went to start a print and Cura is again running at 100%. Log is attached. As is a screenshot of its current condition as I found it. Note that before I went to Cura, I had loaded new filament on the printer. This is generic MatterHackers PLA Pro that I manually selected as "Tough PLA" on the S5's screen. Also here's a screenshot of top for the sake of more data. cura.log

I had restarted it an of course it's running fine so far today. When it happens again I'll grab the logs. Logs are pretty large - do you want the whole thing or just the last hour or so?

Just thought I'd pipe in here. I'm happy to help in any way, but I can confirm that Cura gets almost unusable for me after which I need to restart it. It then works great for a while then gets more and more slow until i have to close and restart it. Here are my computer specs: System: Mac Pro (mid 2010) OS: Mojave 10.14.2 Mem: 64GB RAM CPU: 12-core 3.33GHz Xeon GPU: Radeon RX 580 8G Printer: Ultimaker S5. Firmware 5.4.27.20191212 Cura: 4.3.0 FWIW, I had the same issue when using BCN3D Cura with my Sigma and Sigmax, but I know that's a different version. When Cura is slow, top shows the cura process consuming a single core at 100%. Right now, Cura is not doing anything but sitting in a background window, but it's consuming 100%, but again - only one core.