2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10
- 2017 13" MacBook Pro TouchBar (Model 14,2)
- 3.1 GHz Intel Core i5
- 8 GB RAM
- 256 GB SSD
- macOS High Sierra 10.13.2
- Windows 10
- Aorus GTX 1070 Gaming Box (without the included card)
- MSI Radeon RX 560 Aero ITX 4G OC
- Some old ViewSonic 1080p monitor (connected via HDMI to the graphics card)
(It's a dorm room, in case you're wondering)
- I bought the Gaming Box enclosure used without the normally-included GTX 1070
- Open up the enclosure, insert the graphics card (it's board powered, so the power connectors in the box are unused), close it up
- Plug the monitor into the graphics card's HDMI port
- Plug the thunderbolt 3 cable into the top-left port on the Macbook (the one closest to the screen)
- Note: the other port on the left side seems to work just as well in my experience
- Install Goalque's automate-eGPU (instead of disabling SIP completely, I just allowed kernel extensions with "csrutil enable --without kext")
- Install Windows 10 via the bootcamp assistant
- Use Display Driver Uninstaller to remove all included AMD Radeon drivers
- Create a bootable USB with Goalque's apple_set_os.efi
- Shut down the laptop, plug in the thunderbolt cable to connect it to the enclosure, boot into Windows using apple_set_os.efi
- Install Radeon drivers from the AMD website
I haven't run any benchmarks, but here's my experience with a few games (all run on the external 1080p monitor at native resolution):
- Rocket League (max settings): ~75 fps
- Assassin's Creed 4 Black Flag (high settings): ~40 fps
- Tribes Ascend (max settings): ~60 fps
- Counter Strike (max settings): ~70 fps
- Since setting this up I've switched to booting via rEFInd so that I don't need the bootable USB for apple_set_os.efi, but it doesn't make any functional difference
- Booting into Windows without apple_set_os.efi results in a crash on startup
- I tried various hotplugging methods and none of them worked for me
- Occasionally, even with apple_set_os.efi, Windows won't properly recognize the eGPU when booting up, and crash on startup. Power-cycling the eGPU (plug out, wait a few seconds, plug back in) seems to fix the issue
- Use with the internal display also works via AMD XConnect. Ejecting the external graphics and disconnecting the eGPU afterwards works without any problems in that case. However, connecting the eGPU while the laptop is on hasn't worked for me
- I have a mouse, keyboard, and external SSD hooked up to the USB ports on the gaming box, and haven't had any problems (I'm running the non-H2D firmware)
- To change the lighting: the Aorus Graphics Engine utility didn't work for me, but the Gigabyte Xtreme Engine for their headsets did
Hey, can I just confirm that it is alright to not use an external monitor and just use the internal display with this setup?
Great little set up this... have you tried any other games? Would be interested to hear how PUBG fairs. I'd love a mini AMD eGPU set up but have never managed to beat error 12, no matter what instructions I follow.
Thanks for your sharing!
I bought a Aorus gtx1080 gaming box and replaced the gpu to MSI rx560(used - bought from ebay) just like yours. But when I connected it to my 2016 MBP13(10.14.2 Mojave), it didn't work(rx560's fan didn't run and the light of gaming box didn't open). The power seems work great cause the little fan of it was running. I did a test with the original 1080 card, card's fan running good and the light was on - even I didn't set the workground of Nvida.
I thought it's the rx560's problem maybe. What do you think? Did the fan run when you first connected?