Ashley's Forum Posts

  • As noted in the manual for 'Invoke download':

    Downloading is a browser feature and depends on the browser UI. Note that mobile apps don't run in browsers (there is no address bar etc), so the download feature isn't available there.

    Construct doesn't have a way to write files to storage on mobile at the moment. But you can probably use the Share plugin instead to send the screenshot to another app. The Taking screenshots example shows how to do that.

  • I'm not sure exactly what you're doing based on that description, but a common mistake is to use ViewportWidth("Layer") / 2 for the middle of the screen. That's incorrect, it just gives you half the viewport width, which doesn't take in to account scrolling. The middle of the viewport is (ViewportLeft("Layer") + ViewportRight("Layer")) / 2.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I don't know, it seems tricky, as it stands the engine could assign UIDs to other objects so they're already in use when you try to recreate other objects again. Are you sure there isn't a better way to solve this?

  • You can't put binary in text formats. JSON is a text format, so you have no choice but to use base64.

    You don't need to use JS code for that: you can load the blob URL in to a Binary Data object with AJAX, and then get base64 from Binary Data.

  • I have no idea what the Twitch extension is trying to do. But something you might want to check is Construct 3's worker mode. It now runs in a Web Worker by default for performance reasons. This also means if you just put a tag in the main document it won't run in the context of the runtime.

  • As you do on desktop, double-tap to edit the image/animations of an object. Then the different animation panes are available by swiping in from the side, same as with the normal panes.

  • Tick the "Play in background" property of the Audio object.

  • When you tab away from the game, the game is suspended (paused) to save battery life and system resources. It shouldn't affect wait timing though.

  • Construct switched to WKWebView years ago. We already set Cordova builds to use WKWebView only as well, to make sure Cordova removes all references to UIWebView.

    There may still be certain addons that reference UIWebView. (They don't even need to actually use it, the message appears to be shown for anything that merely contains references to UIWebView.) It's difficult to help further without knowing which addons these are though.

  • I'm afraid large projects are in general impossible to debug. The bug report guidelines covers a way to reduce a large project if you can't reproduce it in a new project.

  • It's impossible to do anything about bugs unless you file them following all the guidelines. We need all that information to be able to investigate.

  • It's a very common mistake that people make if they don't understand why memory usage is important. People can and do make things like several colossal image tiles, or a sprite with 100 animation frames which are 1024x1024 (which uses nearly half a gigabyte of memory alone), etc. Based on years of seeing things like this, it would be my first suspicion; next up I'd suspect a GPU driver bug since those are pretty common too.

    For the record, neither your events nor Construct can typically crash the entire app. That means either out of memory (my first guess) or native code crashed (probably the driver, my second guess). Neither is actually Construct's fault. But really we can only guess based on the limited information provided - dop2000 is right that the only way to properly diagnose this would be to check LogCat, but often issues like this only happen with other people's devices, so you don't immediately have a way to test that, so you have to resort to guessing like this.

  • It's best to look up the device specification. You can try the DeviceMemory expression in the Platform Info object, but it's rounded for privacy reasons and not always supported. There's no way to check available memory either, those cover total memory.

  • A recent update to the Turkish translation has resulted in 113 problems. The list is available here: https://www.dropbox.com/s/m71bmt1r7cjlv65/tr-tr-2020-03-30.txt?dl=0

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

    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.

  • Check the memory usage. If your app needs loads of memory, devices without enough memory will crash.