9 patch object appears blurry on export to mobile

Problem Description

When you export a pixel based game using say - the retro template, if you ever use a 9 patch object, it becomes blurry featuring AA and other artefacting.

This is almost identical to a bug I reported a while back: https://www.scirra.com/forum/viewtopic.php?f=152&t=100468

That bug was fixed, but seemingly not for iOS export.

Images:

http://sean-noonan.com/development/dev_noonanrun/construct_ios_fukt_1.png

http://sean-noonan.com/development/dev_noonanrun/construct_ios_fukt_2.png

http://sean-noonan.com/development/dev_noonanrun/construct_ios_fukt_3.png

Attach a Capx

https://dl.dropboxusercontent.com/u/7282045/9patch_iOS_export.capx

Description of Capx

Just export the project to CocoonJS or Ejecta and run on an iOS device

Steps to Reproduce Bug

• Export the project using CocoonJS
• Deploy it to the CocoonJS app on an iOS device via iTunes
• Run it!

Observed Result

9 Patch looks blurry

Expected Result

9 Patch has the same sharpness as the tiled and sprite objects

Affected Platforms

• iOS export CocoonjS: (YES)
• iOS export Ejecta: (YES)

Operating System and Service Pack

Windows 7 SP1 (problem witnessed on iPhone 5 and iPad 2)

Construct 2 Version ID

Release 178

Your screenshots are different to the .capx you have provided. Can you confirm that the problem occurs with the given .capx? It did not reproduce in iOS Safari or Android Chrome. Also the webgl/canvas2d setting may also affect it, does it happen with WebGL mode?

I would say this is likely to be Ejecta/CocoonJS issues, since if it works in all other platforms/browsers then it suggests our code is in fact correct.

Reproduced exporting to CocoonJS

Oh and this is how it looks with WebGL disabled...

Oh, I know what this is: the middle (tiling) patch is not power of two. Since you have 1px borders, the middle patch ends up 30x30, and WebGL can currently only tile power-of-two textures, so it will have to stretch the middle patch to 32x32 to tile it which affects the display quality.

There's not much we can do about this - hopefully WebGL 2 will fix it since it has non-power-of-two texture support.

Even though it's fine using WebGL in a browser?

I assume when the new iOS is rolled out for everyone, this will be less of an issue?