#GFXCARDSTATUS BEST VERSION FOR SIERRA PRO#

The real problem is Apple shrunk the battery and was hoping efficiency gains would make up for the smaller battery. It uses less power than it's predecessor.

#GFXCARDSTATUS BEST VERSION FOR SIERRA PRO#

The new MBP best card is the Radeon Pro 460 with a 35W TDP. The last MBP best discrete card is a Radeon R9 M370X with a 50W TDP. It just went back to being default for the 15' ones. The 13' Pros have never had them as an option and still don't. Huh? The 15' Pros have always had discrete GPUs as an option or by default. The big difference now is that this is the first time in a while that they've made discrete GPUs an option and the first time they've shipped such a power-hungry AMD GPU (it can drive two 5K displays as well). So they'll either force a switch to the AMD GPU or if any other app is using the AMD GPU when these older apps are launched, the AMD GPU will continue to be used until the older app is quit. There are also some older apps (like gfxCardStatus) that fail to declare they support automatic switching. It's more that too many apps are incorrectly switching to the AMD GPU. 'People were complaining about how much time they had left on their batteries, so we removed the ability to be able to tell how much time is left.' I hate to go back to WWJD, but he would've had someones head for the unnecessary regression in battery life. The non-TouchBar is better but still worse than the 2015 models. Of course the real reason they've removed it is that the TouchBar MBPro 13 has shit battery life. I don't intend to defend this move, but I find the time remaining on my laptop to be variable enough to be nearly useless. I don't think anyone expects it to be 100% accurate. It's a good ballpark for how much time you have left if you keep doing what you're doing right now. I call shenanigans and I'm disappointed this is being removed because I frequently refer to it (on my mid-2012 rMBP). Apple says this is because modern components switch power states so frequently and quickly that it’s hard to correctly estimate remaining battery life based on current activity.

That has always been the case, and is a lot easier to avoid (most app makers avoid frivolous use of Core Animation).The only battery life-related fix in 10.12.2 is the removal of the “time remaining” estimate from the operating system. 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”. 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.

Gfxcardstatus best version for sierra