iPad Retina, config and test with 2 images

Solar2D General Questions/Discussion
#1

tested an easy app with displaying 2 retina images

local \_H = display.contentHeight;  
  
local bg\_red = display.newImage("bg\_red.png", 1536, 2048, true) -- prevent autoscaling  
local bottom\_blue = display.newImage("bottom\_blue.png", 1536, 249, true)   
  
bg\_red:setReferencePoint(display.TopLeftReferencePoint)  
bg\_red.x=0; bg\_red.y=0  
  
bottom\_blue:setReferencePoint(display.TopLeftReferencePoint)  
bottom\_blue.x=0; bottom\_blue.y= \_H - bottom\_blue.height

config.lua:

 width = 1536,  
 height = 2048,  
 scale = "letterbox",

it works on the corona iPad Simulator. Built it to Xcode and in Xcode i changed hardware to the New iPad. I didn’t work. Images are not scaled properly.
I mean it’s the right resolution: my images and my config.lua.
Corona Version 2011.704 [import]uid: 98393 topic_id: 24412 reply_id: 324412[/import]

#2

__ [import]uid: 98393 topic_id: 24412 reply_id: 98729[/import]

#3

Hi Paula. There are three builds for 704:

704 – Built for Xcode 4.2 and iOS 5.0 and available to test drivers.
704a – Built for Xcode 4.3 and iOS 5.1 and available to test drivers.
704b – Built for Xcode, 4.3 and iOS 5.1 **AND** fixes the iPad3 scaling bug but is only available to subscribers.

Since you’re a test driver, 704 or 704a is going to have this scaling issue with the Retina iPad.

You also cannot get 704b right now because you are a test driver and this may frustrate you, but before you let it, consider you have to be a subscriber before you can distribute your app to the app store anyway, so by the time you’re in a position to let your app out on the real world you will be a subscriber. The only real drawback is if you have a Retina iPad and you want to do test builds on it while you’re still a test driver, you will have problems.

As soon as you’re comfortable with Corona SDK and think its the right tool, I would recommend going ahead and subscribing, at least at the Indie level if you only plan on doing iOS apps. We are currently at build 777 and 778 should drop in the next day or so and has considerable enhancements and features that are not in 704, like very much improved UI widgets like tableView and scrollViews, facebook single sign on, native game center, push notifications, greatly improved sprites, retina text improvements, and a bunch more.

Ancsa hasn’t said when the next public drop will be where these features will become available to test drivers, so you could keep going until the next public release.

In Economics there is a term called “Opportunity Cost” which generally covers this scenerio: “If I buy a computer today at $1000 or wait 6 months and get it for $750” obviously you save $250 by waiting. But how much money or opportunity could you have had in those 6 months? If the value of having it now over 6 months from now is $250 or more, you should buy now. This same concept works with software like Corona SDK. While the price isn’t changing, how much is the opportunity worth to you to a) start using all the new features b) solve the Retina iPad scaling bug c) maybe start selling your apps sooner and d) access to subscriber only areas of the forums? So is it worth spending the $199 now for an Indie license now or does it make sense to wait? Only you can answer that for you.

But that’s what’s up with the Retina iPad scaling issue.
[import]uid: 19626 topic_id: 24412 reply_id: 98745[/import]

#4

thx, corona rules!
yeah, I’ve just wanted to test it out. I’ll buy the license if i’ve a working app.
But what about the Users who don’t know about it? They load the free Trial, sync their app on the New iPad and are disappointed. They don’t know about different builds. I didn’t until now.

[import]uid: 98393 topic_id: 24412 reply_id: 98756[/import]

#5

It’s a communications problem Paula, and it’s not really Ansca’s fault as much as it is us not looking in the right places.

The problem first surfaced in Forum threads, which after a while get buried. The forum search tool isn’t the best in the world and it can make things hard to find.

Ansca has at least 3 blog posts about it:

http://blog.anscamobile.com/2012/03/developing-for-ipad-retina-display/
http://blog.anscamobile.com/2012/03/update-ipad-retina-display/
http://blog.anscamobile.com/2012/03/ipad-retina-display-issues-and-update/

but they only show a few of the latest posts and you have to look back a bit to find them all.

They used Twitter and Facebook to try and get the information about these blog posts out to everyone.

But not everyone follows @Ansca, @ansca_forums and @carlosicaza on twitter and on facebook:

https://www.facebook.com/ansca

But even with all these channels to get the info out, there are going to be tons of people who are not going to see these and and depending on forum searches will create frustrating moments.

I’m sure Ansca would be open to suggestions on more ways to let you know about these things. [import]uid: 19626 topic_id: 24412 reply_id: 98760[/import]

#6

As Rob said we are absolutely open to any suggestions about how we might keep developers better informed so feel free to let us know in threads or using one of our contact forms :slight_smile:

Peach [import]uid: 52491 topic_id: 24412 reply_id: 98968[/import]

#7

Peach (and others),

I have the following config.lua file (I write from the higher resolution to the lower):

if system.getInfo("model") ~= "iPad" and system.getInfo("model") ~= "iPhone4" then   
 application =  
 {  
 content =  
 {  
 --zoom  
 width = 1536,  
 height = 2048,  
 fps = 60,  
 scale = "zoomStretch",  
  
 imageSuffix =  
 {  
 ["@2"] = 1,  
 }  
 }  
 }   
   
else   
 application =  
 {  
 content =  
 {  
 width = 1536,  
 height = 2048,  
 fps = 60,  
 scale = "zoomStretch",  
  
 imageSuffix =  
 {  
 ["@2"] = .5,  
 ["@4"] = 1,  
 }  
 }  
 }   
end

Everything works fine in the Simulator besides the “iPad Retina” option, which calls the @1 image, instead of the @4 one. Any ideas why and how to fix?

Thanks,
Alex [import]uid: 4883 topic_id: 24412 reply_id: 115203[/import]

#8

@alex. It’s hard to say given just the config file, but a handy way to debug these kinds of issues (if your running a recent daily build) is to check what image suffix corona is currently using.

  
print( display.imageSuffix )

If this doesn’t help you diagnose the issue I would be open to taking a quick look for you, if you email me the project to: danny [at] coronalabs [dot] com [import]uid: 84637 topic_id: 24412 reply_id: 115412[/import]

#9

I tried to use the print you recommended in both config.lua and main.lua files. In all of the cases it returned nil. I am sending you my project via email. Thanks for the offering! [import]uid: 4883 topic_id: 24412 reply_id: 115424[/import]

#10

@Danny,

Thank you!

I really did not know about this handful print function to know what image suffix we`re using at the time! :wink:
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 24412 reply_id: 115489[/import]