Application Version
3.2.1
Platform
Windows
Display Driver
Intel HD Graphics 4000 20.19.15.4835
Printer
Ultimaker 3 Extended
Steps to Reproduce
After upgrade to 3.2.1 the camera stream is no longer visible in the Monitor tab. The stream is still available on http://
Could you please share your log file so we can look for possible causes?
2018-03-13 09:36:10,173 - DEBUG - [(10484)-MainThread] UM.Controller.setActiveStage [155]: Setting active stage to MonitorStage
2018-03-13 09:36:10,186 - WARNING - [(10484)-MainThread] UM.Qt.QtApplication.__onQmlWarning [267]: file:///C:/Program Files/Ultimaker Cura 3.2/plugins/UM3NetworkPrinting/MonitorItem.qml:9:5: QML Image: Failed to get image from provider: image://camera/2
2018-03-13 09:36:12,132 - DEBUG - [(10484)-MainThread] UM.Controller.setActiveStage [155]: Setting active stage to MonitorStage
2018-03-13 09:36:16,588 - DEBUG - [(10484)-MainThread] UM.Controller.setActiveStage [155]: Setting active stage to PrepareStage
2018-03-13 09:36:16,607 - WARNING - [(10484)-MainThread] UM.Qt.QtApplication.__onQmlWarning [267]: file:///C:/Program Files/Ultimaker Cura 3.2/plugins/UM3NetworkPrinting/MonitorItem.qml:24: TypeError: Cannot read property of null
2018-03-13 09:36:17,307 - DEBUG - [(10484)-MainThread] UM.Controller.setActiveStage [155]: Setting active stage to MonitorStage
2018-03-13 09:36:17,313 - WARNING - [(10484)-MainThread] UM.Qt.QtApplication.__onQmlWarning [267]: file:///C:/Program Files/Ultimaker Cura 3.2/plugins/UM3NetworkPrinting/MonitorItem.qml:9:5: QML Image: Failed to get image from provider: image://camera/4
Any progress on this? I'm having the same problem
Same problem here
I have the same problem, Running Ultimaker 3 Extended over our company network, occasionally you will get a still from the camera but most of the time it wont load at all.
Good to see its not just me!
I just did a clean install of Cura 3.2.1 on a machine that has never had Cura installed before and the issue is the same.
Is this ever going to get looked in to? Its a big issue for me
Just upgraded to 3.3.1 and this issue appears to be fixed. Although I also did a firmware update on the printer at the same time so I am not sure which of the two actions solved the problem.
@peteros85, is it also fixed for you?
Problem for us is solved with the latest version 3.3.1
Most helpful comment
@peteros85, is it also fixed for you?