Ashley's Forum Posts

  • It's always easier to help with an example project. Without one, I can only say it sounds like your timescale is far, far too high - 50x or 100x are both extreme values that the engine is not designed to handle. So, don't do that.

    • Post link icon

    This is a 2-year-old thread about a topic that's been done to death so closing. Please don't bump old threads, especially controversial ones, since it could be misconstrued as intending to create controversy which is against the Forum & Community guidelines.

  • If you're ever unsure just look in the About dialog - it tells you what version you're using there.

    The update system is designed for the common use case of moving between stable releases. I don't think using beta releases in a classroom environment is a common use case or something we should be optimising the update system for. So I'm not really sure what could be done about this.

    • Post link icon

    The main problem with multiple games with lots of players, is the bandwidth requirement increases exponentially with the number of players. This affects all kinds of multiplayer games and is a difficult design problem to solve regardless of the technology involved.

  • Are you using beta versions in a classroom? I wouldn't recommend that, they can be pretty buggy sometimes. If you just stick to stable releases, isn't it straightforward?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Unfortunately Construct can't change installed apps for you. It's just like creating a bookmark - web pages don't have the power to alter the URL of the bookmark, you just have to bookmark the right URL in the first place. It does sound like lots of people keep running in to this, but I'm not sure what we could do about it.

    Also:

    Why isn't it sending me to the beta version??

    Why would it? By the time a stable release is out, the beta version is out of date and the stable release is newer. Do you really intend to keep using an old version?

  • The window load event fires as the runtime is loading. So assuming your script runs after that, it will not fire in your own scripts. You can just write your scripts assuming onload already fired.

  • The new built-in functions feature is a small step towards this. However it's a huge project, and has a high opportunity cost as it would offset all other work for a long time. So I like the idea but I think it will only be feasible to tackle it in the long term.

  • See the manual entry on the C3 runtime. Internet Explorer is no longer supported in the C3 runtime - if you still need to support it, switch back to the C2 runtime.

    Everything should work fine in both runtimes in Edge. Try making sure it's up-to-date. If anything is wrong please file a bug report following all the guidelines.

  • Please file a bug report for that otherwise it will get lost in the forum.

    • Post link icon

    I agree, so closing this thread.

  • Please only post in English on the forum.

    • Post link icon

    Yeah it looks like we accidentally left that behind the experimental flag. Oops! We should have it enabled in the next release...

  • Ashley maybe this could be an export setting for HTML5? Or part of the browser object?

    If the game is framed and the parent page is scrollable, Construct can't automatically control the parent page. So generally to properly solve this the arcade sites need to add that code themselves.

    • Post link icon

    Did you not understand my point about how working alone for years was unsustainable? I suspect you are raising this in bad faith. Please see the Forum & Community guidelines about discussing in good faith.

    Other companies in the past, e.g. in the 90s, did a waterfall style model where they released updates every year or so, incremented the version number, boxed it up, sent it out to the shop shelves (who does that any more?) and sold it all over again. In this day and age, and particularly with browser-based software, this is out of date. Besides, you still end up with the "I have to pay again" complaints. This is also exactly what I anticipated:

    Usually at this point people start throwing in random other payment models they just thought of - it's really been done to death, we've made the decision and I think it was the right one.

    I don't want to be further drawn in to yet another debate over this, so I won't be drawn on defending this topic any further, especially if I suspect the discussion is in bad faith.