Now that we've established the UM3 Networking plugin as the likely culprit, if you need that plugin we need to dig a little deeper.
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. The number of spaces before #self._zero_conf... should stay the same.
This should disable the zeroconf discovery of printers. Effectively this means that you have to manually add your local printer by its IP address.
Recommended Posts
Top Posters In This Topic
27
21
17
6
Popular Days
Jan 3
12
Jan 2
6
Sep 2
5
Jan 20
5
Top Posters In This Topic
GAD 27 posts
nallath 21 posts
ahoeben 17 posts
Kenobinai 6 posts
Popular Days
Jan 3 2020
12 posts
Jan 2 2020
6 posts
Sep 2 2019
5 posts
Jan 20 2020
5 posts
Popular Posts
Nerfstrike
I think I figured it out. I was looking at some forums about internet slowing down cura, and apparently cura tries to connect to web printer servers like octoprint. I am on a large wireless network be
nallath
In 4.5 we also switch to a much more extensive crash logging system, so let's hope it gives us what we need 🙂
GAD
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
Posted Images
ahoeben 1,986
It is. It is being replaced entirely by a new implementation that I hope will perform better too. For now it seems to be resizable.
Link to post
Share on other sites
GAD 10
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.
Link to post
Share on other sites
GAD 10
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.
Link to post
Share on other sites