Ashley's Forum Posts

  • It does not boost performance. Normally frames are scheduled once per display refresh. There's no point generating frames faster than the display hardware updates - they won't be seen, and it just wastes power.

    Unlimited framerate mode instead schedules frames as fast as possible. It's for performance testing. However since it uses loads of power generating frames that will never be seen, it will needlessly drain the battery on laptops and mobiles, so you should never publish an actual game using that mode.

    That's pretty much all there is to it.

  • Construct 3 already uses a WebAssembly build of OptiPNG to optimise your images on export (if you enable image recompression). This can also do automatic palette reduction to smaller 8-bit PNGs as well - particularly nice for retro style games with low color counts.

    compresspng.com does not seem to include any details about what it really does, but I would guess it is using lossy compression. A tool like Construct can't in general use lossy compression since it will degrade artwork, and I think most artists will want their art quality preserved.

  • In both cases, as per the original announcement, both C2 and the C2 runtime in C3 are only being supported with "essential bug fixes and compatibility updates". Minor or non-essential reports will no longer be investigated. Basically that means if some browser update happened that broke all Construct 2 games, we'd fix it, but other than that we won't be doing any further work on it. Since this appears to fall in the category of non-essential, we won't fix anything involving C2 or the C2 runtime if you file an issue for it.

    In other words, since February 2020, C2 and the C2 runtime are not actively supported, they're just being kept alive with essential maintenance. The purpose of the delay until July 2021 is merely to give you plenty of time to upgrade to C3 with the C3 runtime, with the confidence C2 won't suddenly stop working before then.

  • There's not a lot of value in fixing bugs in a codebase that will be removed in a few months time. I'd much rather everyone just switched over to the C3 runtime. The whole goal of retiring the C2 runtime is to eliminate the maintenance burden of having to work on it.

  • Bug fixes filed in the C3 runtime usually aren't backported to the C2 runtime, so it may well be that there are still bugs in the C2 runtime that were fixed in the C3 runtime.

    It shouldn't matter, since the C2 runtime is being retired in July. You really should stop using it as soon as you can.

  • FYI, the tilemap object was never designed to be used with 1x1 tiles. It was designed for each tile to be a reasonably sized independent image.

    Using C3, the C3 runtime is faster than the C2 runtime. It appears to sit idle most of the time, but when you click, the C2 runtime spikes the CPU usage up to 30%, but the C3 runtime only spikes the CPU usage up to 7%. So it looks like the C3 runtime is about 4x faster.

  • We can already publish the game with unlimited frame rate mode. I read on the forum that even someone is using it to make sure that the app run smoother in all devices.

    A strong warning is shown on export if you try to do that, because you should never publish a game with that mode.

    What you are suggesting is an incredibly ugly hack that will not only prove very difficult to actually usefully apply, but could well make things even worse. It really is the wrong direction to go in. Just because you can doesn't mean you should.

  • I think it's more likely that what you propose will make things worse, not better. Either the developers or the players will be likely to mis-configure the option, and then the situation is worse than it was to begin with.

  • A recent update to the Turkish translation has increased the number of problems to 150. The list is available here: https://www.dropbox.com/s/hfjvrogr9vcwvtl/tr-TR-2020-11-10.txt?dl=0

    They will all need to be corrected before the in-progress translation in the Construct editor is updated again.

    The translation currently has many systematic mistakes characteristic of using machine translation. Please do not use machine translation, like Google Translate, when translating Construct 3. It is an inappropriate tool that results in poor quality translations. These translations will then fail later quality reviews and have to be re-done, resulting in wasted effort and taking longer before the translation is ready. Translation rewards will NOT be issued for use of machine translation.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The Polish translation currently has 60 problems. This is an increase of 50 problems since August 2019. The list is available here: https://www.dropbox.com/s/6zp6r2hhcnneru3/pl-PL-2020-11-10.txt?dl=0

    They will all need to be corrected before the in-progress translation in the Construct editor is updated again. It has not been updated for some time now.

  • The latest version of Cordova increased the minimum Android version to 5.1. Older versions are no longer supported. According to StatCounter, less than 1% of devices still use Android 5.0.

  • If you have trouble with displaying AdMob ads you should contact AdMob - that part isn't handled by Construct.

  • Ashley, would you consider to allow us to switch the framerate mode in realtime?

    No, that's not a solution, it's just a hack which only raises further difficult problems, like: how do you know when to turn it on? There are thousands of different devices out there with different hardware and different software configurations. And if you get it wrong, you'll drain the device battery, which is a worse problem than you started with.

  • You'd need to file a new issue following all the guidelines if you want that to be investigated, because the previous issue was fixed.

  • See this thread covering the same problem. It looks like an AdMob bug, your best bet is to post in the AdMob SDK forum asking for help.