2007-12-05, 16:43
Unfortunately, this post brings up the rest of the gui into question:
http://forum.xbmc.org/showpost.php?p=147...tcount=356
http://forum.xbmc.org/showpost.php?p=147...tcount=356
dan_f14 Wrote:one of the reasons it has been such a big success is that the hardware being coded was a constant factor ie the xbox.
atom Wrote:That's some awesome work. Still doesn't meet the opengl requirement for XBMC...
vibe666 Wrote:I'm actually surprised that more people aren't jumping on thislack of interest is not the problem; we said time and time again throughout this topic thread (and everywere else that the PS3 have been suggested) that the problem is XBMC requires OpenGL 2.0 support (or OpenGL 1.5 + OpenGL GLSL extension at the minimum) that features 24bpp or 32bpp for 3D hardware-acceleration support, which XBMC GUI need to run smoothly at an acceptable frame-rate. Without a device driver that enables hardware support you might get 1 or 2 frames-per-seconds displayed on the screen, ...try watching a movie at that rate, (a movie is made up of 24, 25 or 30 frames-per-seconds but your TV actually refreshes the screen even more often than that, more like 60 frames-per-seconds).
Gamester17 Wrote:None of Team-XBMC developers have the low-level skills required to make such OpenGL device drivers themselves, thus will have to wait and see if someone else produces them for Linux on the PS3.
wHack Wrote:It seems to me that if you guys aquired a few devs who understood how to write stuff at this lower level the conversion would be quite possible and much cleaner and more efficient than using a full featured OpenGL layer.Again, we do not have any programmers with such skills, and simply aquiring a few developers with such skills is not a simple as you might think, (I refer to the fact that when we announced the Team-XBMC was looking for Linux developers and that news even got slashdottet we still only gained one new developer since then, from the very beginming of the Linux port project). You have to remember that all developers (and all other members) of Team-XBMC are unpaid volunteers who only work on XBMC in their spare time as a hobby for fun, and they only spend time on features/functions that interest them personally, ...they do not work on XBMC for you, the end-users of XBMC, they work on XBMC for themselves.