So regarding Thuderbolt/usb3.1/usb-c port- today I received a USB3.1-Type-C To SATA 22 Pin 2.5 Inch Hard Disk Adapter in the mail. Unfortunately, it does not work in OSX. Tested it in Windows 10 where it is fully functional, but in El Capitan, Disk Utility etc doesn't see the port at all or any volumes attached to it. Made sure to boot with the drive attached before powering up, in windows installed the Thunderbolt Driver that Gigabyte offers Windows users for the GA-170X ud5-th as well and made sure that Thunderbolt was enabled in bios and that thunderbolt security was set to legacy mode. (based on what some people do to get TB2 working on older gigabyte motherboards) Continue to get no thunderbolt recognition in System preferences as well though for now. Not sure if there are other settings I should tinker with.
Not sure what else I can do to test as there really aren't many thunderbolt 3 products on the market and the Startech TBT3TBTADAP thunderbolt 2 to thunderbolt 3 adapter seems overpriced to me at $80. Will pick up a TB3 HD enclosure when they are more widely available and there are some decent budget options to test more, however hopefully by then apple will have released more skylake/TB3 computers and implementation on the hackintosh side of the fence will be more complete.
One other thing that is slightly frustrating at the moment is trying to get 4k@60HZ to my Vizio M49-C1 monitor display. The display is capable of 4k@60HZ when connected via HDMI 2.0 to its HDMI input #5 according to its manual. I've read that AMD 7970's should be capable of driving 4k @60HZ in osx via displayport with an active adapter. I bought a
Club3D CAC-1070 Displayport 1.2 to HDMI 2.0 UHD (CAC-1070) active adapter that should work at 60Hz with an HDMI 2.0 cable, however when I try to create a custom profile in switchresx for 3840 pixels × 2160 @ 60HZ, I get a black screen when selecting it in the Daemon. Not sure if I am inept with setting up a proper profile in switchresx, or if I am running into a hackintosh related issue or an inherent osx issue with this, but it would be nice to sort out if anyone has any advice.