#1 piece of advice for "Security Update"s from Apple...DON'T RUN IT WITHOUT THINKING !!! (ie, see if new Web Driver out yet)
With 10.12.2 going official there were new Secuirt Updates for 10.10 and 10.11.
And both broke Web Drivers
And now we're getting emails.
Best bet for now is to use the "Beta" driver for that OS. I know this work for 15G1212, haven't got word on the 10.10 OS.
Look before you leap and always wait for the WebDriver !
We will update the driver page within 24hrs of Nvidia releasing a fix.
So we are getting more than a couple emails regarding the mismatch between 10.12.1 update from Apple showing build "16B2657" and Nvidia providing a driver that matches to "16B2555".
I can confirm that the mod listed below will work. Just change the "OS required" string to match to "16" and it works fine. (You will need to disable CSR)
Working on new stuff, and can report EFI running on some new cards soon.
Orders still shipping, all good here.
Nvidia has already released a final driver for macOS 10.12. Please see our driver page for a link.
I was able to EASILY move from a Sierra Beta to the Final version
Thanks again to Nvidia for their continued support.
There are now new drivers for OS X 10.10.5 and 10.11.6 available on our Drivers page. They resolve the issues created by the OS X security update from two days ago.
Well, haven't got any emails about this yet but be aware that if you have any of the "Must Have Web Driver" cards (780Ti/Titan Black/750/980/980Ti/Titan-X) that you should NOT run this update yet.
Nvidia will doubtlessley have an update in next day or two. So, most folks should just be patient and all will be well.
For those who clicked before thinking and now don't have a working GPU going backwards isn't easy.
With a few terminal commands you can be back up running.
1. Go to S/L/E and drag "NVDAStartupWeb.kext" onto the desktop. Do it again. OSX will warn you that there is already one on desktop. Hit "Keep both" This should result on one with right name and one named with the number "2" after it. The one with "2" is your backup in case things go south.
2. Right click to get inside, use X-Code or a text editor to open the info.plist. Drill down to NVDARequiredOS. Where it shows "15G31" change this to just "15G"
3. Save and close.
4. Use a kext utility to install this into S/L/E.
5. Boot into recovery partition. This can be tricky, even with an EFI Maxwell card. Have a look for the nv_disable=1 trick, it will allow any EFI card to get there.
6. Open the terminal here and type "csrutil disable". You will need an admin password.
7. Change boot args to remove nv_disable.
7. Reboot, all should be well.
Please note, these instructions assume a fairly high level of knowledge. If you don't understand this stuff, just wait a few days for the fix.
UPDATE: Best option is to roll back to "BETA" versions of these drivers. Look on our Driver Page. Find your OS (ie, 10.11.5 or 10.11.6) and look for FIRST driver in list. Easy way to tell Beta from Final is the letter "b" in the name versus "f". (Captain Obvious reported this)
UPDATE #2: Nvidia has kindly released drivers for 10.10.5 and 10.11.6, linked on our driver page. The 10.11.5 driver is corrupt so those folks should keep using Beta driver until it gets fixed.
We have heard from several folks with issues using Adobe applications with latest OSX release.
Adobe has identified the issue and there is a temporary fix.
Loks like between Apple, Nvidia, and Adobe somebody dropped the (metal) ball.
Note that this has nothing to do with MacVidCards or our EFI roms or cards. The issue also occurs on EVGA GTX680 Mac Edition cards and GT750 cards in Macbooks.
Will update when a better fix is out.
UPDATE: New Nvidia Web Driver on our driver page.Can someone report if this fixes and allows Metal to be used?
So our Customer Service and orders have been slightly erratic recently. We have encountered family issues which will hopefully be resolved shortly. Apologies in advance if you feel neglected, we will fulfill all orders and answer all emails, maybe just not as quickly as usual.
Thanks for your patience.
OSX Sierra has full Fury Drivers ! But they're hidden away, and we need Hackintosh buddies to help unlock
As I recently posted on Netkas, OSX Sierra has drivers for the AMD Fury Nano. But oddly, if you put one in a cMP, it is useless.
I was only able to get it working on nMP 6,1 via an eGPU.
The "little trick" is that you have to add the device id of "7300" to the Baffin personality. For those not in the know, Baffin is a new Polaris chip.
Sooner or later we will figure out what the "missing piece" is to get this working on cMP. Probably just a little tweak here or there. If we could do that, then maybe we consider an EFI rom and taking the time to find PCIE 2.0 resistor.
Before anyone gets TOO excited consider that for both 6970 and R9 290X/390X Apple gave, and tooketh away. Driver support was good, then broke in later iterations. But fun trying anyway.
I dragged the Rift setup into the Lab where the cMPs are. Hooked it up to a 4,1/5,1 with a 3.46 6-Core and a Titan-X.
To make sure it would work well, I also used an Inatek USB 3 card.
Setup was even easier than 6,1 nMP.
On the plus side, it ran perfectly. On the "minus" side, it kept remid=nding me that my hardware wasn't good enough. I think it meant the built in USB 2 or the Westmere CPU.
But it ran just fine.
The game Chronos was smooth and efficient, looked good and ran smoothly.
I may try with just the USB 2 and see what it does. But it is proven, there are Macs that can run VR. They just need a little help.