Cura: [4.8] Selecting model not possible after switching to monitor tab

[marine-3d]

Cura 4.8
Mac OS 11.0.1
2 x UM3's

With a model on the build plate, if you click on the monitor tab and then back to prepare/preview, model no longer selectable with mouse.

No difference if model just loaded and/or not sliced/sent to printer. Can be selected with keyboard shortcut/right click - select all models, but no interaction is possible.

[nallath]

It seems that the issue template has not been filled in entirely. Please check our guide on https://github.com/Ultimaker/Cura/wiki/Reporting-issues for more information on what information we need and why we need it.

[marine-3d]

Hi Nallath,

Hopefully the attached video is enough to go on. Also, managed to isolate the issue to when the UM3 status is cloud or network connected (Blue icon with cloud or tick symbol). When the printers are off (grey icon), the issue isn't present and you can still select the model as normal, even when flicking between prepare/preview/monitor.

Hope this helps.

Screen Recording 2020-11-13 at 16.48.21-1.mov.zip

[fieldOfView]

Does this also happen without the sidebargui plugin installed?

[marine-3d]

Hi fieldOfView,

Just uninstalled the plugin but still the same issue.

[fieldOfView]

~Wew, so it isnt my fault for a change.~ Err, I meant... shame that does not fix the issue.

[scottmloving]

Same issue on my Macbook Pro with Ender 3. I just upgraded to Big Sur (11.0.1) and Cura 4.8.0. After monitoring a USB print, models are not selectable, even after starting a new project or reloading the models.When a model is selected from the object list, the move arrows appear, but they disappear as soon as they are clicked.

[Ghostkeeper]

Hmm, I'm unable to reproduce the issue. I'm basically doing the exact same steps as marine-3d, just with a different model and my own UM3.

Do either of you have a log file you can share with us?

In my log I'm only seeing this warning when switching to the monitor page:

plugins/UM3NetworkPrinting/resources/qml/MonitorStage.qml:75:13: Unable to assign [undefined] to bool

Seems that the supportPrintJobsQueue property is not defined for LAN printers. But that shouldn't really affect anything.

[khaoskosmos]

I have this issue as well. MacOS Big Sur 11.0.1. If I go to the monitor tab and back, I can no longer select the model. Starting a new project does no clear the problem, only completely closing Cura (CMD + Q) and relaunching it.
cura-no-select-macos.mp4.zip

Edit:
Snippet of cura.log attached. I am using MKS WiFi module for monitoring, not usb (using usb gives the same problem, even before I installed the module IIRC).
cura.log

[nikolafamit]

Same problem. Big Sur & Cura 4.8

[marine-3d]

Log attached

cura.log

[evtrados]

Hey all.
Just upgraded to Big Sur v11.0.1 from Big Sur beta, but I cannot reproduce the issue. I used .stl and .3mf files and 3 different models for each. I also tried removing the configuration folder, but still the issue is not there. Could it be model-specific? I doubt it, but in any case if you could send me the model with which you can reproduce the issue, or even better the whole configuration folder, I can try and check if it's appearing then.

Whoop, scratch that! I was able to reproduce it eventually. So it seems that you need to be signed in to your account in order for it to appear. And indeed, the model (even though it's possible to select it again with Cmd+A) is not much usable anymore, since in case you want to perform an action (move it, scale it, etc) you have to do that from the action buttons on the left. I'll bring this up with the rest of the team to see how we can tackle it.
Thanks!

[khaoskosmos]

It doesn't always do it, I'm not sure what triggers it. I am not signed in to Cura at all.

I just had it happen after leaving Cura open after a print. I imported a new stl and could not select it (you can get it to select by click on it from the object list in the bottom right, but you can't interact with it). Completely quitting Cura and reopening allowed me to select and manipulate the stl (same one as before). I could switch to the monitor tab, back to prepare with no issues. I was able to slice, reslice, change tabs, no problems. The printer was actually turned off during this though (it was also off in the first instance of Cura as well).

I turned my printer ON, switched to the monitor tab, back to prepare, and could not select the model again.
cura.log

[SmithyAT]

I see the same issue here, Cura 4.8 and Big Sur 11.0.1.
First I was not able to reproduce it, a user in the forum had the problem, so I looked deeper on it on my system. It has nothing do to with the monitor tab, which I don't use very often. It occurs when I leave Cura open for some time. For example I sliced and printed something on Friday and didn't close Cura. Today (Sunday) I tried to select the part on the build plate I printed on Friday and I was not able to do it anymore. Between Friday and Sunday, I did nothing with Cura.

I think you should be able to reproduce it when you just do nothing for one or two days.

[nikolafamit]

I see the same issue here, Cura 4.8 and Big Sur 11.0.1.
First I was not able to reproduce it, a user in the forum had the problem, so I looked deeper on it on my system. It has nothing do to with the monitor tab, which I don't use very often. It occurs when I leave Cura open for some time. For example I sliced and printed something on Friday and didn't close Cura. Today (Sunday) I tried to select the part on the build plate I printed on Friday and I was not able to do it anymore. Between Friday and Sunday, I did nothing with Cura.

I think you should be able to reproduce it when you just do nothing for one or two days.

Yes. The same situation happened to me. Although, it wasn’t for days but in my case Cura was opened for 6-7h

[fieldOfView]

just do nothing for one or two days.

Yeah, that's not going to happen in a hurry ;-)

[Gatix]

So I have the same issue, Cura 4.8 and Big Sur 11.0.1. I'm on a Macbook Pro with an external monitor.

If the Cura window is on the external monitor, I can't select object nor click on the axes. Moving the window to the laptop screen fixes the issue. Perhaps the difference in pixel density or resolution is causing the issue?

[SmithyAT]

Interesting observation that moving the window to the laptop fixes the issue.
I can reproduce it on my iMac with default resolution but have not seen it yet on my MacBook Pro.

[evtrados]

Developers, see internal issue CURA-7897.

[meichthys]

I can also confirm that the issue happens in Cura v4.8.0 on my Macbook Pro (Big Sur) without any external peripherals attached.

[meichthys]

I can also reproduce the issue every time using the following steps:

1. Open Cura
2. Add stl to build plate and select model
3. Click the following menu icon:
   
4. Click/Drag on the build plate (Not on a model)

At this point the models bill become un-selectable.

[SmithyAT]

Bingo, with these steps I can reproduce it easily.

[nallath]

We've also been able to reproduce it (at least) once on our side. I still don't quite get how this is only happening with big Sur though.

[SmithyAT]

Thanks Jaime for the update. If there is anything I can do or help, just let me know.

[Rukongai]

I get this one a lot. I have to restart the application every 15-20 minutes. Is there any logs I can provide to help track this down?

[nallath]

I'm not the product owner, so I don't decide the priority of issues. But I (and our QA engineers as well) have pushed for this to get priority. As it stands I expect that this will be picked up for the 4.9 release.

Right now it looks like that we have good/reliable reproduction steps, which is usually enough to fix the issue.

[GuyJanssen]

I have exactly the same problem and it popped up after Big Sur was installed and I still had Cura 4.7. It is not solved by moving the window from my external screen back to my MacBook screen.
The problem rises when I add per model settings or even just click on the icon. I use per model settings a lot so I practically have to restart Cura for every object which is pretty often in a 3D printing business. Hopefully you will solve this in 4.8.1 and not in 4.9!