As a previous commenter said, this may be associated with Retina MacBook Pros. However, no other software has ever had a problem like this on my machine. The previous version of Cura was fine.
Julian
As a previous commenter said, this may be associated with Retina MacBook Pros. However, no other software has ever had a problem like this on my machine. The previous version of Cura was fine.
Julian
@Julian7 Could you make a photo of the dialog? Thanks!
Edited by thopiekarI have the same issue. iMac 2012 27" (Non-retina). MacOS 10.13.3 from clean install (new hard drive so no old software issues). I did update from Cura 3.1, if that makes a difference
My latest (and last) try to fix this: https://stack.mybacklog.info/s/iQBrFQrR3DxB7ol If this doesn't fix it, the error is coming from somewhere else and you might need to wait for 3.3 for it to be fixed. :(
Sorry to say, but the problem is still there.
Julian
@Julian7 The issue reminds me of another one in Ubuntu.
https://github.com/thopiekar/Cura-packaging/issues/30#issuecomment-365672330
In my point of view, we should try turning off 3D acceleration, because it really seems to be a driver or hardware issue. I already did that in the past for Linux and I hope it should be not too difficult to do that on Mac, too.
Rendering will be damn slow, but if we turn this off and the text is clearly visible then we know that the issue really comes from the hardware or driver level and not from Cura.
Are you interested to make this test? I will try to give you further instructions
Sure. Let me know what to do.
Julian
Alright! I never did this before, but I hope this should work.
What we are going to do is opening Cura from the Terminal
First confirm that this is working:
"open /Applications/TextEdit.app"
The text editor should appear, which confirms me that the "open" command works as expected.
Next try to open Cura the same way.
"open /Applications/Cura-3.2.0-beta.app"
the name of the app might be different. If you have only one installation of Cura installed, just type in:
"open /Applications/Cura" and type twice and fast [TAB]. This should autocomplete the path to the app.
If this is working and you see still the corruption in Cura, then close it again and type in the next command.
"QT_OPENGL=software open /Applications/Cura-3.2.0-beta.app"
This should enforce Cura's user interface toolkit to use software rendering.
As soon as I have time I can try the same with a virtual machine with macOS High Sierra installed.
However, try this first and I will cross fingers for you. Good luck!
PS: The quotation marks are not part of the terminal commands!
Edited by thopiekarI've done that, but still no luck. Some points:
I had to enter:
open "/Applications/Ultimaker Cura.app"
and
QT_OPENGL=software open "/Applications/Ultimaker Cura.app"
The app opens but the text looks as it did before.
However, I noticed this time that the text appears briefly correctly when you open the app, and then it appears to get partly overwritten by some white shapes. It's as if something in the same colour as the background is displaying over the top of the text. Don't know if this helps.
Julian
4 minutes ago, Julian7 said:The app opens but the text looks as it did before.
So in both cases it starts, but no differences?
Yup. Starting from Terminal using both commands gives the same result. I have tried both commands with the original, released 3.2 and the newer version from the link earlier in this topic. The same text corruption in all four combinations.
Julian
This display issue is not limited to Macs. I'm having the same issue with 3.2.1 under Windows 10 Pro.
Here’s a screen recording of starting the app. You can see the text loading fine but then getting messed up the version is the official 3.2.1 from Ultimaker’s website. It looks like the menu starts loading from the bottom or at random and the text doesn’t refresh properly after the other menu elements are loaded. The scrambling is always different also, sometimes it’s almost perfect. Hope we can find a solution for that I’d love to try the new tree supports.
Edited by LazaroFilm
Thank for the video! We fixed it in 3.2.1 for some people, but also knew it was not fixed for everyone. We are still looking into this issue, but nobody in the Cura team has this so it is hard to reproduce and fix.
In fact the bug has been fixed, but no official release has been made with the fix. See https://github.com/ultimaker/cura/issues/3277
latest Mac OSX, CURA 3.2.1. MacBook Pro Retina
same Scrambled Text Issue, If I connect External Display no improvements
so both Displays have the same Issue
Same response.
Good news! I was having the same issue with Cura 3.2.1 on a non-retina 2012 MacBook Pro. I am running 10.13.5 Beta (17F35e). I just switched to the 3.3.0 BETA and it works. So this also works (for me) with the latest OSX Developer BETA.
Model Name: MacBook Pro
Model Identifier: MacBookPro9,1
Processor Name: Intel Core i7
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP91.00D9.B00
SMC Version (system): 2.1f175
Serial Number (system): C02J428LF1G4
Hardware UUID: B2DB5536-B555-52AC-9689-9C06C0901744
Intel HD Graphics 4000:
Chipset Model: Intel HD Graphics 4000
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 1536 MB
Vendor: Intel
Device ID: 0x0166
Revision ID: 0x0009
Automatic Graphics Switching: Supported
gMux Version: 1.9.23
Metal: Supported, feature set macOS GPUFamily1 v3
Displays:
Color LCD:
Display Type: LCD
Resolution: 1440 x 900 (Widescreen eXtended Graphics Array Plus)
UI Looks like: 1440 x 900
Framebuffer Depth: 24-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
NVIDIA GeForce GT 650M:
Chipset Model: NVIDIA GeForce GT 650M
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Dynamic, Max): 1024 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0fd5
Revision ID: 0x00a2
ROM Revision: 3682
Automatic Graphics Switching: Supported
gMux Version: 1.9.23
Metal: Supported, feature set macOS GPUFamily1 v3
Recommended Posts
Msuurmond 28
Than it has to be something else. I revered all 3.2 changes in these files, but you still have the problem. In Cura 3.3 we will upgrade to Qt 5.10 which might fix this, sorry that I can't help you now :(
Link to post
Share on other sites