Ashley's Forum Posts

  • I don't think we're anywhere near the kind of disaster that you seem to think is befalling us.

    The flip side of making a roadmap is users who get upset if we promise something and then plans change and it's dropped or delayed. Besides, we have talked about our future plans already, such as our plan for further developing the C3 runtime, the new timeline feature that is in the works, and so on. I think that is the right balance.

    • Post link icon

    First you blamed us for relying on Apple with software that runs in Safari, then you suggested making a Windows app and leaving macOS users using Safari, which would not actually solve the original problem that you blamed us for. So even if we do what you suggest, you can continue to blame us in the way you previously did. Therefore I think your only intent is to go round blaming us for anything you can. On that basis, I'm closing this thread.

    zumwaltwood - apologies for closing your thread but we are continuing investigation on the bug tracker here: https://github.com/Scirra/Construct-3-bugs/issues/1493

  • See our latest blog post: we plan to work on the addon SDK for the C3 runtime soon.

    • Post link icon

    Nothing wrong with your browser version approach, but like I said above. Stable windows version ( standalone ) first, then a browser version that would cover people using macs, etc.... makes more sense to me.

    So... because of a bug in a browser that isn't supported at all on Windows... you think we should have made a Windows app first?

    • Post link icon

    So then do you only blame Apple when Apple break their OS, but blame us when Apple break their browser?

    I suppose you think we should have written native apps for every OS simply to bypass the odd browser bug? Then we can say goodbye to all our customers on Chrome OS, Android, iOS, and Linux, none of which are viable to support with a native/separate codebase. Losing Chrome OS would stymie our appeal in the education market. And then we'd still end up dealing with Apple breaking things in macOS, or Microsoft changing things in Windows (which even affected C2 recently). And then our development would slow down so much with the extra workload that additional projects like the C3 runtime would simply be off the cards.

    Do you think we should have chosen that route? Personally, I am super glad we went with browser-based software, even if it means dealing with browser issues sometimes.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'm afraid it's considerably more complex to implement such a feature in a real commercial piece of software with a whole existing library and framework to integrate with, so providing a basic implementation like this does not really make it any easier. (It also uses jQuery, which we specifically avoid these days.) As with many features, I'd do it if we had unlimited resources, but we have to balance this with hundreds of other requests, bug reports, projects etc., and it doesn't look like the posted feature request has many votes.

    • Post link icon

    There's nothing about this that is specific to browsers. Take a look at this tool that broke with the High Sierra update - and it's all native code. Would you accuse them of screwing up for "relying on Apple" too? Are you absolving Apple of any mistakes they could ever make and determined to pin everything that could ever go wrong in the industry solely on us?

  • Most games don't save on a timer because how do you know you haven't saved a moment before the player dies, therefore making their save useless? A more common approach is to use checkpoints.

    • Post link icon

    The main problem with Safari right now is Apple just released Safari 11.1 which has a severe bug that breaks Construct 3. We've filed a report with Apple who are working on it: https://bugs.webkit.org/show_bug.cgi?id=184502

    We're doing our best to patch Construct 3 to avoid the issue in Safari. The latest r95 includes a workaround, but it may take some time to get right, since an essential feature is simply non-functional in Safari 11.1. I must point out that it is Safari that is broken, not Construct 3. Despite that we are working hard to get Construct 3 back to normal in Safari. It's quite frustrating for us since Apple are a multi-billion dollar corporation with thousands of engineers, and their software is broken; we have three developers (one of whom is currently off sick), and Apple's mistake here has left us in a spot of bother. I apologise for the inconvenience, but we are actively trying to sort things out.

    For the time being I'd recommend using Chrome on a desktop system where everything should be working smoothly.

  • Just out of curiousity, what's the main reason frame animations has that big of a performance hit?

    In that test, each sprite takes on the order of a few hundred CPU cycles. So even tiny amounts of extra work will look like a big performance hit.

    The work to tick animations ought to stop when the animation stops, but if you leave the animation playing it will have to keep ticking the animation, which will show up as a performance impact.

  • It sounds like this issue: https://github.com/Scirra/Construct-3-bugs/issues/1396

    It's a Chrome bug that's already fixed, just need to wait for the fix to reach the stable channel.

  • We've closed around 95% of all issues filed for Construct 3 - well over 1000 reports. We have thousands of happy users who use it daily. Can you point to any specific issues that are giving you trouble?

  • In short, it's been 18 days without any updates...no more support from Scirra?

    Many software tools out there only have updates every few months. I think we've really spoiled you with regular updates if you think 18 days is a long time!

  • 1) Every 0.1 seconds, save it.

    There is no reason to do that and it will be very inefficient and have a significant performance impact. The feature is designed for one-off saves. If you provide a project that uses the feature in a reasonable fashion, I can take a look, but otherwise it sounds like it's not working because you're mis-using the feature.

  • The project uses a third-party addon. Please see the bug report guidelines, closing. Also both those URLs you provided return 404 not found, which is obviously a problem with the server, not Construct.