Ashley's Forum Posts

  • How are you exporting/testing? Have you tried Chrome for Android?

  • Yeah, according to GSMArena: ZTE Open C sensors includes just "Accelerometer"

    Compared to the Nexus 5, which lists for sensors: "Accelerometer, gyro, proximity, compass, barometer"

    The ZTE Open C has no gyroscope!

  • Does the ZTE Open C actually come with a gyroscope? I think Firefox OS supports it, but if the device doesn't have it, then it can't report any values for it. It's a budget device so they might have cut the gyroscope as a way to lower the cost of the device.

  • Pub Center support is in the next build, but even Microsoft don't appear to support it on WP8.1 yet, so I'm not sure what to do about that.

    IAP, back button, and suspend should work identically to other platforms. I'm not sure what other information you're looking for.

  • Without knowing anything more about your game or your profiler measurements, all I can direct you to is performance tips.

  • You should not use this plugin any more. Use our official universal exporter for WP8.1+. It should support all of those features. The HTML5 support is so far better with the WP8.1 update that it's probably not worth the extra hassle getting WP8.0 support.

  • I have a blog post covering the performance differences coming up, but in short I did not measure any significant performance difference in either CocoonJS or Ejecta between iOS 7.1 and iOS 8, but PhoneGap and Safari have seen some big improvements, and a future PhoneGap update should bring performance up to Safari level.

  • Kali - try the latest beta, we've made some fixes to do with audio preloading lately.

    Also since the OP is fairly old now, preloading sound effects is now redundant in the latest builds if you enable 'Preload sounds' in project properties.

  • Shadertoy has lots of shaders which involve ******** intensive calculations for the most impressive effects. If a gaming laptop managed 10 FPS, then 5 FPS on a phone is actually, like, super impressive.

    I'm about to do a blog post with lots of (more realistic) performance tests for iOS 8 so stay tuned!

  • It's not possible. The user presumably knows where their browser downloads files to, though. Most browsers also offer to open the file directly or its folder location once downloaded.

  • The only bug construct 2 has at the moment is the double canvas bug in older samsung devices. It wasn't there in R168 so an update in R169 might have caused it to happen.

    Well if it doesn't happen anywhere else it already sounds very likely to be a browser bug, but perhaps we can still work around it, especially if you can track it down to a particular release number that first broke it. Is there a bug report for that in the bugs forum? There ought to be a thread so we can track the specific issue over time, and maybe get some help from other users in reproducing it and narrowing it down to specific devices/Android OS versions.

  • Closing as probable glitch in the matrix.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Cordova basically is PhoneGap. One's the open source name and the other is Adobe's name.

    We currently only officially support Crosswalk on the XDK, but since it's free for the other platforms as well, hopefully we can add support for them as well soon.

  • Why does it matter?

  • I think any speed up from spritesheeting on preview would be more than offset by the time spent building the spritesheets. Previewing is local so there is virtually zero latency and unlimited bandwidth, so I doubt there is much extra cost from having to make extra HTTP requests, plus most browsers can decode images in parallel on all CPU cores.

    I'm not sure what you're seeing when you talk about slow preview: if you're seeing a progress bar in the Construct 2 editor, then it's most likely building the JSON data for the project, but if you're seeing a progress bar in the browser itself, then it's most likely downloading and decoding images (as well as sounds if you have 'preload sounds' enabled).

    I find Node-webkit specifically can take a couple of seconds to start up, and you can avoid that by treating it like a browser - leave it open and press preview again in C2, and it will refresh the same instance of node-webkit rather than starting a new process.