oh man ...  Just unboxed my iPad3 ...    loaded up my app.  It looks like complete crap.

The world has known about the iPad resolution increase for months...   please tell me there is a fix to this. 

I have tried out our Air app on it and it really looks fine.  We use pngs for a number of buttons and also display pictures. That all looks as good as iPad 1.  The labels and text buttons are perhaps a little "fuzzy" compared to iPad 1, but nothing near a deal breaker.

Its not as bad as the 2X button.

It's basically the regular iPad version running on the new iPad.  What my concern is .. is that I have a lot of stageWebView elements... and all of these look fantastic with all the HD support.  What looks horrible is seeing those screens on the same stage as my now low res PNG's and Text.

Please Adobe fix this!

Hey, thanks RichardLord.  I'm trying that now.  Do you know if linking it to the iOS 5.1 sdk results in making the app only compatible with 5.1 and higher?

i posted banch of comperecent screens in other thread.

http://forums.adobe.com/message/4272566#4272566

No solutions though on fixing issues on not perefect images, even with vector

can u post a pix of high quolity rednering? i still stuck with very visible pixilization on edges

so all you did is set requestedDisplayResolution to high and enabled smoothing? CPU or GPU rendering? What was canvas resolution? Aslo what font did you use?

i guess i need to try to reduce stage size maybe it will help

Whats direct render mode? Do you think there might be differenve between 3.1 and 3.2? i thought only difference is multithereted video rendering?

acrowne - I didn't use the native extensions dialog in Flash Builder, I used the command line to build the .ipa. I also used the Air 3.2 SDK but I don't expect that is a factor. I only built the project I am currently working on. The difference when compiling against iOS 5.1 was distinct with vector graphics clearly rendered at a higher resolution than when compiling against iOS 5.0 or when running on an iPad2. I didn't have time to do more and the iPad is at work so I can't investigate further today.

I did not use the command line, but rather Flash Builder's interface.  But reading Adobe's support materials, I gather that in the Native Extensions dialog, setting the Apple iOS SDK is the equivalent of setting -platformsdk. So I set that value to point to my copy of the iPhoneOS5.1.sdk.  Below is my sample project code.  In the application descriptor file, the only thing I changed from the default is my project id to match the provisioning profile and adding <requestedDisplayResolution>high</requestedDisplayResolution> to the iPhone xml tag.  I tested this out on my iPhone 4 and it worked great.  On the new iPad only the top corner of the image appears on the screen because of the scale.  I am using AIR 3.1, so unless the 3.2 beta includes a fix, it seems that Adobe needs to produce an update before AIR supports the new iPad's display.  Please tell me if you find anything I missed.

package

{

          import flash.display.Sprite;

          import flash.display.StageAlign;

          import flash.display.StageScaleMode;

          import flash.display.Bitmap;

          public class RetinaTest extends Sprite

          {

                    [Embed(source="bgd@2x~ipad.png")]

                    private var bgdImg:Class;

                    private var bgd:Bitmap;

                    public function RetinaTest()

                    {

                              super();

  // support autoOrients

                              stage.align = StageAlign.TOP_LEFT;

                              stage.scaleMode = StageScaleMode.NO_SCALE;

                              bgd = new bgdImg();

                              addChild(bgd);

                    }

          }

}

RichardLord, I can confirm that running the identical test I posted above using AIR 3.1 but using the command line instead of Flash Builder produces a retina version of the app.  I am going to try out making a placeholder native extension and see if that will force Flash Builder to include the -platformsdk line, which I am presuming is being left out.

Thanks for the blog post.  Great info.

Adrian

Success!  So after including Adobe's sample vibration Native Extension (here) in the build and setting the requestedDisplayResolution to high, I am able to use Flash Builder 4.6 to build retina enabled iPad apps.  Thanks RichardLord for the help.

iBrent, I am currently just doing an Actionscript Mobile project, not a Flex Mobile project.  But it seems that as long as there is a native extension present, it will include the -platformsdk if you have specified an SDK in the Native Extensions dialog.

So can I achieve this from Flash Professional 5.5?  If so can someone tell me how ?

Cheers!

Visually, my Flex app looks great on the retina screen compiled with the iOS 5.1 sdk.  Performance feels a bit slower. Unfortunately, where it was solid with the iOS sdk that comes with Flash Builder 4.6, it hard crashes (i.e. throws the user completely out of the app - no runtime error to debug) rather often under the 5.1 sdk.  Same results when using AIR 3.1 and 3.2 RC1.  So begins the testing of workarounds.    

Update: Setting <renderMode>gpu</renderMode> in my -app.xml file appears to have solved the performance issues I was seeing on the iPad3.