note 10.1 tablet 2014 edition and noticed a little lag but the game is playable

Well, this device is too powerful to lag, guess you are using Fullscreen Quality - High Quality, your game renders in note's 2560x1600 resolution, that's too much. Use 1280x720 window size with low quality, you don't see the difference, but you see fps improve.

Egyptoon i tried my game on nexus 5 and galaxy s4, no lags, today i'll try my game on galaxy s3 and note 10.1(1st gen), i got a feeling that on a gpu-blacklisted devices cw10 start to perform poorly because of higher cpu-loading than with cw7.

I tested both versions and both runned very well in my smartphone.

Then, it is not a Crosswalk problem, maybe a possible incompatibility with your device.

Crosswalk 10 poor performance issue is already confirmed by intel team, they are informed and already working for a fix, i attached a link to the intel's investigation thread above.

Glad to hear that you don't experience any performance problems with cw10, i don't experience them too, but in intel xdk thread there's almost 30 pages of posts of other people about how poorly cw10 performs. Even if it's a simple device incompatibility, it means that cw10 is incompatible with too many devices.

Hm, now i think that it's probably by design, well anyway i'll leave this report here for your decision Ashley, and i'm sorry if it's not a bug.

And i reuploaded a .capx

Problem Description

If with asm.js you set the object's property "Collision Mask" to "Circle", "Is Overlapping" or "On Collision" conditions are not triggering because this collision mask is bigger than object's bounding box, so if i set object's collision polygons (in image editor) to bounding box (or i can set anything else), it is impossible for that object to collide with other objects with that polygons, because they just cannot reach other objects with that collision mask. In box2d this mask is little less than in asm.js and at least while the ball is rolling, the Is Overlapping always triggers.

Attach a Capx

[attachment=0:14j1x9gn][/attachment:14j1x9gn]

Description of Capx

A layout with a ball object and ground object with physics (asm.js), event sheet with events - If ball is overlapping ground set text to yeah, else set text to nope, and Is in touch event that applies little torque to ball. So if you touch or hold mouse buttons in preview the ball will roll.

Steps to Reproduce Bug

• Open project, start preview, let the ball hit the ground.
• Notice that Is Overlapping condition is not triggering
• Touch the layout or hold mouse buttons, the ball will roll, see, Is Overlapping is triggering as it starts to roll, but sometimes for a half of second it is not triggering while the ball rolling, i guess this is because when ball's angle = 0 or 90 or 180 or 270 its bounding box cannot reach the ground to overlap it.

Observed Result

Is Overlapping or On collision conditions are not triggering, when they should because collision mask is bigger than object's bounding box.

Expected Result

If circle object is on the ground, Is Overlapping triggers.

Affected Browsers

• Chrome: (YES)
• FireFox: (YES)
• Internet Explorer: (YES)

Operating System and Service Pack

Windows 7, 8.1 64bit latest drivers.

Construct 2 Version ID

r199

Problem Description

Affects only editor, if i zoom out enough in editor, 9 patch displays wrong (see screenshot), zoom in and it's okay. I hope i'm not the only one who have this, and i'm not sure that the problem is with my system, because i tried it on 3 different systems, iMac 2010 21inch with 1080p display and 32bit windows 7, MBPr 13 Late 2013 2560x1600 display and 64bit windows 7, and on pc with gtx660ti and 1080p display 64bit windows 8.1, latest drivers everywhere.

[attachment=0:chd5j45v][/attachment:chd5j45v]

Attach a Capx

[attachment=1:chd5j45v][/attachment:chd5j45v]

Description of Capx

Just a project with 9patch object inside.

Steps to Reproduce Bug

• Open .capx
• Zoom Out until you get the incorrect displaying result from screenshot
• Zoom In and everythings should back to normal.

Observed Result

9patch displays incorrectly on zoom out and back to normal on zoom in

Expected Result

9patch always displays correctly

Affected Browsers

• Chrome: (NO)
• FireFox: (NO)
• Internet Explorer: (NO)

Only in editor: (ye)

Operating System and Service Pack

Windows 7 32bit, 64bit, Windows 8.1 64 bit, 3 different machines, latest drivers.

Construct 2 Version ID

r199

Sisyphus

Thanks for your reply

can you please tell me when the fix can be available ? any workaround for now to save my game on google play store and get rid of this alert ? any update coming soon ?

Relax, google will not remove your game right now, and i'm not sure that they got somekind of timer, i'm sure if they will want to remove it, they contact you with a last warning or something. There's no workaround or fix yet, and i don't know when this stuff will be fixed, or if it will be fixed at all.

EstudioCelula3 — Come on guys, you can't search forums? Crosswalk 10 crappy performance is a known issue that intel's guys are trying to fix here. And open SSL in crosswalk 7 is broken, not because it used to scam people, 10 pages thread about openssl issue, it is also a known issue, intel wants everybody to update their crosswalk builds, but crosswalk 10 has very poor performance on many devices, but they are working on it.

You're HTML5+JS expert.

Hey guys, more news about cordova-ios 4.0.0 and wkwebview, official release dates (April 2015) and more LINK

Sisyphus i think your thinking about google play where you cant have apps more then 50MB without expansion files. C2 has no size limit

Nope, in my post above there's a rule from itunes connect developer guide that says that executable file must be less than 60mb, but if damjancd published bigger games, it looks like all exporters are not packing everything into executable. So the limit for ios is 4gb.

Is it possible that it is a problem with the Audio plugin again? All I changed/added was a new layout and audio.

It happens regularly on Chrome PC and Safari on iOS for me.

Just file a bug report with a .capx that reproduces the problem, and Ashley will investigate the reasons of the problem.