[quote:ytlc7qaf]2: the engine is written in java

Can we please NOT mix up Java and Javascript?

To the original poster:

Buy.

The $500 thing is obviously targeted at bigger players and not indies.

I wonder if that's going to bite 'em in the ********* in the long run.

It sounds like you are using a continuous event like "is in touch" our "is touching object" instead of a one time trigger.

Can you post a bit of your code? Maybe a .capx with everything thrown out but one button, that produces the error.

Ashley Have you had a chance to file a bug against asm.js regarding this?

My only feeling is that xdk is slower.

It is slower. But you asked for the best way and it is.. it's not the fastest, but the best one overall with the least trouble.

A little side question: what kind of performance gains do you get there? Is it like 1000000 objects that are clogging the CPU? (it should not be a rendering issue, those are culled by themselves, if they are far away)

Depends entirely on the game and how well you optimized it.

That said, there are a lot of C2 games working quite well on mobile devices, you just have to do it right.

i still play Clash Of Clans and other games like that with no lag.

You cannot compare that. Clash of clans is a native game. C2 exports HTML5 games, that's like 50 more layers of abstraction Wrappers like XDK don't magically make a native game out of it, they just package a browser engine with it. It's still "just" a browser game.

The newer the tech, the less a problem this is. On modern phones you can make perfectly fine HTML5 games with Construct2 that that run at 60fps.

But not with an S2.

Unfortunately only the simplest of games will run on an S2 in "acceptable" quality. They won't run with full speed. The device is basically 2 generations too old for HTML5 stuff. Even on modern phones you have to optimize aggressively to avoid bad performance.

Are you testing exported APKs (via crosswalk or whatever) or are you testing on browsers? And if so: stock browsers? Samsung have been notorious for having all sorts of bugs within the stock browser, sound trouble among them.

They have also been known to not fix any of it, which has been a problem for years.

It was btw. quite common on old arcade machines to just slow everything down instead of skipping.. some shooters even used this as a feature (comparable to the "high precision movement" that some of the contemporary ones allow), if there was too much going on (bossfights or boss blowups) the clock would just run slower.

I also found graphicsgale to be quite a useful and nice piece software. No problems there..