Ashley's Forum Posts

  • At this point the vast majority of projects are already using the C3 runtime. You could just skip supporting the C2 runtime.

  • This looks like a bug we already fixed in the latest beta. You should check using the latest beta release to ensure it's not something we already sorted out, otherwise filing a bug report following all the guidelines is the way to go.

  • Unless otherwise noted, everything in the SDK documentation applies to both runtimes.

  • Great to hear! Sounds like an excellent use for Construct. Hope things continue to go well!

  • That should already be fixed in the latest beta release.

    • Post link icon

    I don't want to pretend we're actively doing something if there's nothing we can practically do. Would you rather I mis-represented the situation to make it sound nicer?

    — - it's still not clear which version you're using, so this is simply repeating the confusion I already described. As I mentioned I'd strongly recommend starting a new thread specific to r269 and ensure every single case is comprehensively described.

  • I have to point out that the only way to solve the problem is to fix, or at least work around, the bug in the third-party library. You should contact them for support if necessary. Banning people will reduce but not eliminate the problem.

  • I think these days for privacy reasons mobile OSs make this intentionally difficult to obtain. It might be easier to find a different way to do this, such as requiring a login and using that to restrict access where necessary.

  • That sounds similar to this NW.js bug.

  • The event equivalent literally does: offset position, test overlap, restore position. It's straightforward to do that from script as well. You could wrap it in your own function to handle the offset and restore.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • is it possible to set multiple object types to the same custom class?

    Yes. You're basically just changing the type of class used with new.

    Note that inside a constructor, the object has not yet actually finished initialisation. It is only in its final state once it has run all super calls, initialised the entire inheritence chain, and then finished the most-derived class constructor. So if you want to inspect the fully initialised state of the instance, you need to check that after creation.

  • The PlainText expression of the Text object gives you the text with all the tags stripped out. So can't you just calculate a time based on the length of that string?

  • Please note that as explained in the bug report guidelines, large projects make it considerably more difficult to investigate bug reports and so if you report issues this way you should expect a much longer duration for investigation and resolution. In comparison, if you can provide a minimal project to the bug tracker following all the guidelines, we can often fix the problem very quickly.

    • Post link icon

    This is understandable. But why not just roll back to the stable version then (r265)?

    This will cause more problems than it solves, because any project saved in r266+ cannot be opened in r265. It would result in absolute chaos. If we modified r265 to try to avoid this, we would have to issue a new release, and that means we're not actually using r265 any more.

    If you look at the changelogs, there have only been minor changes since r265, and mostly to the runtime. As it stands I have no idea what could have changed that would result in the kinds of stability issues people are reporting. We already made a significant upgrade to our third-party UI library in r268 as an attempt to resolve this, and as I recall the initial reports were that improved things. However there appear to still be issues being reported, although it's not particularly clear which versions are affected, because this post initially referred to r267 (prior to that change) and people aren't consistently referring to exact versions (again critical information we require in bug reports). Maybe something changed in our build system, but there has not been any intentional change there, so I don't know where to look or what to do about it - as always, being able to reliably reproduce an issue and investigate it via debugging is critical to identify what could be done about it.

    Long, confusing threads like this usually actually make it harder to deal with issues. We need concise, accurate, comprehensive information to be able to investigate reports. As I mentioned it's very difficult to make sense of a thread initially relating to r267, but with new vague reports of something possibly wrong in an often unspecified version. Are lots of people still using r267 and complaining of stability issues that are already fixed? I can't tell from this. I'd strongly recommend starting a new thread that relates to issues in r269 specifically, and do everything possible to identify the systems, circumstances, configuration, version, steps to reproduce, and everything else that helps identify bug reports. I'm still perfectly willing to investigate crashes and stability issues in C2, but if there is no useful information to follow up on, there's simply nothing that can be done.