(2013-10-30 01:35)volcom45 Wrote:(2013-10-29 02:31)Cpuroast Wrote:(2013-10-29 00:23)stevellion Wrote: Yes! 12.3 build runs fine on my OSX Mavericks. (well, it doesn't crash!)
I confirm "xbmc-20131027-9d75530-Frodo-x86_64.dmg" loads and plays fine under mavericks.
A part from the known mouse issue, 2 things remain.
1. XBMC starts up in 16bit color instead of 32 when the default auto-switch GPU setting is enabled, which switches from the Intel to the nVidia GPU.
If this is disabled, it launches with the correct 32bit color. This is something new to 10.9, since 10.8 didn't have this issue.
2. The test builds aren't signed, so the firewall requests authorization every time the application is launched.
I suppose this is intentional, since these are test builds and not the final release.
codesign -dvvv /Applications/XBMC.app
/Applications/XBMC.app: code object is not signed at all
Thanks for pointing out what is going on here, Cpuroast! I've been pulling my hair trying to figure out why my 1080P video had tearing/red lines/glitches in it since mavericks and it must be the 16bit that XBMC is loading with as you say. I tried changing resolution and then changing back and my 1080P was normal again! I can't seem to find this auto switching option you speak of. I have the 2012 13" Macbook Pro with Retina display. My energy saver options don't show the graphics switching that I see in other google search results. I'd really welcome a way to load XBMC in 32bit by default and not have to switch resolutions and back every time for normal playback. Any suggestions would be welcome.
The autoswitch option is only on the 15" model which ships with the Integrated Intel and the nVidia discrete gpu.
The one you have only has the Intel one. So it could simply be general buggy behaviour with OpenGL in 10.9, which may be fixed in 10.9.1 when it's released. But yah, switching resolutions and switching back also fixes it for me.