Font glitchy on MacOS

[RedRightArm]

Application Version
3.2

Platform
Mac OSX v10.13.3

Display Driver
NVIDIA GeForce GTX 780M 4 GB

Steps to Reproduce
Start the program

Actual Results
Text is all funky

Expected results
Text should be legible

Additional Information
Screen shot attached

[Appesteijn]

We made a test version, it includes some bug fixes and a possible fix for the garbled texts. We have tested this version, but not extensively.
The download location is from my personal could storage, since we don't have another way to distribute 'daily' builds (yet).
Could you try Cura 3.2.1: https://stack.mybacklog.info/s/MgLnKXLL0P9ro4M ?

[uffe]

I got see problem as well, tried the (unofficial) 3.2.1 above and it unfortunately does not fix the issue. See https://www.dropbox.com/s/v9jf32s8amtbdwk/Screenshot%202018-02-11%2020.39.54.png?dl=0

[RedRightArm]

Same here. I installed this newer version and still have the same font issue. It looks like there's a problem with the font files. Particularly the bold fonts.

[Appesteijn]

Could you try: https://stack.mybacklog.info/s/F78VhDOiMOQ9Qay

[uffe]

Tried it, but the non-bold fonts are still messed-up: https://www.dropbox.com/s/zphd5e2j6us6vd0/Screenshot%202018-02-12%2015.24.16.png?dl=0

[Appesteijn]

A long shot, but Is this also on the Light theme?

[RedRightArm]

This new download gave me the same issue... at first. @uffe, try this. Load the newest version that @Appesteijn sent. Open it. Switch from dark interface to light interface. Close and quit. Open. Switch from light interface to dark interface. Close and quit. Open. Switch from dark interface to light interface. Close and quit. When you open it this time, see if the fonts are fixed.

Also, don't pay too much attention to following my suggestion exactly. If you have it on light, switch to dark as the first step. If you have it on dark, switch it to light as the first step. The point is, switch it back and forth three times in a row and see if it resolves itself.

Doing this just worked for me. No idea why.

[vegestoc]

That did not work for me. Cura 3.2 macOS 10.13.3

[RedRightArm]

Yeah, I spoke too soon. The fonts came back all screwy again after a short while.

@Appesteijn I had no problem at all with fonts on v3.1. Is it still possible to download 3.1? There's something I'd like to try.

[Appesteijn]

So switching the themes made it work for a short while? That is really weird.

Older versions can be found here: https://ultimaker.com/en/products/cura-software/list

[uffe]

I tried switching back and forth between themes and quitting between each, no visible improvements

[Appesteijn]

**Update Could you try this version: https://stack.mybacklog.info/s/LDltcUP2BXur7AZ

[uffe]

Sorry, still no difference. Is there any way I can wipe a font-cache or maybe help you with info?

[RedRightArm]

I downloaded Cura 3.1 for Mac OS. No problem with the fonts at all. So I downloaded Cura 3.2. Font issue again, same as when I started this thread. So I dug into the app resources and replaced Cura 3.2 fonts with the fonts from Cura 3.1. When I opened Cura 3.2 the fonts were still all wacky. Whatever the issue is, it isn't coming from the fonts. Something in Cura 3.2 is telling it to display these fonts all weird.

[Appesteijn]

Last time we had this, it was a problem that certain margins and/or widths were not rounded numbers and fonts were rendered on behind-the-comma pixels (that don't exist and won't get shown).

I went through all margins and widths to make sure they are rounded numbers, but that didn't solve the problem for you guys.
I also changed the 'custom mode' qml files to the state they were like in 3.1 but that also didn't solve it.

In this sprint we are changing the font (to NotoSans) and updating to Qt 5.10. If I have a build that has theses changes, I'll post it here so you can test it.

[Appesteijn]

Last, last try: https://stack.mybacklog.info/s/iQBrFQrR3DxB7ol

[RedRightArm]

The only font giving me an issue with this new version is the one that italicizes when you adjust a setting.

[RedRightArm]

I spoke too soon. After closing and reopening a few times, the fonts went all wacky again.

[nean-and-i]

3.2.1 font issue still there, even if it is highlighted to be fixed in the release notes:
macOS 10.12.6

[fieldOfView]

I am 90% certain PR #3320 fixes the remaining problem.

We had the "broken font look" on OS X before when the setting names were changed from Label to Text, and the difference between the two was the renderType property (system native vs Qt). With the switch to QtQuick.Controls 2, Label seems to have changed to not include the renderType property, so we get the same miserable rendering again. The PR specifically sets the renderType to use native font rendering again.

[Appesteijn]

Thanks to @fieldOfView it looks like we have a solution. Can you test this build please: https://stack.mybacklog.info/s/wOg49yivjI6AIHv ?

[vegestoc]

Looks great here, thx everyone!

[nean-and-i]

confirm its working now.
But is it normal that font rendering still takes ages on startup (meaning up to 20 sec until tree is shown) ?

[vegestoc]

This is the fastest booting version of Cura I have used. 10 seconds 'loading machines' and an extra two seconds to load the tree menu.

SPECS: 2.3 GHz Intel Core i7, 16 GB 1600 MHz DDR3, NVIDIA GeForce GT 750M 2 GB, Intel Iris Pro 1536 MB. Might be worth mentioning that I have a lot of fonts installed.

[RedRightArm]

Looks perfect at my end too. Thanks!

[nean-and-i]

@vegestoc , very strange, my specs are: 3,2GHz i7, 24GB Ram, NVIDIA GeForce GTX 1070 8GB, macOS 10.12.6.
But, after startup time, only the first 3 lines of the tree are shown after 2 seconods or so the rest of the tree takes that long.

cura startup after first couple of seconds

... than it takes another 15-25 sec in that state until the rest of the tree is shown:

is there a way to debug this?

[fieldOfView]

The best way to solve that delay is to NOT make all the settings visible. Learn to use the search on top instead of always having to scroll through the long, long list. The idea is - and always has been - to only make those settings visible you use a lot.

The delay happens because the GUI framework (Qt) is creating/drawing all the elements for all the settings. This predrawing can be turned off, but that causes delays while scrolling through the long list.

[24c]

@Appesteijn "Can you test this build please:" Just a heads up, works fine after using your 3.2.2 macOS build above, and all text renders properly now. Thank you

[nean-and-i]

@fieldOfView , indeed after getting rid of most of the fields its much faster now.
BUT:
I'd agree on using the concept of a search bar, but then one just can't see all the related options within a section of the keyword, and thats the reason to fallback on tree structure!

Maybe all options can be tagged internally and presented properly on a search, so the output is structured in a way one can even find all related options/parameters to a given search phrase (even if its name differs from search input)?

Otherwise it may sounds like a bit, the search bar exists only because getting rid of rendering issues,...

[ianpaschal]

Since this is fixed and will be included in the next release, I'm closing this issue.

[fieldOfView]

Has a decision been made if the next release will be Cura 3.3 or Cura 3.2.2? If we have to wait until Cura 3.3, I may do a plugin to specifically fix this issue.

[ianpaschal]

I am not sure, actually. Paging @Appesteijn.

[Appesteijn]

3.3 Beta is planned in 3-4 weeks, that will be the next release.

[mechaMecha]

I'd love to be able to download the Cura build that fixes the broken text problem, but it's no longer available through the link provided by @Appesteijn. Is it available anywhere else?

[fieldOfView]

You can download and install my plugin here:
http://files.fieldofview.com/temp/PrepareStageCompactor.curaplugin

This plugin makes the sidebar more compact and fixes the fontissue as a sideeffect.

[Appesteijn]

https://stack.mybacklog.info/s/PyEfKmkt63jkVZ3

[mechaMecha]

Awesome! Thank you very much, @fieldOfView and @Appesteijn !

[mechaMecha]

@fieldOfView , your plugin doesn't correct the problem for me, although it does work better when I use the dark interface. @Appesteijn , installed your Cura build and everything looks perfect. Thanks again!

[SConaway]

@Appesteijn , your version works much better.

[0xMarkian]

@Appesteijn can you post the file again, it's no longer available ...

[fcollingwood]

@Appesteijn can you please post the file again - the last link is no longer active

[24c]

@fcollingwood Have you seen the 3.3 Beta, as this fixes the font issue on macOS too.

[ianpaschal]

@fcollingwood We won't distribute that test build anymore as it's too difficult to have people running these one-off test builds rather than official builds and still diagnose problems. As @24c says though, 3.3 beta has been released which fixes this issue.

[Andreaux]

I downloaded Cura 3.2.1 from the official site yesterday and have my fonts garbled... I see this issue was resolved in February, how come it didn't make it to the downloadable version?? Am I missing something? Any help is greatly appreciated.

[24c]

@Andreaux Have you tried the 3.3 beta? That works fine in macOS for me.
https://ultimaker.com/en/blog/52522-announcing-ultimaker-cura-33-beta

[Andreaux]

@24c Thanks for the advice. I downloaded the beta and although the sidebar seems OK, the Plug-ins window now has garbled fonts. I didn't check further, there might be other issues. Annoying :(

[24c]

@Andreaux Odd, I have that too, but never noticed that one at all, but it's almost the same as the Sidebar distortion previously. I wonder if their plug ins font is pointing to the old one, not the updated NoToSans version? There's probably an issue logged, but I've added to a thread over there. Thanks

[fieldOfView]

The font is not the problem, the renderer is. It should be easily patchable. Thanks for reporting.

[Andreaux]

@24c Thanks for your help. Hope it gets fixed.

[kilomonk]

Cura 3.3.0 BETA works for me on 2012 MacBook Pro non-retina running the latest OSX Developer BETA Version 10.13.5 Beta (17F35e)

Thank you.