2008-05-22, 16:52
I knew this issue was going to come to a head at some point, and lo, it has. In order to get around the issue of texture size limits for Intel GMA chipsets, I've had to split my main media panel into two separate textures, arranged side-by-side in a group. The group animates in the same manner as the old single texture, of course, so theoretically you shouldn't be able to tell the difference.
Except you can when running any resolution other than the 720p in which the skin's coded. When you run at, say, 1080i, which is the native resolution of my HDTV, there's a pixel-wide gap running down between the two textures, which obviously looks bloody awful. Assuming this is because the automatic scaling isn't precise enough, I need to find a way of dictating the exact skin dimensions at 1080i and, potentially, 1080p.
I've tried putting the correct 1080i dimensions into the 1080i folder but, in what seems to be a nagging issue with this new resizing method, XBMC is still using the 720p folder. Are there plans to get it to recognise the 1080i folder any time soon? Even better, can we expect to see a 1080p folder?
Except you can when running any resolution other than the 720p in which the skin's coded. When you run at, say, 1080i, which is the native resolution of my HDTV, there's a pixel-wide gap running down between the two textures, which obviously looks bloody awful. Assuming this is because the automatic scaling isn't precise enough, I need to find a way of dictating the exact skin dimensions at 1080i and, potentially, 1080p.
I've tried putting the correct 1080i dimensions into the 1080i folder but, in what seems to be a nagging issue with this new resizing method, XBMC is still using the 720p folder. Are there plans to get it to recognise the 1080i folder any time soon? Even better, can we expect to see a 1080p folder?