Ashley's Forum Posts

    • Post link icon

    I deal with thousands of bug reports. The vast majority of them are just fine. Reports like this are extraordinary in how combative and difficult they are to deal with. It is unacceptable to treat the staff with such distrust and accusations, and I am not obliged to investigate any issues where people are behaving unacceptably, especially when it's a third-party issue. We usually help with third-party issues out of good will, but if you make this difficult, we will run out of good will and simply stop working on it. If you don't like this policy, go and use different software.

    Also see this rule:

    [quote:2j9t3sjk]Don't troll the developers

    ...

    Arguing about whether or not what you did qualifies as trolling or not ("meta-trolling"). It is up to the judgement of our staff.

    —, you were already on a final warning - you have repeatedly done everything in that list time and time again. 7 day ban. Next time, you will not be unbanned.

  • It ought to remember everything. If it doesn't, please file a bug.

  • It looks perfectly smooth to me. I've seen a lot of these kinds of tests over the years, generally aimed at v-sync quality - they tend to look fine for me these days. For example on my system the space blaster vsync test can hit every frame within 0.1ms over a period of a minute. There does seem to be variation across systems as to how liable it is to jank.

    FWIW GC is entirely on the browser's end, but in modern browsers it's all designed to run in tiny slices of just a few milliseconds to avoid jank. It shouldn't be holding up for a noticable amount of time.

    It could actually be a browser addon spewing out rubbish in to the GC - have you tried disabling them?

  • If you're concerned about performance, then you should be aware we're aiming to release a whole new runtime for Construct 3 this year, which will have major performance improvements throughout. C2 still performs pretty well for the most part though - historically we've had far more users running in to hardware limits than engine limits, which is more of a game design issue than technology issue.

  • The manual lists every possible reason IIRC. If you can't figure out what causes it, share a minimal project demonstrating the issue and I'll take a look.

  • - Is using the 'every tick' system condition generally a bad idea?

    In general, no, unless like you say, you do something particularly expensive in that event. It's easy to find out if it has a performance impact: disable the event and see if performance improves. I'd guess most of the time you won't be able to measure a difference.

    [quote:7pts5odj]- Are there any performance implications for splitting up events on multiple event sheets?

    No, none.

  • Web content can't hide the URL bar for security reasons. (E.g. a page could open a popup window with no URL bar, which looks identical to a Facebook login dialog, but the URL is actually evilwebsite.com not facebook.com. You need the URL bar there to be able to tell if it's real or fake.)

    The desktop builds aren't affected though so can open popups with no URL bar. I'd also point out the browser tab mode is what you always got with C2!

  • The trace looks like it's updating the text object and there's an unusually long WebGL operation to update a texture. Endless Runner is fairly unique in having an every-tick-changing-text which will hit the text updating code regularly. It's strange if it's normally fast though, since it's doing the same thing every frame, so it's odd if one frame is suddenly longer. It could be the browser going off to do GC or something, or maybe even the graphics driver suddenly choking for some reason. Not sure...

    Does this only happen in Firefox? It says Gecko in the trace in places. Is it better in Chrome/Edge/Safari?

    • Post link icon

    I seriously doubt Microsoft engineers can help with a third-party application they have never heard of.

    There are Microsoft engineers whose job is literally exactly this.

    Since the evidence points to this being a third-party issue and you don't seem to want to co-operate, closing this report.

    • Post link icon

    > You can always cut us out the process anyway: if a Windows Update makes C2 go slower, you can try and go to Microsoft about that directly. If you find any way to do that though, I'd be interested to know how...

    >

    I'm sorry, but this is a ridiculous suggestion.

    It's not. If we can't reproduce the issue, it's better if you file it yourself. The first thing they'll ask is probably how to reproduce it and whether any variations help, and we can't answer that, only the affected users can. Microsoft engineers are pretty smart and can figure out the details from a high-level bug report. I've seen write-ups of far, far harder bugs that MS engineers figured out anyway. And then you don't need to sit around waiting to see what we'll do.

  • It's not supported yet, we need to figure out a good way to distribute it.

  • Usually you get a warning if the object is not in layout right?

    No, that's a different thing - there must be an instance of the object somewhere in the entire project to be able to create it.

    Separately, there must be an instance on the layout for it to be pre-loaded. If you create an object that is not pre-loaded, there is no warning, it just silently loads it on the spot, which often janks.

    As for the other issue, I'm afraid my telepathic debugging has its limits and I don't know. Try making a minimal repro.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Should be fixed in r253 - the fix being that Edge now correctly detects as not supporting multiplayer.

  • Closing, please follow the bug report guidelines (attach a minimal .capx reproducing the problem).

  • Closing, please see the bug report guidelines - we need all that information to be able to investigate reports, especially the steps to reproduce. Without it there is nothing we can do. We can't debug screenshots!