Ashley's Forum Posts

  • It's a bug in the Android Webview. Google need to fix it.

  • It sounds like this issue which we've been working on for a while. I think it's a bug in iOS, and it's proving difficult to work around.

  • I think the issue may be related to suspending the window (which also suspends the engine) and maybe also suspends that part that is supposed to refresh the service worker.

    Hmm, maybe that's related - does the issue only happen if you minimize or otherwise hide the preview window for an extended period of time?

    As with any issue, testing other browsers, and identifying the first affected Construct release, are useful additional details.

  • It sounds like a bug in iOS 14 that I reported last year. Apple say it's fixed, but their secrecy means they never say when things actually get released - I guess it may be fixed in one of the next few iOS updates.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'm afraid that until an actionable issue is filed, it's impossible to do anything. As far as I have seen from running some tests in Construct, everything is working fine.

  • It should not normally be possible to cause that error in Construct, because Construct won't let you switch to a runtime if it is not supported by some of the addons in your project.

    I would guess you have actually installed the wrong version of the Lite Tween addon which is incompatible with the last time you saved your project. You'll need to find the correct version. Beyond that third-party addons are outside of our control, so contact the addon developer for further help.

  • I saw this and thought it was worth checking whether there was some kind of synchronisation problem in worker mode, since the runtime runs in a separate thread to where the gamepad input is polled, and similar subtle problems have cropped up in other ways. I realised that it's possible for some input updates to be missed in worker mode, especially if the framerate is dropping, since the runtime could get out of sync with the input polling. I made some changes to guarantee "On button pressed" and "On button released" reliably get triggered and the change is in r235, so it should be working better there. (You can probably also work around it in the stable release by turning off worker mode.)

  • There shouldn't be any need to use old releases - the 'Open local project folder' option in the Chrome browser should be able to open any project folder saved with any prior version of Construct (desktop or browser).

    The project is probably corrupt. You may be able to see a more detailed error message if you press F12 and check the browser console. Beyond that it would be hard to help any further without a copy of the project.

  • We didn't remove it. I just checked and it's still there.

    It's only shown if the browser supports it, which is currently only Chromium-based browsers (Chrome, Edge, Opera...)

  • You do not have permission to view this post

  • As of r234, new projects default to using JavaScript Modules, which handle globals slightly differently. See Upgrading projects from classic scripts to modules.

  • It's definitely not a virus. It must be a false positive by MalwareBytes. I guess it's also possible that your system is infected, and it also infected the APK that you downloaded to your system.

    If you did a debug or unsigned APK export for testing, it is probably not trusted since it is missing the digital signature that verifies the author. You might need to enable some extra developer settings on your device to allow testing unsigned APKs.

  • (viewportright("HUD")-viewportleft("HUD"))/2

    The correct expression is:

    (viewportright("HUD") + viewportleft("HUD"))/2

    i.e. plus, not minus. You want the value half way between the two, not half the difference.

  • I don't believe we've changed anything to do with that for several months. Perhaps a browser update affected it.

  • I don't see much that we can do here: the APK signing tool is the official one by Google, we didn't make it, and the build server just runs that. If you use a third-party tool, we can't support that - any issues will need to be taken up with the respective developer. (As with addons, this is another reason why you should choose third-party tools carefully and make sure they are actively supported and maintained in case they cause any problems.)

    For general advice on building and signing Android apps, you can refer to Google's official documentation, such as Sign your app. You can also export Android Studio projects from Construct and continue to do building and signing with Android Studio, which Google's official guides also cover.