Ashley's Forum Posts

  • See the blog post Construct 3's new redesigned functions.

  • 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.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • 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.

  • 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.

    • Post link icon

    Like all the information required for bug reports, it can help, but often does not in itself lead to a solution. This is why we require full reports for every issue: it can't be known in advance what will lead to the solution, so we require as much information as possible to help us identify what is going on. Very commonly people miss out crucial details which delays the investigation. We really need comprehensive reports in every case.

  • That's not currently supported. You could invent your own system like using AJAX to fetch the latest version from a server, and if there's a newer one available, prompt the user to go and download and install it. (This type of thing is much easier on the web...)

  • Please file a bug report following all the guidelines, otherwise there is nothing we can do about this.

  • It's actually very difficult to use these, for two reasons:

    1. All the formats are lossy. So if you have something like nice clean pixel art, the lossy compression will probably add visible artefacts. They're designed for 3D games where things tend to be far away and so the detail less visible, but 2D games tend to require lossless textures.

    2. The formats need to be encoded, which requires shipping an image encoder with the runtime, and encoding the image during loading which will slow down loading times. Some compressed texture formats are also proprietary, so we're actually not allowed to ship an encoder.

    • Post link icon

    > As ever, there is very little we can do without reliable steps to reproduce the problem. There still does not appear to be anyone who's found reliable steps to reproduce.

    I feel so much sad while reading this, seems like a robot machine replied this :(

    I say this a lot, because it's true for all bug reports. I'm afraid reports without reliable steps to reproduce are usually useless. So until anyone can figure that out, there's almost nothing we can do towards investigating this, let alone fixing it.

  • The latest release lets you access the Binary Data's ArrayBuffer in script. So I think the most flexible solution is to write the binary modification you want to do in JavaScript.

    I have to say though, if you've never done binary modification before, it sounds like you're going to have to learn a few things about that before you can get this working.

  • > Why Adsense and not another?

    Because Google is 99% of the market?

    Do you have data to back that up? We won't develop features based on made-up numbers!