Ashley's Forum Posts

  • I can't reproduce any problem here following those steps. I tried doing "close all but this" on Layout 7 and again with Layout 12 and it worked fine. Based on the error message though I've added in an extra check for the next build, which might fix it.

  • This type of error is almost always caused by buggy third-party addons. Please check your addons and report whichever one causes this error to the developer.

  • The engine does not do more work when you add a family to an instance, so I don't know why this would happen. FWIW the measurements C3 provides are very approximate and based on timers, which can make them unreliable. For me the C3 debugger measured 20% CPU time, but making more accurate measurements revealed it to be more like 7%, so it's at least not as bad as it shows.

  • The reason we have bug report guidelines is because we need all that information to actually be able to help. In threads like these, all I can say is, I don't know either. The best thing to do is to figure out one specific action that you can repeat over and over and reproduce the issue as quickly as possible, and then file a bug based on that.

    In the past we've had vague threads like these popping up occasionally over years, and as soon as someone made a .capx that reproduced the issue directly, it was fixed in the next build. That's how big a difference it makes.

  • It's an interesting idea, but the API surface is huge, so would take a great deal of development time. Then I'm doubtful how much third-party use there will be anyway - will someone really work for months to add major new features? Also many of those things in your list would basically have to be built-in features anyway, for architectural reasons, so an editor API probably wouldn't be suitable for building them. (Some of them are in our long-term plans anyway.)

    We're currently working on drawing plugins, which just for that involves a large API surface, then we'll probably look in to custom importers so tools like Spriter/Spine can handle importing themselves. Beyond that I think we will focus on adding specific features that are definitely needed by a third-party addon, so we'll add things as needed from there.

  • Traditional desktop apps (i.e. not distributed via a store) generally all invent their own auto-update mechanism. So you have to come up with something yourself. One of the nice things about stores or web publishing is they solve this for you.

  • Yes, and UWP apps run using the Microsoft Edge browser engine, so UWP apps support the same features as Edge. Since Edge doesn't currently support it, multiplayer is simply not supported. You could use something like websockets instead which Edge does support, but they aren't so good for real-time games, and you'll have to write a server since it can't work peer-to-peer. Alternatively you could wait for Microsoft to add DataChannel support, but there's no sign of when that will happen.

  • FWIW, the limit is in your CPU circuitry, not Construct.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Browsers don't currently provide an API to do this, so it's not possible.

  • Edge doesn't support WebRTC DataChannels, so you can't use Multiplayer in Edge or UWP apps either.

  • The installer covers both the 32-bit and 64-bit versions. It asks you during installation which one you want to install. The default is to automatically detect it.

  • Thanks, should be fixed in the next build.

  • Closing, please see the bug report guidelines otherwise we can't investigate the problem.

  • Closing as it looks like this is an issue in the latest Windows 10 update.

  • This is currently by design. Touches on HTML elements are dispatched to those elements only, and not used by the runtime. Otherwise you get weird effects like clicking buttons fires touch/mouse click events which can cause unwanted events to run. For example a game might play a sound on every click and create an explosion by the mouse/touch, but have an OK button where they don't want that to happen when the button is clicked. This is what the current behavior is aimed at.

    As you've pointed out you can modify the style of elements yourself using the 'Set CSS style' action if you want to adjust this behavior.