Cura 4.0.0 incredibly slow on Mac OSX High Sierra

[nallath 1,120]

True, but it was moved to a high enough prio today so that we could work on it.

[ahoeben 1,948]

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.

[wildjokers 0]

30 minutes ago, ahoeben said:

Please let me know if the build works, and if it is indeed faster.

 

I finally upgraded my computer from my 2007 iMac to a 2017 iMac so I can't test this out for you. I nursed that 2007 along for a long time but it didn't like uploading sketches to arduinos (old usb drivers I guess), the cura performance issue, and then the kicker was Turbo Tax stopped supporting the newest Mac OS the 2007 could run. So finally bit the bullet and bought a new one. 

 

Cura 4.0 works great on the 2017! (obviously it is new enough so it supports OpenGL 3.0).

[ahoeben 1,948]

@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)

[Cincinnatus 0]

37 minutes ago, ahoeben said:

@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)

 

Unfortunately not working on MacBook Pro (Retina, Mid 2012); Mojave 10.14.5 Beta (18F108f).  Opening the application presents an error:  "Ultimaker Cura” is damaged and can’t be opened. You should move it to the Trash."  Issue with the signed code being modified.

[phaedrux 2]

@ahoeben I just tried your build on my 2013 MacBook Pro running Mojave and it says the app is damaged and can't be opened. You should move it to the trash. 

[ahoeben 1,948]

Yes, sorry, apparently something went wrong “signing” the app bundle. I’ll post a new version today.

[ahoeben 1,948]

I replaced the build. Could you test again?

[phaedrux 2]

@ahoeben I tried the build. It works this time, however, performance is still awful. If I turn on legacy layer view it's super fast, but obviously limited.

 

[ahoeben 1,948]

Is everything slow, or just the layer view?

 

Is there any way you can force Cura to use the NVidia GPU instead of the Intel GPU? You have an interesting corner case. The Intel Iris Pro gpu in your Macbook PRO seems to not support OpenGL 4.1 (4.0 is the maximum it will do), but the NVidia GPU does.

Edited April 12, 2019 by ahoeben

[phaedrux 2]

It gets very slow in the layer view. 4.0 is much faster using the UI, I'll give it that much. 3.6 was slow all over. Now the UI is mostly responsive even with a model loaded. But once it's sliced and you're previewing it in the layer view it starts to chug. The UI gets slow as well. Once you've changed a setting and the layer view disappears it's faster again.

 

I made a quick screen recording to show it. https://www.dropbox.com/s/3f9z9uimjkzwikf/SlowCura.mp4?dl=0

 

It's definitely using the Nvidia GPU. Sadly Apple isn't allowing nvidia to release any web drivers for Mojave, so it's stuck with whatever Apple has bundled. All part of planned obsolescence. 

[ahoeben 1,948]

2 hours ago, phaedrux said:

It gets very slow in the layer view. 4.0 is much faster using the UI, I'll give it that much.

 

Sorry, this is getting confusing. Is the performance of my build any different for you than the performance of the official 4.0 build?

[phaedrux 2]

54 minutes ago, ahoeben said:

 

Sorry, this is getting confusing. Is the performance of my build any different for you than the performance of the official 4.0 build?

 

Sorry for the confusion. In a word, no. Performance in your build and the official 4.0 is the same. 

 

Is there anything else I can test or information I can provide? I would love to have the level of performance from the legacy view with the detail of the proper layer view.

[ahoeben 1,948]

@phaedrux, thanks for testing. The fix I made is specifically for Macs where everything is excruciatingly slow, because everything ends up being drawn by the processor instead of by the GPU. For them, the workaround with the "Force compatibility mode" checkbox in the general preferences only improved things a tiny bit. My fix forces "compatibility mode" on those computers, not just for layer view but for everything.

 

Your case is why the compatibility mode checkbox is there; apparently your GPU supports the required functionality, but it is just slow when doing it. So you can manually opt for either slow or limited. Fixing that is outside the scope of this particular fix.

[sonmer 0]

@ahoeben, thanks for the test build. I run a 2018 MacBook Pro 13" and your test build feels more fluid in layer view on my machine. Especially when I have many travel paths in the model and display them. But I can't tell yet if the overall UI performance is better, I have to do further tests.

[phaedrux 2]

Just doing some more back to back testing between your build and the officialt build and I think the GUI responsiveness is a bit better with yours when a sliced model is being previewed. 

[hoegge 6]

On 4/4/2019 at 5:13 PM, nallath said:

True, but it was moved to a high enough prio today so that we could work on it.

Good - since of course Cura should be tested and run on the second and third newest Mac OS version too. Fancy graphical features on the layer preview cannot be more important than working reliably on more than the newest MacOS version. Since a lot of software manufactures have issues on different platform versions, you cannot ask customers to upgrade and only use the latest version of an OS. I suppose you don't only support the very newest build of Windows 10 either. 

[ahoeben 1,948]

The fix has been tested internally at Ultimaker, and will be part of Cura 4.1. Thanks for testing!

Edited April 15, 2019 by ahoeben

[yuriy_skvortsov 1]

Hi! I'm new to Cura so I do not have an experience with 4.0. With current 4.1 though on my MacOS the interface is really slow when it comes to changing print settings and especially adding new setting items through preferences. On some settings it could freeze for half a minute easily. Sometimes I also have hard times selecting and rotating the model (either the model is not getting selected or it gets deselected after trying to grab a rotation circle).

Is it the same bug as in 4.0 or it's something new and should be reported?

[ahoeben 1,948]

Without a log, there's no way of telling.

Help -> Show configuration folder. Locate cura.log, upload it somewhere and post a link.

[yuriy_skvortsov 1]

Ok I've reproduced the issue (clicked a couple of times on checkboxes "enable acceleration control" and "enable jerk control" in print settings). The interface freezed for about a minute. Here is what I believe is a relevant section of the log:

 

2019-06-14 12:37:24,808 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._rescheduleCheck [136]: New error check scheduled.
2019-06-14 12:37:31,341 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._checkStack [140]: Need to check for errors again. Discard the current progress and reschedule a check.
2019-06-14 12:37:31,604 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._rescheduleCheck [136]: New error check scheduled.
2019-06-14 12:37:35,380 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._checkStack [140]: Need to check for errors again. Discard the current progress and reschedule a check.
2019-06-14 12:37:35,665 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._rescheduleCheck [136]: New error check scheduled.
2019-06-14 12:37:38,704 - DEBUG - [MainThread] cura.AutoSave._onTimeout [56]: Autosaving preferences, instances and profiles
2019-06-14 12:37:43,799 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._checkStack [140]: Need to check for errors again. Discard the current progress and reschedule a check.
2019-06-14 12:37:44,880 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._rescheduleCheck [136]: New error check scheduled.
2019-06-14 12:37:48,532 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._checkStack [140]: Need to check for errors again. Discard the current progress and reschedule a check.
2019-06-14 12:37:48,931 - DEBUG - [MainThread] cura.Machines.MachineErrorChecker._rescheduleCheck [136]: New error check scheduled.
2019-06-14 12:37:56,778 - DEBUG - [MainThread] cura.AutoSave._onTimeout [56]: Autosaving preferences, instances and profiles
2019-06-14 12:38:28,128 - INFO - [MainThread] cura.Machines.MachineErrorChecker._setResult [188]: Error check finished, result = False, time = 39.2s

 

And here is the full log: https://www.dropbox.com/s/i2z9dgjhwi00ixe/cura.log?dl=0

cura.log

[ahoeben 1,948]

In answer to your original question: this is a different bug, and should be reported.

[yuriy_skvortsov 1]

Ok, I've created an issue here: https://github.com/Ultimaker/Cura/issues/5894