Ashley's Forum Posts

  • Remove from the resulting folder files intelxdk.config.additions.xml and Newproject.xdk

    In this step, you remove the files that specify to use WKWebView. So you are effectively disabling WKWebView yourself. So it should not be surprising the resulting app does not use WKWebView! If you try to add the settings yourself afterwards, it's possible you made a mistake. There's no reason to do that anyway, C2 exports all the necessary settings to use WKWebView.

    Closing as not a bug.

  • I previously asked for a .capx that reproduces the issue without any third-party plugins, as per the usual bug report requirements to make it as likely as possible that we can resolve the issue. As far as I can see, nobody has provided one, so there is very little we can do until then.

  • I have no idea how this could happen. The OS should keep separate applications separated, unless TeamViewer tries to reach out to other applications and modify them in some way, in which case it's a bug with TeamViewer.

  • Sorry, not much we can do without a .capx and steps to reproduce - and even then it might be a permissions issue with the folder you're trying to save to, or a conflict with another piece of software trying to sync the files or something like that. (We've had trouble with Dropbox getting in the way of saves before.)

  • Closing as it's a Chrome issue as pointed out previously. Star the issue and post in it to try and bring attention back to it.

    Moving the audio to the sounds folder uses the Web Audio API instead which can loop seamlessly. The only disadvantage is it stores the whole track decompressed in memory, which isn't great for long tracks, but for short ones it's fine.

  • Dang, this results in uncatchable exceptions in the underlying library. There's not an obvious way for us to handle this. I filed a bug for it here: https://github.com/localForage/localForage/issues/647

  • Should be fixed in the next build. So long as you grab a handle that only resizes on one axis, then the snap is only applied to that axis. If you grab a corner it still resizes both axes like it does already.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Sorry, nothing we can do unless you follow the bug report guidelines. You could provide the spritesheet image you are importing and the exact steps for how you import it and the settings you choose.

  • Should be fixed in the next build.

  • I am not sure which link you are talking about. I tried a few and they all worked. Providing a screenshot or more specific description would help.

  • Closing as won't fix. The solid behavior is not meant to be used with movements. When you move a solid like that, you're effectively teleporting a solid in to another movement, which is set to not overlap solids. When the behavior finds itself wedged inside a solid it's not supposed to be in, it resorts to a sort of emergency "get me out of here" avoidance which looks for a nearby space and positions the object there instead. That doesn't always move in a predictable direction, hence the inconsistent direction. So this is actually working correctly, given the design of the engine.

  • The key code is provided by the browser, not Construct 2, so it's not something we can fix. I'd guess it's working correctly anyway - I suppose if you change keyboard, the key codes are the same, even if the key labels are different.

  • Closing as won't fix - I'm afraid there's not much we can do about this. All browsers and OSs have their own text rendering engines, and they are all slightly different. You can't rely on an exact text representation. You have to design games to allow a bit of variation in the text rendering.

  • Closing, please see the bug report guidelines. This project has 393 events. In all likelihood you just made a mistake in your events. The Function object is mature and well-tested. If you think there is a bug with it, try to reproduce it in a new empty project.

  • If you export with Crosswalk it bundles the Chromium browser engine in the APK which is ~17mb. If you don't want it, you can set the minimum Android version to 5.0+ and it will exclude it. If you have any other issues, please file a new report following all the bug report guidelines, otherwise nobody can help you.