I asked on an internal list. The one person who responded said it should be safe to set to high.
-Alex On 12/11/14, 1:26 PM, "Harbs" <[email protected]> wrote: >I assume someone on the AIR team did tests. Is there anyone you can ask? > >On Dec 11, 2014, at 10:58 PM, Alex Harui <[email protected]> wrote: > >> OK, I tried your example and read some articles I found on the web. It >> seems that when you create a .AIR file, the requestedDisplayResolution >> locks in how many pixels the runtime is going to render and on retina >> screens the OS scales up the low res. I rarely run published AIR apps, >> but when I just ran our published Apache Flex Installer, I can see it is >> also not as nice looking on the retina screen. Interestingly, the .AIR >> file from your example does not have an option for “open in low >> resolution”, but the actual .app for the Installer does, but it appears >>to >> be locked to “open in low resolution” and you can’t change it. >> >> So, this is an AIR issue and controlled by the >>requestedDisplayResolution >> flag. We might need to do some tests on what happens if you set that >>flag >> to true and run on a non-Retina Mac, and whether cpu overhead goes up or >> not when that flag is set. >> >> At first, I couldn’t believe that the scaling would cause these kinds of >> visual artifacts, but after thinking about it more, I can see how, if >>the >> app generates bitmaps and chooses anti-aliasing values based on low-res, >> when scaled, those choices will be more apparent. >> >> -Alex >> >> On 12/11/14, 11:55 AM, "Harbs" <[email protected]> wrote: >> >>> When I debug the app, it looks fine without editing the >>> requestedDisplayResolution. It’s only when I export it as an AIR >>>package >>> and install that, things get blurry. >>> >>> On Dec 11, 2014, at 9:29 PM, Alex Harui <[email protected]> wrote: >>> >>>> I’ll take a look. I have a Macbook Pro with Retina. >>>> >>>> I have a feeling there is more to it than just this setting. I have >>>> been >>>> running the Apache Flex Installer I built and it has an -app.xml with >>>> requestedDisplayResolution commented out and I don’t see blurry >>>>visuals. >>>> >>>> Are you running these apps with the runtime baked in or via adl? >>>>Could >>>> you be launching some other version of adl? >>>> >>>> Remember that Flash/AIR rendering is done via scan-line conversion. >>>> That >>>> means that the set of vectors on the display list are visited for >>>>every >>>> output pixel. I’m sure there are optimizations in there, but if you >>>> have >>>> to compute 4 times as many pixels, that might add up to something, >>>> possibly even the cpu utilization when the app is drawing an >>>>animation. >>>> >>>> We have a descriptor-template in templates/air/ in the SDK folder. I >>>> always thought FB used that one. We could teach the installer to not >>>> copy >>>> the one from the AIR kit, but first I want to make sure that this is >>>> truly >>>> the root of the problem, and that it won’t be gpu/cpu intensive to >>>> default >>>> to rendering times as many pixels. >>>> >>>> -Alex >>>> >>>> >>>> On 12/11/14, 10:25 AM, "Harbs" <[email protected]> wrote: >>>> >>>>> I just tried on 4.10 with the same result. >>>>> >>>>> Here’s a zip of a really simple project with two AIR files. One with >>>>> standard, and the other with high. The difference on Retina displays >>>>>is >>>>> very obvious. Even the window chrome is blurry using the standard >>>>> setting. >>>>> >>>>> https://www.dropbox.com/s/emj93lumi6s06m7/BlurryTest.zip?dl=0 >>>>> >>>>> On Dec 11, 2014, at 8:10 PM, OmPrakash Muppirala >>>>><[email protected]> >>>>> wrote: >>>>> >>>>>> Can you try with an earlier version of the Flex SDK (4.13 or 4.12) ? >>>>>> I >>>>>> am >>>>>> wondering if we messed up something.. >>>>>> >>>>>> Thanks, >>>>>> Om >>>>>> >>>>>> On Thu, Dec 11, 2014 at 10:06 AM, Harbs <[email protected]> >>>>>>wrote: >>>>>>> >>>>>>> I have no idea why. >>>>>>> >>>>>>> Even text was blurry in the app I built. >>>>>>> >>>>>>> Searching the web brought up very few results. You’d think >>>>>>>something >>>>>>> like >>>>>>> this would have an awful lot of hits… >>>>>>> >>>>>>> On Dec 11, 2014, at 7:38 PM, OmPrakash Muppirala >>>>>>> <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> It seems like not a lot of folks have run into this issue. >>>>>>> >>>>>>> >>>>> >>>> >>> >> >
