

- GFXCARDSTATUS SIERRA INSTALL
- GFXCARDSTATUS SIERRA DRIVERS
- GFXCARDSTATUS SIERRA UPDATE
- GFXCARDSTATUS SIERRA DRIVER
Sleep Wake Failure with High Sierra 10.13.4, with some saying it's FileVault related.
GFXCARDSTATUS SIERRA DRIVER
That note still in the latest web graphics driver download page for 10.13.4.)
GFXCARDSTATUS SIERRA DRIVERS
(The Nvidia web drivers have listed "Beta" support for MacBook Pro 11,3 (2013), MacBook Pro 10,1 (2012), and MacBook Pro 9,1 (2012).
GFXCARDSTATUS SIERRA UPDATE
(UK)"I kept hoping an OS update or Nvidia driver update would help. I downgraded my Early 2013 15" rMBP back to 10.12 from 10.13, performance is back to normal proving it is the OS and not hardware as had been suggested in the early posts on some discussions. Although the support has got better as of 10.13.4, the onboard intel graphics are often better but still poor. Frame rates as low as 2fps in the UI and using apps such as Photoshop, InDesign, Illustrator and games.
GFXCARDSTATUS SIERRA INSTALL
The download page for the graphics driver has an install note on High Sierra Security/Privacy settings, also on our driver update post.) Hopefully they install the Graphics driver update for 10.13.4 to see if that helps. BTW: I saw an apple forum post from someone that upgraded to 10.13.4, then got the CUDA Update required (in prefs) - installed CUDA 387.178, but prefs still shows "update required". ( Did you install the April 2nd CUDA 387.178 & web graphics driver update for 10.13.4 (17E199)? Driver v387.10.10.10.30.103, not seen any later updates for D/L as of April 9th. Are you running the default driver or nvidia's web driver?ĭefault Apple Driver, although I do have the NVidia CUDA driver installed. Just FYI - maybe there is something involved in the switching back and forth between the two GPUs that is slowing things down or something? FWIW, I run the dGPU (discrete GPU) mode non-stop because I've got a second monitor attached all the time. I'm running 10.13.4 on a 2013 rMBP with a Geforce 750M GPU and seeing no major frame drops in the UI.

Is Chrome 80 designed to switch dynamically? My Chrome 80 doesn't. So, Firefox doesn't behave the same as Chrome - at least in my MacbookPro setup. This is the behavior I had seen before 74. In Firefox 74, when I set fault-low-power to False, Firefox switches between the discrete and the integrated GPU dynamically. "Use hardware acceleration when available" has always been enabled. With Firefox 74, switch to discrete GPU never happens. Switch back to integrated GPU never happens. In Chrome, when I turn on "Use hardware acceleration when available", graphics switches immediately to the discrete GPU.
