![gfxcardstatus 2.3 pc gfxcardstatus 2.3 pc](https://1.bp.blogspot.com/-ndTe6t7rCWc/XileJf8W8wI/AAAAAAAAMtg/pnQ7fR1-1Mca0ggpwP3nLCVmducamqsUwCLcBGAsYHQ/s1600/PcRepaX%257E03.jpg)
That way, you know when something is draining your battery, and you can send a note to the developer(s) of those apps, and ask them to fix it (unless the app has a good reason to use the discrete GPU, like Photoshop, Keynote, iPhoto, games, etc.). The recommended way to use it is to just start it up, and not touch anything – leave it in Dynamic Switching mode. GfxCardStatus is, first and foremost, a diagnostic utility. It just so happened that in the 10.6 and 10.7 days, it was mostly the former, because nearly every other app caused the discrete GPU to come on.
![gfxcardstatus 2.3 pc gfxcardstatus 2.3 pc](http://simasima.info/wp-content/uploads/2013/02/12430011e.jpg)
There's a good reason that OS X's automatic graphics switching is on by default so that there can be a relative balance between graphics performance and battery life. Having Integrated Only mode available is convenient when you really need to squeeze some extra battery life out of your machine, but it's not what you should be running in 100% of the time. The recommended way to use it is to just start it up, and not touch anything leave it in Dynamic Switching mode. Rather than spend a ton of time trying to fix it, it's being removed altogether, because it's largely unnecessary if you're on 10.8 at this point. I just don't have the time to deal with that anymore.
![gfxcardstatus 2.3 pc gfxcardstatus 2.3 pc](https://cdn.statically.io/img/hiugames.com/wp-content/uploads/2022/06/cossacks-3-v2-2-3-92-6008-pc-screenshot-50372.jpg)
Power source-based switching was removed because a) it has never worked 100% properly, and was causing an unbelievable amount of problems for some people, and b) I get several hundred support emails about it per month. That has always been the case, and is a lot easier to avoid (most app makers avoid frivolous use of Core Animation).If that was the whole point of gfxCardStatus, I wouldn't have buried the settings under the Advanced tab in preferences. CA in turn opens an OpenGL context, which 100% always enables the discrete GPU. So the last *remaining* cause for dGPU is when applications use OpenGL *or* Core Animation. Now that’s no longer the case! WHAT A RELIEF! The issue that Apple has fixed in 10.12.3 was that the mere existence of certain versions of certain frameworks ( without the app even opening any OpenGL contexts) marked the app as “needs dGPU”.
![gfxcardstatus 2.3 pc gfxcardstatus 2.3 pc](https://www.alo.bg/user_files/y/yomusic/4716028_92418676_big.jpg)
The recompiled version linked somewhere in this thread is still recommended, however, because it contains bugfixes not merged into the abandoned official version. Previously, the only way to fix it was to re-compile it with newer frameworks. GfxCardStatus 2.3 (last official version): When Core Animation was removed from the app (in a private build), the application no longer required the discrete GPU. Uses Core Animation, which is the cause of it. MacOS 10.12.3 contains some fixes to Apple’s frameworks! There’s been a development on that front, so I’m writing to make you all aware. This is regarding the state of previous dual-GPU MacBook Pros again.