2013-10-23, 04:24
So I upgraded to Mavericks, all went well, using Cassiel's 12.2 version with the mavericks patch.
It runs fine for the most part and like others have pointed out, the mouse has minor issues, I'm using a remote most of the time, so it's not exactly a problem.
The one annoying issue I've encountered is that XBMC insists on starting up in 16bit color mode.
As seen here:
10/22/2013 10:08:21.858 PM WindowServer[89]: Display 0x04280140: Unit 0: Mode 1680 x 1050, CGSSixteenBitColor, Resolution 1, ioModeID 0x80001001, ioModeDepth 0x1, IOReturn 0x0
10/22/2013 10:08:21.860 PM WindowServer[89]: Display mode changed
So as you can imagine, banding everywhere on the UI and on playback.
The workaround is to change the res to something else in xbmc and 32bit will return, then change it back to the original resolution.
This happens everytime XBMC is started. I've also tested with an empty config folder, same issue.
If I force the system to only use the Intel or only the nVidia, it will start in 32bit more correctly.
However, if I leave automatic switching enabled, it will switch to the nVidia GPU when XBMC starts and somehow select 16bit instead of 32bit color.
This is on 10.9 final using a MacBook pro which contains an Intel HD4000 and an nVidia GT650M video card.
This was fine in 10.8 with automatic switching enabled.
It runs fine for the most part and like others have pointed out, the mouse has minor issues, I'm using a remote most of the time, so it's not exactly a problem.
The one annoying issue I've encountered is that XBMC insists on starting up in 16bit color mode.
As seen here:
10/22/2013 10:08:21.858 PM WindowServer[89]: Display 0x04280140: Unit 0: Mode 1680 x 1050, CGSSixteenBitColor, Resolution 1, ioModeID 0x80001001, ioModeDepth 0x1, IOReturn 0x0
10/22/2013 10:08:21.860 PM WindowServer[89]: Display mode changed
So as you can imagine, banding everywhere on the UI and on playback.
The workaround is to change the res to something else in xbmc and 32bit will return, then change it back to the original resolution.
This happens everytime XBMC is started. I've also tested with an empty config folder, same issue.
If I force the system to only use the Intel or only the nVidia, it will start in 32bit more correctly.
However, if I leave automatic switching enabled, it will switch to the nVidia GPU when XBMC starts and somehow select 16bit instead of 32bit color.
This is on 10.9 final using a MacBook pro which contains an Intel HD4000 and an nVidia GT650M video card.
This was fine in 10.8 with automatic switching enabled.