Ashley's Forum Posts

  • In the near future, all browsers on all systems will impose autoplay restrictions. Construct already handles this automatically. So I don't see any reason to change anything.

  • Please file any issues on the issue tracker.

  • But it is possible, to play without user input

    It's not, with the latest versions of browsers. The change is still in progress though: any that do allow it, will shortly block it as well. So anything you do that can play automatically in certain cases, will soon be broken, so is a waste of time.

  • 1. The idea is all the gameplay is 2D, but some of the graphics can be Z elevated. So collisions will still work as if everything is on Z=0.

    2. There's no concept of depth, and I don't think it makes sense to add it for 2D objects with Z elevation - they essentially have no thickness.

    3. Due to the first answer (all gameplay is 2D), we don't have any plans to update behaviors to use Z at this time.

  • The C3 runtime is still very new - if you file any issues we'll try to fix anything that's not working right. I'm also happy to profile projects that aren't performing well and figure out if there's something inefficient in the engine.

  • You added more things than the original suggestion covered - please try to avoid that, it confuses the purpose of the suggestion and makes it harder to track, any different ideas to the original post should be posted separately. That suggestion will be treated as referring to the original description only.

    FYI I can't see any reason to support getSupportedAPIs(), since you can't do anything with them from events. If there are features which are only sometimes supported, we'd add separate conditions to cover them, but AFAIK there are no such features yet.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Can you put that on the suggestion platform? That's the kind of helpful detail that helps explain what the suggestion is aimed at.

  • It's not rotatable mainly because some features involve a ton of really complicated transforms (e.g. pasting an object with effects), and adding rotation to this makes it even more complicated. It's already been tough to get right, and there are still some outstanding bugs (please file them if not already on the tracker), with pasting without rotation...

  • You do not have permission to view this post

  • Read the error message! It tells you that

    On Android - make sure the Android System Webview is up-to-date

    On iOS - the simulator is not supported, test on a real device

  • It's difficult to interpret a suggestion that just says to expose a JavaScript API. It's not a good user experience and goes against Construct's design to just let users call JavaScript APIs directly, it's always wrapped in higher-level conditions, actions and expressions. If the suggestion doesn't specify how that is done then it's not clear how to go about it, especially when these are complex APIs which cover a wide range of features, some which probably need to be supported, and some which probably aren't feasible to support in Construct (e.g. bots). So it's still not at all clear to me which parts are necessary and how it would actually look and work in events, hence 'need more detail'.

  • You already only need to write a few lines of GLSL to make a custom shader.

    Time is by far our most limited resource, and writing a whole shader editor to wrap this for you would be a huge job for a small, niche benefit.

  • Isn't this what WebGL shader effects do?

  • There is only ever 1 layout to be saved. Do you mean 1 layer? Why do you only want to save 1 layer?

  • This isn't a problem with Construct, it's iOS has buggy iframe sizing. See the tutorial Publishing to the web section on "embedding" for the workaround (scrolling="no" noresize="noresize").