AIR 15 Beta - New Improved compiler engine for iOS is now Default.

stortof

I have the same bad result with the default "Verdana" font (which is not embedded)... 🤬

var txt:starling.text.TextField = new starling.text.TextField(100, 50, "test", "Verdana", 15, 0xFFFFFF);

stortof

I have seen this in the release note of AIR 16.0 :

"iOS tlfText not rendering, when application packaged with new fast packaging engine"

But in my case, it is not a tlfText, but the simple starling Textfield.

joshtynjala

Here's something interesting I noticed in the release notes for AIR 15:

[iOS] [New fast packager] Some applications compiled with older ActionScript compiler won’t work with new fast packaging engine but when rebuild again with latest ActionScript compiler apps work fine. (Bug 3837665)

I'm sure that they'll get it fixed, but if you're still using the legacy compiler from Flex SDK 4.6, now might be a good time to upgrade to the new ASC 2.0 compiler in the AIR SDK.

stortof

You are RIGHT !!!!!
Everything is working now ! (exept some stupid warnings with the TweenMax library - so I need to disable warnings to compile...)

Thanks Josh 🙂 !

soccerob

I'm still having some trouble compiling through FlashDevelop (air 16.0.0.214). I have my target air sdk set, is there a way to change to the ASC 2.0 compiler in Flash Develop? or is that the same thing?

Framais

@soccerbob it sounds like you are using AIR SDK 16, in which case you are(FlashDevelop is) already using the ASC 2.0 compiler.
You would only be using the ASC 1.0 compiler if you were using the AIR + FLEX SDK

If you are interested in learning more about the differences between ASC 1 and 2, here's an interesting reading: www.bytearray.org/?p=4789

soccerob

Well I discovered that I actually WAS using the old ASC 1.0 compiler in FlashDevelop. My setupSDK.bat file was definitely pointing to the latest AIR 16 beta, but under Project -> Properties -> SDK, it was set to <b>Default (Flex 4.6.0, AIR 3.7)</b> instead of <b>Air 3.7</b>.

I was able to confirm this by adding -inline as an additional compiler option under the Compiler Options tab, when I tried to build, it said: unknown configuration variable 'inline'

This FINALLY fixed my compilation problems and I am able to compile without the argument -useLegacyAOT yes

Daniel

That's a great find! I was not aware that many developers were still using the old compiler.

Now, it's crucial that anybody who still finds a problem with the new packager files a bug report — Adobe is really keen to fix all those issues.

I put together a list of tips what best to do when filing a bug report at Adobe's bugtracker: Starling FAQ - I found a bug in Flash/AIR

I know that some of those AOT bugs are hard to reproduce, so I asked Adobe what to do if you can't come up with a sample. Here's what they said:

If developer can share working sample app with AS code then it would be the best thing. In some cases, it is hard to recreate the issue in sample app, and if developer doesn’t want share AS code, then swf+app-xml file would be helpful.

Either a sample or a working app with blocked features/ watermarks etc increases chance of finding and fixing the bug a lot more.

Thanks in advance for anybody who takes the time to write such a report! I know that all of us want to have that new packager as stable as possible, and that's the best we can do to make that happen. 🙂

joshtynjala

I'm also surprised at how many people are still using the legacy Flex 4.6 ActionScript compiler. I recently had to add some weird workarounds to Feathers because the Flex AS3 compiler was creating bad bytecode while the new AIR SDK AS3 compiler (ASC 2.0) worked like a champ. I wish that hadn't been necessary.

bali33

How to check if we are using the legacy compiler or the new one ? Don't want to looks like ignorant, but compiler and packager are two different things, is that right ?

Robominister

@bali33
Yes, they are different things. The 'legacy compiler' in this case is the ASC1 compiler (part of the flex sdks). If you are using a pure Air SDK in your project (no merge between Air and Flex sdks), then you will be using the new ASC2 compiler. These are the compilers you are using to build a swf file, when you compile you AS3 project.

The ios packager is a seperate application (although it is a compiler in a sense?). Both options are there by default in the newest Air sdks. The way to choose between the 2 is a command line argument (-useLegacyAOT=true, or something like that) to use the old java packager, if you don't give that argument, it uses the new one by default.

Framais

@bali33 you can perform a quick test to double check if you are using ASC 2.0. Just add:

-inline

to the list of Additional Compiler Options and if you get no error messages during compilation complaining about the -inline parameter then you are successfully using ASC 2.0. This is because the inline functionality is only implemented in ASC 2.0 and not in ASC 1.

« Previous Page