Ashley's Forum Posts

  • The icons can be any size, you just need to make sure the adaptive foreground and background icons are the same size. As for what icon sizes and types to use, that's not up to Construct - refer to the Android guides for that.

  • What goes wrong? I would guess you are running in to the Cordova issue that needs to be fixed.

  • In theory the APK and browser run the same game with the same browser engine (Chromium), so there shouldn't be any meaningful difference between them.

    OS-level memory measurements are surprisingly complicated and nuanced, so it may be that you're looking at misleading measurements and the memory usage is actually the same. Chrome is a multi-process browser, so it may be that you're looking at the memory usage for a single tab, excluding the rest of the browser. Or maybe the browser is already loaded at the system level and opening a new tab only uses a bit more memory, but opening the APK uses an entirely new instance of the browser engine, increasing the memory usage more even though they both use the same overall amount of memory. So you should probably force-quit Chrome before making any comparisons, and be clear about how exactly you're making these memory measurements.

  • If you request URLs at runtime in your app, the server response may be telling the browser engine to cache the response in case it needs to request the same URL in future. So you might be able to avoid these resources being saved to the cache in the first place by adjusting the server HTTP response. For example if you add Cache-Control: no-store that will tell the browser engine not to save the response in the cache. However the flip-side is it then means every single time it requests that URL it will go to the server repeatedly instead of using the cache.

  • Every plugin request requires a full security review to make sure there is no risk to the build service, and we're a small team with limited resources. Please be patient. Also paying a small amount will make the problem worse, since administrating one-off payments manually is a significant amount of additional work.

    You can also build with any Cordova plugins by doing your own offline build with the Cordova CLI. So you don't need to wait for us to update the build service and approve plugins. If you're on a deadline, just do your own build.

    Developers should also post any requests well ahead of time. For example if you know you'll need a plugin allowed in 3 months time, you can file the request immediately and it should be ready in time. If you leave it until the last minute and we're busy at the time you make the request, then you'll needlessly face a delay.

  • It's pretty simple: you just need two same-sized images, and set one to the adaptive background, and the other one to adaptive foreground.

    However sometimes the build fails due to a Cordova bug. I've reported it to the Cordova developers, they'll need to fix that.

  • Most exports happen locally and so don't rely heavily on the Internet connection. When you build APKs it sends it to our build service, so you will need a reliable Internet connection for the duration of the upload, build and subsequent download.

    You can also do your own builds offline with the Cordova CLI.

  • I just tried a debug APK build and it worked fine. Are you sure your Internet connection is working reliably?

  • Please see the FAQ:

    Why haven't you responded to my bug report yet?

    We do look at every report, but developer and release schedules mean we may not get round to it immediately. Please allow a few weeks for it to be investigated. If you are waiting, you can improve the chance it is resolved when a developer does get round to it by carefully reviewing these guidelines and providing as much useful information about the problem as possible. If you are missing anything, you may end up waiting a few weeks for a reply simply asking for the missing information, and then you're back to waiting again.

    Note the assignment isn't particularly important. It just means we decided who should fix it. It doesn't represent the progress of the actual fix in any significant way.

  • editor.construct.net serves the latest stable release.

    editor.construct.net/beta serves the latest beta release.

  • Look at the releases page. There are newer beta releases. Every couple of months the latest update is transferred to a stable update, and then a new beta cycle begins again.

  • You should always use feature detection (in this case "is speech recognition supported") instead of browser detection. If you only enable a feature in one browser, you will needlessly block it from working in other browsers, including if other browsers add support for it in future.

  • There is no event named "onstartoflayout" in scripting. See the runtime events "beforeprojectstart" and "afterprojectstart", or the layout events "beforelayoutstart" and "afterlayoutstart".

  • I just tried it and it seems to be working fine. Are you sure your Internet connection is working?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's interesting to hear about HTML5 games that end up on consoles, even if they're not using Construct. However having a look at their blog, it sounds like they more or less ended up porting the game to standard native technology (e.g. porting/rewriting in C++), which is already the de facto way to port HTML5 games to console. There are already companies that port Construct games to console this way, such as Chowdren.

    Also note the topic of Construct support on Switch has been discussed to death already and I'd prefer to avoid going through that all again in another thread. The current situation is Construct has built-in support for Xbox One (via UWP export), and for PS4/Switch you have to find a publisher who can do a port for you. Unfortunately as I've described many times in the past, it's very difficult to improve on that. The best approach is to keep asking Sony and Nintendo for support for HTML5 games.