I can't waste time with reinstalls and backing up everything. This forum isn't supposed to serve only as praise but complaining only, in fact that helps to find other users with the same issues and get to a fix.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds First Beta of macOS Mojave 10.14.1 to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Truthfully, you should probably always do a clean install like that whenever possible. You get rid of bloat and likely wont get the issues you have now.
Yeah, it's how us software developers do it. If we didn't, we'd never be able to ship. (Bug-free releases aren't a thing.)
The UI has been ugly and choppy since the Yosemite redesign. Forget all these folks (aka Apple apologists) telling you that you are the one with the problem and that there must be something wrong with your install, Mac OS just hasn’t been as smooth since the redesign. I recently bought a brand new high spec MacBook Pro and I immediately noticed the frame drops compared to my 2013 MacBook running Mavericks which was smooth as silk in comparison. Same thing with iOS since its flat design. There’s something about the flat, bare-bones-minimalistic white UI that doesn’t perform as smoothly as the heavily textured skeunorphic one which is ironic because you would’ve thought the former would perform even smoother not worse. No coincidence that it’s ever since Forstall and his team were fired. Federighi and the team under him leave a lot to be desired.
Last edited:
Anyone else having issues with the new app store for the Mac? It shows two updates for installed programs but all i get is the spinning circle when I click update.
Most stable release ever, Mojave is by far the most stable since the first beta, some glitches in certain betas but that's it, most agree it's the better/best one.
It's because of the retail time blur effect that they added on iOS 7 and Yosemite, it renders in real time for such high resolution screens with weak GPU's, nevermind the intel GPU performance which is a joke.
Read through the posts in this thread. Some are wondering about sub pixel rendering, and many have offered various solutions and work arounds. This thread has just been universal acclaim for Mojave (in fact, it largely hasn't been about that). Those who have specifically asked for help are getting you - your posts have been nothing more than complaints.
In addition, I offered a potential fix of re-installing the OS, if you don't want to take the time to do that, that's not my problem but yours.
Yes I had the same, it keeps spinning and spinning, then you get an update install it, it fails then you retry and it fails.
What worked for me was turning off Wi-fi, shutdown for 5 minutes, turn back on again, turn on Wi-fi and the spinning wheel showed me the update and I was able to install it.
[doublepost=1537909810][/doublepost]
I'm not a "fan" of changing my systems with command lines and workarounds. I like stuff to work as expected out of the box.
Again, for the vast majority of people, things have just worked out of the box. I'm not sure what more you expect here? People have posted some issues, others have posted solutions or workaround, you simply don't want to follow anything.
I consistently have this issue and I have identified it to be a permissions issue that resulted from using migration assistant to a new Mac. The only solution I have found is to delete the affected apps using the command line in recovery mode and then reinstall. Alternatively, disabling SIP would also work.
What am I expecting? You are the one constantly quoting me so I'm only answering your questions. I already gave my opinion and I'm free to join in any conversation related to issues or not about Mojave and this thread in specifically.
I have a 2012 iMac so I am concerned about this change as, apparently, it would impact my experience. I am confused about the issue. As I understand subpixel anti-aliasing is gone, but grayscale anti-aliasing remains. Apparently Mojave defaults to not having this on as users with a non retina screen need to enable this. Turning this on apparently improves readability, but isn’t as good as subpixel anti-aliasing, at least for non retina screens.
But you raise a different issue. You seem to be saying subpixel anti-aliasing, though available, wasn’t being used or capable of being used in some situations. So my question is, how often and where does this come into play? Are you saying the menu bar is an example of a UI element that did not have subpixel anti-aliasing even in High Sierra?
Not entirely though. Even when you disable the blur effects (if you mean ‘transparency’ here) it still stutters and renders at what feels like 20fps instead of the 60fps that I used to love and enjoy in Mavericks and prior versions. The software team has become a joke, or rather already were because the old team who were actually superior at their jobs were fired in favour of this inferior team who are currently behind their lacklustre sloppy software.
I saw choppiness in Yosemite itself, but it got much better with El Capitan thanks to Metal. Early releases of High Sierra also had issues, including memory leaks in WindowServer, likely due to Metal 2 adjustments. I haven't seen anything like that since, and haven't thus far, at all, in Mojave.
Ultimately, it indicates a bug, and hopefully Apple gathers some data to improve performance.
Just because someone had issues and others do not, however, it doesn't follow that those others are "Apple apologists". They're just having a better experience.
The Yosemite UI has more complex effects. Painting a texture isn't that hard compared to vibrancy. If that's what's causing the lag, you can mitigate with the Reduce transparency setting.
Forstall only briefly oversaw macOS at all, so that doesn't seem relevant. Do you want to add a "this would never have happened if Jobs were still alive" in there?
Of course you are! You can say or post anything you'd like. I'm simply pointing out that your posts are not productive - which I guess is really neither here nor there.
I guess, enjoy complaining? The rest of will happily enjoy Mojave. And if we run into issues, which is bound to happen, we'll proactively work through them instead of complaining and making blanket statements.
[doublepost=1537910711][/doublepost]
There is something ironic when people post about "Apple apologists" or "Apple fanboys" when they themselves are nothing more than "Apple haters" because they can't stand when Apple does something positive.
That's makes no sense at all.
Try resetting your Mac by issuing a pram reset, resetting the SMC would be most likely the culprit, that sometimes makes a huge difference.
Last edited:
Yeah I saw the relevant WWDC session.
I've taken some screenshots showing subpixel text rendering on Mojave GM right in front of me. It's probably not fully supported, but it works. It might not work in Dark Mode but I haven't tested that yet as I'm not bothered about it.
Basically.
No, what people are tweaking with the command line is mostly the thickness of the rendering.
(edit)
The above isn't quite right. CGFontRenderingFontSmoothingDisabled does apparently bring back subpixel rendering for non-layer backed views. (Or possibly for applications not linked against the 10.14 SDK.) It
Yes.
From 10.0 on, text on an LCD display got "LCD font smoothing", which takes advantage of a known subpixel layout (a certain arrangement of red/green/blue elements within the LCD panel) to make the text crisper. This takes place on the CPU, and requires that the LCD matches that assumed layout, that the background on top of which the text is rendered beforehand, and some other aspects. (It gets complicated when, say, you have multiple displays that work differently.) This is part of what Quartz/Core Graphics does out of the box.
Critically, for this subpixel trick to work, you need to know in advance what your character glyph looks like, and which subpixels it will fall onto.
From 10.5 and iOS 1.0 on, with Core Animation, an alternative path is offered, where graphics are layered and rendered straight on the GPU. The big benefit is much higher performance. However, text rendered with Core Animation doesn't support such subpixel rendering at all. It basically can't (at least not easily) — as a tradeoff of the performance being better, you can no longer predict the background underneath a text, and as a result, the above will no longer work: you'd need to alpha-blend all elements in advance in order to know how to render the glyph, but at that point, you would throw the performance benefit out of the window.
For macOS, Core Animation was mostly opt-in — developers decided whether they want their views to be "layer-backed" (i.e., with Core Animation enabled) or not. For iOS, it was always on.
One of the effects introduced in 10.5 Leopard is the menu bar has been translucent. (Between 10.5 and 10.9, this could be turned off; this is no longer possible since 10.10 Yosemite.) But, for performance reasons (and perhaps also to show off the power of Core Animation), that translucency took place on the GPU, using Core Animation. Hence, if you have that on, which these days you definitely do, the menu bar is never ever subpixel-rendered. Not in 10.14, but also not for many releases before that.
This matters a lot less on retina displays because the pixels are already small enough for the subpixel effect to be of much additional help. But for non-retina displays, it's a bit unfortunate.
Now here's the part that's semi-informed speculation: I believe the two changes in 10.14 are:
- several cases where layer-backed views used to be opt-in for developers no longer are, as the legacy paths are no longer beneficial or necessary. Those views automatically become layer-backed, and thus, among other things, faster. But, as a side-effect, they also lose subpixel rendering.
- to make things look more consistent, even text that would support subpixel rendering no longer is rendered such
Last edited:
Do you know what the "Use font smoothing when available" option in System Preferences -> General does? I figured that was for sub pixel rendering - but since it's still an option in Mojave that's obviously not the case.
I agree, the old Mavericks times were a joy to use, the UI used to be so smooth and eye pleasing. Now we got unreadable fonts and badly executed Dark Modes.
[doublepost=1537911990][/doublepost]
It does make sense so you shutdown and let all ram processes clear themselves.
[doublepost=1537912023][/doublepost]
Since neither your posts are productive at all, I'll from now on stop answering them. Enjoy your Mojave.
Interesting, thanks for sharing. Would you know what the Terminal command does? It works relatively well for my MBA and Apple Cinema Display and was suggested by someone on Reddit:
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO
I can confirm a choppy UI on my Mac Mini 2012 as well. My MacBook Air 2013 works fine though. Hasen't been like this on High Sierra.
I don't know if it does additional things, but it appears to affect the thickness of the smoothing. That's rather misleading naming on Apple's part.
(Truly disabling font smoothing altogether is not and never has been possible in macOS, at least from the GUI.)
My point was exactly what others have pointed out. The experience of one doesn't define a release. The reality is that the vast majority aren't having problems. This forum needs to stop this belief that a few people having a problem means everyone is. If these problems were as widespread as some believe, they'd be making national news.
Studies have shown places like MacRumors make problems appear far larger than they really are.
It's fine to discuss an issue, but don't jump to the conclusion that it's widespread. It's most likely not.