iPad - Why option for Overscan/Letterbox?

0belisk

So i just published my new app's iPhone version, built for iPhone 5 using Overscan for older devices.

And now im releasing the iPad version, but i dont understand why we must select an option for Overscanning or Letterbox, for iPad publishing... when as far as i know all iPads are the same aspect ratio, and ive never had any issues releasing iPad apps prior to the Overscan update.

So basically, which option do i need to choose? Or how do i not select any, as it is not necessary, unless there is indeed a new iPad with a alternate aspect ratio that i am unaware of.

Thanks in advance!

carlblanchet

I use letterbox when publishing to iPad, the screen is so big that the black bars (if even there which won't be the fact if the dimensions are proper) wont make a difference.

Edit: I published mine with retina iphone resolution, which is why i mention letterbox

PixelMetal

If you're doing a separate release specifically for iPad, I wouldn't use either of those options. If you have to select one, use Overscan, because if you've published at iPad resolution it should not, in theory, do anything.

Note that I say this having only tested on Android where Overscan & Letterbox don't work at all, but based on what those terms mean, I'd go with Overscan.

Socks

. . . If you have to select one, use Overscan, because if you've published at iPad resolution it should not, in theory, do anything. . . .

If you've published at the right resolution (in fact just at the right aspect ratio) for iPad both overscan and letter box should have no effect.

0belisk

. . . If you have to select one, use Overscan, because if you've published at iPad resolution it should not, in theory, do anything. . . .

If you've published at the right resolution (in fact just at the right aspect ratio) for iPad the both overscan and letter box should have no effect.

Yeah i just tested this and published a letterbox and overscan version of my app and played it on my iPad 2, both were exactly the same, so whatever option you choose, it works.

Which is what i thought, but i dont see why gamesalad includes the option and makes it compulsory to select it, when it's only applicable to the iPhone format.

carlblanchet

It's still a fresh feature :P

Hymloe

I find that with the new Overscan feature, it is no longer respecting my attempts to control the camera's origin point.

I even have debug text readout saying that it is at the camera origin, but it simply isn't. It's positioned too high, and is therefore cutting off the bottom of my menu.

Think I might have to drop back to Game Salad Creator 0.10.0. Shame nothing really works as it's meant to around here.