Severe Artifacts in AIR beta 15 in BitmapData.draw()

[Mario_Klingemann]

The latest beta has introduced a serious bug in BitmapData.draw() - when drawing a bitmapData onto another using a transformation matrix, the pixels are getting messed up:

Example:

package

{

  import flash.display.Bitmap;

  import flash.display.BitmapData;

  import flash.display.Sprite;

  import flash.geom.Matrix;

  public class Air15ArtifactDemo extends Sprite

  {

  public function Air15ArtifactDemo()

  {

  stage.scaleMode = "noScale",

  stage.align = "TL";

  var map:BitmapData  = new BitmapData(1024,1024,true,0);

  var map2:BitmapData  = new BitmapData(500,500,true,0xff000000);

  var m:Matrix = new Matrix();

  m.translate(-250,-250);

  m.rotate(Math.PI*0.25);

  m.scale(1.3,1.3);

  m.translate(512,512);

  map.draw(map2,m,null,"normal",null,true);

  addChild(new Bitmap(map,"auto",true));

  }

  }

}

[Pahup]

Hi Mario,

Thanks for reporting the issue. You faced this issue on mobile or desktop? Could you please share the OS/Device and OS version? Also, what is the SDK version, it is 15.0.0.196 or 15.0.0.216?

Thanks

-Pahup

[Mario_Klingemann]

That's on Desktop, Windows 8.1, 64 bit - I've also filed a bug report in the bug base.

I think the SDK does not really matter in this case since it also affect old pre-15 AIR application - I am pretty sure the bug is in the runtime - but it's 15.0.0.196 in this case.

[Pahup]

Thanks Mario, could you please share the bug number? I've forwarded the issue to appropriate team.

-Thanks

Pahup

[Mario_Klingemann]

It's this one: Bug#3805033 - Visual artifacts in old AIR projects running on the AIR 15 runtime

[david doull]

Hi Mario,

did you find a workaround for this? You seem to have fixed it in nodeworx

[daveomatic]

Hi Pahup,

This is NOT fixed in AIR 15 released version or beta.

I just installed AIR 15.0.0.297 (beta) and see the same problem as on 15.0.0.249 (released version).

Note this only happens on Windows, Mac seems fine. That's Windows 7 64 bit.

I just added a comment to the bug report but am surprised to see someone at Adobe say its fixed internally, get several comments that it is not, but no response from Adobe....

Please fix this!  This is not a trivial corner case.

Thanks,

Dave