Ashley's Forum Posts

  • AFAIK NW.js does not support Linux on ARM chips, and the Raspberry Pi uses an ARM chip. It only works on Intel-based chips such as those commonly found in PCs and laptops. Raspberry Pis come with Chromium though so web exports can be run in the browser.

    Also on Linux the name of the executable file is the name of your project ("Swimming" in this case).

  • OK, I can reproduce an issue saving a project folder. We'll probably issue a patch release for that tomorrow.

    In the mean time you can either roll back to r277, or clear recent projects in settings and use a different save option for the time being.

  • If you use thing.addEventListener("tick", callback), then the callback will only run if thing fires an event named "tick". Otherwise, nothing happens.

    Check the documentation for which objects fire which events. In Construct, "tick" is only fired by runtime.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Instances don't have a "tick" event.

  • It works fine for me. Are you sure it's not a third-party addon? (Try testing in a private browsing window to check)

    Can you share the platform information too? That gives a summary of the setup you're using.

  • I can only repeat that if there is a problem in iOS, and you actually want it to be fixed, the fastest thing is to cut us out the process and go direct to Apple. Try contacting their developer evangelists yourself if you think that will help. In my long experience though, the best way is to file a good bug report directly with Apple. Anything else is just beating around the bush.

  • Posting binary data (as in your last screenshot) means the entire posted body is a single block of binary data. The server needs to handle this and not try to parse a string of parameters or anything like that.

    That means you can't put extra string parameters in the post data, but you can put them in the query string.

  • My standard response is: don't do that, it will waste the device battery. Why do you need to send a message on a regular basis? If you need to do something like simulate the passage of real-world time in a game, then you can just measure the time between the app suspending and resuming, and simulate that much time passing, allowing the device to save battery in between.

  • Just remove your test addon from the Addon Manager.

  • The overhead of the event engine likely makes the difference negligible.

  • But has Scirra/Construct filed or notified Apple of this problem as an engine developer?

    So far I don't believe I've been able to reproduce the problem myself. We cannot file a bug report if we can't reproduce the problem - if it looks like everything works, how can we tell Apple it's broken? Getting us to reproduce the problem is just an unnecessary extra step anyway, as all we'd do is forward the issue on to Apple. So it will be quicker to cut us out and report the problem directly.

    Does Scirra have a contact at Apple or relationship they can follow up on?

    Absolutely not. Apple are notoriously secretive to the point of absurdity, e.g. they mark bugs as fixed but can't tell us when the fix will ship, only saying "Apple does not comment on future releases" as a standard response. If Apple made anyone available to us, we'd definitely talk to them about such issues, but they do not make any such person available nor do they appear to have a culture that would be open to such an idea.

    So in short, you're probably best off reporting iOS regressions directly to Apple. No software is perfect, all platforms have bugs and occasional regressions - this really is business as usual in the software world. And if people keep trying to pressure us to do something about it when it's impossible for us to do anything about it, it will only make it take longer to solve the problem. This has happened before in other ways and to be honest it's pretty frustrating for us; I know you all just want it to be fixed but it is genuinely out of our hands and we have few options - Apple need to fix it and if you keep telling us to do something about it then you'll get nowhere, because so far there's nothing we can do.

  • I already prototyped something similar but it's blocked on a bug in Safari that causes it to break all rendering.

  • If you run in to a problem please file an issue following all the guidelines, as we need all that information to be able to help.

  • Make sure you specify "scale outer" again in the Request fullscreen action. It lets you choose a different fullscreen mode when entering the browser fullscreen mode, and if you want to keep the same setting you must set it again there.

  • Use the Post binary to URL action of the AJAX object. Pick your Binary Data object, and its data will be posted as binary to the server.