Ashley's Forum Posts

  • It's not supported yet.

  • What browser are you running? Chrome for Android is one of the only mobile browsers that supports WebRTC right now.

  • PhoneGap will work great from iOS 8 and Android L. Previously iOS and Android's webviews were very slow; from these releases they will be GPU-accelerated with WebGL support and full-speed Javascript. See https://www.scirra.com/blog/146/webgl-arrives-on-ios-8-and-more.

    Ejecta will more or less be obsolete after iOS 8; it will still cover older versions of iOS, but since iOS updates tend to reach about 90% distribution pretty quickly, I think it would be wise to simply target iOS 8+ only and enjoy the far better compatibility with a real browser engine.

    Crosswalk will still be useful for a while after Android L's release, since Android updates take such a long time to propagate. Until Android L+ reaches vast majority marketshare (like Android 4+ is only just achieving recently), Crosswalk will be the way to use a real browser engine to reach all Android 4+ systems. Hopefully their ads+iap support will come soon, they tell me it's effectively ready but needs to sort out some legal issues (don't know what those might be).

    Eventually though in the long term PhoneGap will basically cover both platforms with excellent performance and support.

    IAP support is already coded in for Ejecta, if there's a problem with it then please file a bug report!

  • It is far easier for us to actually be helpful if all messages go to the same places. The forum and the support email addresses should be where you send messages, not to developers themselves directly. For example people would sometimes previously PM me issues about the website; that's actually Tom's job, and it is awkward to deal with that by PM. Or they would ask beginner questions, which are better off in the beginner's forum, where it is also public and searchable and possibly useful to other users. To avoid these problems we have disabled PMs for all Scirra staff members.

  • 1) The name is what it appends numbers after if the room is full. So if you specify "myroom" and "myroom" is full, it will continue to try "myroom2" and so on. You have to specify a base name so you don't accidentally try to use rooms being used for other purposes. You might for example want to have 2 different types of room that can be auto-joined.

    2) What is it exactly that you want to manage?

    3) Yes, that's what auto-joining rooms is for.

  • Issue #1: should be fixed in next build, thanks.

    Issue #2: this is not a bug, CocoonJS simply does not support the Twitter button I'm afraid.

  • I'm afraid the project cannot be recovered, it is entirely missing all animations and all image files. Hopefully you had Construct 2 set up to save backups in several places.

    There's nothing we can do about this unless you can reproduce it or provide at least some kind of hint as to what caused it. I cannot conceive of any reason Construct 2 would delete all that data - we have coded the save routines very carefully specifically to avoid this kind of problem.

  • Closing, please follow the bug report guidelines.

  • Closing, I'm afraid we cannot do anything about reports unless they include a way to reproduce the problem, or at least some kind of hint as to what might have caused it. As it is you've just submitted a project with a file missing. The workaround TELLES0808 described should fix it (.capx files are really just folder projects in a renamed .zip file).

    caplocks1111 - please do not respond to bug threads unless you have relevant information to add - general system maintenance tools are probably not related to this issue.

  • If you don't want the overhead of node-webkit, remember you can always publish to the web and the user can play it with whichever browser they happen to have installed already.

    • Post link icon

    Closing, please only post in english.

  • Well, your screenshots show the window size has changed, so presumably you have not set up support for multiple screen sizes properly.

  • We currently maintain support for 3 different physics engines and it makes it very difficult to make changes while maintaining compatibility. If we dropped support for CocoonJS physics it would be easier, but then that would probably upset everyone using CocoonJS.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Closing, please follow the bug report guidelines. If the problem is with Newgrounds' site, report it to them instead.

  • That's not an officially supported exporter. You should try using one of the officially supported ones for Android devices (Crosswalk or CocoonJS).