WARNING: Do not upgrade to Mojave if you have any non-retina screens!

[Fishrrman]

Mr. Tod wrote:
"So what do I need to do to enable it."

I just went through this with my new 2018 Mac Mini setup yesterday.

Here are some steps to take (all require terminal)
Note with each command, you have to log out and then log back in to see the result:

RE-enable subpixel antialiasing for non-retina displays:
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

Next you have to choose the AMOUNT of smoothing you want to use.
It might be necessary to try all of the following commands, to find "the look" that you like the best:

Light font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 1

Medium font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 2

Heavy font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 3

NO font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 0

Source article:
https://www.howtogeek.com/358596/how-to-fix-blurry-fonts-on-macos-mojave-with-subpixel-antialiasing/

PERSONAL EXPERIENCE:
I tried the "medium font smoothing" setup, and it seems ok for now.

 

[Mr Todhunter]

Thank you Fisherman for your help. I've tried all and I've found the Heavy font smoothing best for my taste. So if somebody asks me I would say go for it. That is if what's keeping you from running Mojave is just the font issue.

 

[Crunch]

Mr. Tod wrote:
"So what do I need to do to enable it."

I just went through this with my new 2018 Mac Mini setup yesterday.

Here are some steps to take (all require terminal)
Note with each command, you have to log out and then log back in to see the result:

RE-enable subpixel antialiasing for non-retina displays:
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

Next you have to choose the AMOUNT of smoothing you want to use.
It might be necessary to try all of the following commands, to find "the look" that you like the best:

Light font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 1

Medium font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 2

Heavy font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 3

NO font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 0

Source article:
https://www.howtogeek.com/358596/how-to-fix-blurry-fonts-on-macos-mojave-with-subpixel-antialiasing/

PERSONAL EXPERIENCE:
I tried the "medium font smoothing" setup, and it seems ok for now.

Thanks for the post. So which font smoothing setting resembles the High Sierra and earlier type? Is this known?

Thanks...

 

[Fishrrman]

"So which font smoothing setting resembles the High Sierra and earlier type? Is this known?"

Can't say.
It's a matter of personal preference.

Try them all.
See which one works for you.

 

[chacrat]

Bump

 

[chacrat]

Oops. The post above shows three different images using three different settings.
Mac mini running latest Big Sur on my Dell P3421W (3840 x 1440).
Is it me or is there no effect at all ?

 

[TheRdungeon]

Mr. Tod wrote:
"So what do I need to do to enable it."

I just went through this with my new 2018 Mac Mini setup yesterday.

Here are some steps to take (all require terminal)
Note with each command, you have to log out and then log back in to see the result:

RE-enable subpixel antialiasing for non-retina displays:
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

Next you have to choose the AMOUNT of smoothing you want to use.
It might be necessary to try all of the following commands, to find "the look" that you like the best:

Light font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 1

Medium font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 2

Heavy font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 3

NO font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 0

Source article:
https://www.howtogeek.com/358596/how-to-fix-blurry-fonts-on-macos-mojave-with-subpixel-antialiasing/

PERSONAL EXPERIENCE:
I tried the "medium font smoothing" setup, and it seems ok for now.

Wow, is this still an issue with Mojave? Because I enabled this and chose medium on my 2012 non retina 15" and I swear everything is a whole lot clearer, not sure if it's placebo or not though

 

[madrich]

Mr. Tod wrote:
"So what do I need to do to enable it."

I just went through this with my new 2018 Mac Mini setup yesterday.

Here are some steps to take (all require terminal)
Note with each command, you have to log out and then log back in to see the result:

RE-enable subpixel antialiasing for non-retina displays:
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

Next you have to choose the AMOUNT of smoothing you want to use.
It might be necessary to try all of the following commands, to find "the look" that you like the best:

Light font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 1

Medium font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 2

Heavy font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 3

NO font smoothing:
defaults -currentHost write -globalDomain AppleFontSmoothing -int 0

Source article:
https://www.howtogeek.com/358596/how-to-fix-blurry-fonts-on-macos-mojave-with-subpixel-antialiasing/

PERSONAL EXPERIENCE:
I tried the "medium font smoothing" setup, and it seems ok for now.

I have early 2015 MBAir and I tried the first step and get: -bash: -g: command not found ????

NEVER MIND: I did copy paste error.?

 

[rocknrotty]

Just completed Install 10.14.6 I think this thread is solved as Font smoothing seems to be part of this update. What do you think?

 

[Panthera Tigris Altaica]

Just completed Install 10.14.6 I think this thread is solved as Font smoothing seems to be part of this update. What do you think?

It wasn't a problem for most people in the first place. It was just barely detectable on machines around here, and I only saw the 'problem' after seeing this thread and going looking for it. This machine is currently on 10.15.7 and the 'problem' does not seem to exist, nor has it ever been significant. YMMV but it simply wasn't a big deal, at least not here.