It wasn't a performance improvement; it was broken (didn't work at all) and now it works again.
Huge tiles are bad, and lots of objects on-screen are bad as well. So if you have lots of objects spread out over a long level, without too many being on-screen at once, you should be fine.
Develop games in your browser. Powerful, performant & highly capable.
I tried and couldn't reproduce on an iPad 2 with iOS 6. Did you check that?
Closing: in computer graphics, you cannot guarantee seamless display of adjacent images unless you use both pixel rounding and letterbox integer scale (normal letterbox scale will result in floating point scale levels, which can cause seams). I'm not sure why Chrome manages to display it without seams, but you still can't rely on it to be seamless on all systems without those settings. I noticed Internet Explorer seams in the browser too without those settings.
The manual already made this clear, but I've updated the description in the object for the next build too.
Ah, I just noticed the autocomplete is case sensitive. The system expression is lowercase ("random") and if you make a global variable with uppercase ("Random2"), and you type an uppercase R, it will prefer to autocomplete the match with the same case (in this case the global variable). I've turned off case sensitivity in autocomplete for the next build.
I tried adding two global variables called random2 and random3 and I still couldn't get the problem to occur, if I type "random(" I get "random(". Closing, please provide a .capx if you want this to be investigated further (this is why we always ask for a .capx from the start...!)
Xantomen - only iOS 6+ supports playing sound in the browser. I'm sure the Android problems are browser limitations too rather than Construct 2 bugs, since our audio system works very well everywhere else including on iOS 6+. Chrome for Android will be getting the Web Audio API soon too which hopefully will fix this on Android too.
Very strange, music ought to have no effect at all on pathfinding!
I can't reproduce the problem in Firefox, only Chrome, but you said you could reproduce in Firefox. Are you sure about that?
Closing, no .capx provided. Please follow the bug report guidelines.
Should be fixed in the next build (will do a .2 update shortly)
This is not a bug, your events are not multitouch aware. If there are two touches, Touch.Y or Touch.ID could return for either of them, which is not what you want but what your events say.
Here's a fixed version which is multi-touch aware: https://dl.dropboxusercontent.com/u/15217362/fixedtouchslider.capx
Closing as not a bug.
I can't reproduce any problem with either method on an iPad running iOS 6. I think this is a problem with Chrome for Android. You should probably report the issue to Google.
Should be fixed in next build.
Thanks, should be fixed in the next build.