10.13.3 automatic graphic switching not working on 2017 15" MBP

[wubsylol]

I've noticed that since installing 10.13.3, my system is stuck using the Radeon Pro 560, shaving a huge chunk of my battery life away.

I've done a PRAM and SMC reset, even tried flicking the Automatic Graphics Switching checkbox in energy saver settings a few times to no avail.

Anyone else seeing this?

 

[Mr. Zarniwoop]

How can I test? iStat Menus shows the Radeon Pro 560 now just browsing Safari, I think it used to show the Intel most of the time. But I'm not honestly sure?

 

[PBG4 Dude]

My MBP seems to be switching between the two GPUs, according to gfxcardstatus. Flips to dGPU when I fire up Unity 3D or Blender, and flips back to iGPU once I’m out of those.

 

[Mr. Zarniwoop]

gfxCardStatus shows switching without issues. I had Photos open which was forcing the Radeon.

 

[OriginalAppleGuy]

I just updated tonight and remembered to switch my settings back to allow automatic switching. So far, It's staying on the 560 when in the past it would be on the Intel. I'll keep watch and see what it does.

 

[--ld--]

I updated to 10.13.3 on my 2017 15" MBP and had no issues with the graphics switching yet. I have gfxCardStatus installed and everything is set to automatic switching.

 

[OriginalAppleGuy]

One of the things I've noticed is Google Chrome Helper seems to be causing the Radeon to be engaged now when before it was not. I quit Chrome and the the system switches to the Intel GC. Strange.

 

[PBG4 Dude]

One of the things I've noticed is Google Chrome Helper seems to be causing the Radeon to be engaged now when before it was not. I quit Chrome and the the system switches to the Intel GC. Strange.

If you look on the Energy tab in Activity Monitor, it will tell you what programs are currently forcing dGPU usage. That’s how I found out the Kindle program was engaging the dGPU.

 

[OriginalAppleGuy]

If you look on the Energy tab in Activity Monitor, it will tell you what programs are currently forcing dGPU usage. That’s how I found out the Kindle program was engaging the dGPU.

That is cool! My iStat was showing me Chrome was GPU Dependent but Activity Monitor shows a lot more. Thanks for the tip.