ti_padawan

1) I see, could be :). I think you had best head over here and ask directly. That's where the key members seem to have moved. 2) Yes, but that's Windows-only. I don't have experience with Optimus myself but some posts come up if you search the forum. E.g. here.

1-2) When you look at the script's GitHub page, experimental support for RX 480 is crossed out. My interpretation is that it didn't work. You might have more luck trying out the EFI app demo but first take a look here, at the very least. 3) I'm not sure but I think I've only seen AMD cards being mentioned to work with software like Adobe. I recommend to search the forum :). 4) In Windows, perhaps (I can not say for sure). As far as I know, not in OS X - you need an external monitor for the cards to be detected (especially NVidia). 5) Depends on which application window is run on which screen. If the GPU intensive application windows will be run on the external monitor accelerated by the eGPU, internal cards will stay cool (as they are idle). However, do note that: - GPU-intensive also means CPU-intensive sometimes (e.g. games). - For some configurations (including the MBP model) the internal screen will still be accelerated by the internal GPU, and for some configurations acceleration will be taken over by the eGPU :).

First and foremost, a quote from Basic hardware guide: I'm not completely sure that includes Akitio's shipped power supply as I have seen people try and succeed in using it while powering the GPU with a separate PSU. However, people on this forum would advice against that, labelling Akitio's shipped power supply as a temporary solution. Then, the issue is how much power your card needs (I don't know). There are 3 input types: - PCIe x16 slot - max. 75W - PCI 6-pin slot - max. 75W - PCI 8-pin slot - max. 150W If you use Akitio's shipped power supply, the PCIe x16 slot's input will be limited to max. 25W (in practice, it should be less - maybe 10 or 15). Nevertheless, don't be afraid of making your own barrel adapter. The important thing to remember is to make the adapter from a cable that came with the PSU (made by the vendor), and to make sure you convert the right end of the cable. Theoretically, you can also use other cables but then, you really need to know what you're doing. You see, vendors don't generally use standardized pinouts on their PSUs' connectors and this can be deadly. I almost fried my system after I made the adapter from a standardized cable that I bought online.

You're welcome :). I appreciate the offer but local reputation is not one of my ambitions. Even if it were, I think this section of the forum is going to die a slow death anyway as key members have been forced to leave. If you don't know yet, they seemed to have moved here.

In that case, I can only think of one more thing: even if it doesn't really make sense and chances of success are little, perhaps it's worth a try to reinstall the game and delete system cache in between :). EDIT: Just searched the forum and found somebody else having the exact same issue: Goalgue's answer: Also see here. So I guess it's really an issue with the game itself. The choice is probably either to install native Windows or put this issue in front of the game's developers.

1) Hmm, that's definitely weird (doesn't happen to me). Granted, I have an NVidia dGPU inside the Mac but by default, Intel iGPU accelerates the internal screen anyway. 2) That's good news. From the top of my head: is there a maximum frame cap setting in LoL? If the game itself limits the maximum amount of stress for your GPU, it's logical that performance won't go past a certain point. Although I don't understand how (and more importantly why) this number would auto-adjust itself. 3) Some applications let you choose but it seems that most depend on the GPU that renders the application window in question (in OS X, I mean). 4) That's weird again... I don't think installation of D3 made any system changes regarding the eGPU because it would need the user's confirmation and normally, system integrity protection would remove the changes with the next restart anyway. As it happens, I can offer performance comparison because I play D3 as well. In my case, GTX 970 reaches up to 100 FPS (maximum settings) in town but again, make sure that you don't limit the GPU potential in the settings (Options / Video / Max Foreground FPS). I have the eGPU in a PC case that is mostly open at the back (closed everywhere else) and as far as my skin sensors go, the temperature inside doesn't really exceed 70° C. EDIT: If all else fails, perhaps you could try to reset the PRAM, run automate-egpu again and restart the Mac. If I remember my own beginnings correctly, I had some issues and resetting the PRAM helped. Same might go for deleting system cache files, perhaps - I did that with a great app named CleanMyMac. Sierra experiences I read on another forum also seemed to indicate that OS X may take a few restarts to really adjust to some drastic changes.

Do I assume correctly that 33 FPS was achieved on the external monitor while 60 FPS was achieved on the internal one? Two things might be worth a shot to perhaps grant us a little more data: 1) Run the game on the external monitor while using the default OS X drivers (no eGPU acceleration). 2) Run Unigene Valley benchmark and observe the eGPU's FPS: - what is the difference between minimum/maximum FPS? - is the average FPS actually close to the maximum? EDIT: OS X 10.11 or 10.12? And which version of the script did you use? In my case, OS X 10.11 and automate-egpu pre-v1.0.0. (November 2016).

@1TrikPony I have an Akitio + GTX 970 + MBP 2012 and the acceleration gives cca 5 times better performance so personally, I'm not too keen on seeking the culprit around the GPU itself. What if you try to unplug the "unneeded" external monitors and launch a game on the remaining one? Btw, how did you manage to do that? In my case, internal and external screens are either all accelerated by the eGPU or iGPU (at least, according to what the system settings say)? Are you running Windows?

How are you powering your Akitio? Have you selected "NVidia Web Driver" in the NVidia control panel? Have you also set the external monitor as primary in your system's settings? Have you restarted the Mac after running the script?

That benchmark effort has obviously been run on a Windows system installed on a Mac. Now that IS possible and like I said: However, I have never seen a way to leverage a Pascal card on macOS yet (in terms of graphics acceleration of course). The followup comment to your question at Youtube sums it up in a way too:

I don't know about your specific case but at first, I had some issues with launching my MBP 2012 as well. As far as I remember, resetting the PRAM helped (make sure to rerun the automation script afterwards). Then, it was about figuring out the timing and the order of turning things on. For me, I turn on the external monitor, the egpu and then the mac, one after the other. I turn on the egpu by turning on the power supply which takes about 2-3 seconds to start up so only then I actually start the mac. Perhaps try to tinker with this too to find just the right routine :). As for the power-off issue, that might suggest something more serious. I'm no expert but system log may be useful to the community :). I think you should also start a new thread and not hijack this old one.

What you need is an appropriate web driver that would enable the system to use the card to accelerate the video output. But like I said, such web driver has not been "released" (developed?) yet and it will probably take a long time still, if there's ever going to be one... Chance for you to solve this problem on your own is like 1 in a million - basically none :). What you can do is install another system on your Mac - a display driver has been released for both Windows and Linux. On the contrary, CUDA driver for macOS and pascal cards is released and working. But I don't know if CUDA is going to work without the web driver...

@pokerman837 There are no OS X drivers for NVidia 1000 series cards yet and I reckon they will still take quite some time...

@shirazigs I'm still on El Capitan myself but I believe that the "G-SYNC requires an NVidia G-SYNC(TM) display" explains it. Either you don't have a G-SYNC certified external monitor or the driver thinks you don't. I have a G-SYNC certified monitor myself so this is a very interesting topic for me too. However, macOS might first have to be updated to fully support G-SYNC (or free-sync, for that matter). Experimental support is also indicated by this thread on insanelymac.com. Sadly, it rather seems not to work for now :(.

Yep, everything works wonderfully. Guess I was lucky not to fry anything the first time... Thank you so much @Dschijn :).