Ashley's Forum Posts

  • You must have done something else, like visit it directly or visited an older beta release, because stable releases do not notify you about beta releases unless you have changed the settings. I just checked to verify this.

  • We're using an experimental new feature in Chrome (Local Font Access) to support the ability to pick fonts for the Text object from a full list of all locally available fonts.

    Where it's supported

    To use the experiment you will need to use:

    • Google Chrome 88+
    • Construct 3 r225+
      • In stable releases, tick Enable experimental features in Settings
      • In beta releases, it's enabled by default

    How it works

    When the feature is supported, the font picker dialog for the Text object will prompt for permission to access local fonts. If you approve the prompt, then the list of local fonts is filled with a comprehensive list of all available fonts installed on your system. Without this feature Construct guesses a list of fonts, which is usually incomplete.

    Feedback

    Let us know if you have any thoughts about this! You can use this thread for general discussion about the feature. If you find a bug or a crash with it, please file an issue on the issue tracker as usual, following all the guidelines to ensure we can help.

  • Construct won't automatically update to beta releases by default. It only will if you enable the beta notifications in settings, or if you directly load the latest beta via the website.

  • The architecture of the event system does not allow for objects not referenced in conditions or actions to be picked, so it's not currently possible to automatically pick other object types in the hierarchy that are a different type to the root.

    Using conditions like "pick children" or "pick last created" should be used instead. If that doesn't work please file an issue.

  • See the guide on memory usage in the manual to understand how memory management works.

  • Try turning off "Enable experimental features" in settings. Sometimes experiments can cause crashes and problems.

  • Take a look at the Voice Recorder example.

  • Check the manual entry on Functions which covers this.

  • If yes, then I would appreciate a more specific response, especially from you, from the list of possibilities above (and profiler/inspector charts) on which of these could be more related to heating up, than the other.

    My point was: it's all of those things. All CPU and GPU work gives off heat. So optimising everything - all aspects of your game - will help.

  • This is deliberately not supported to avoid the many compatibility nightmares that arise from doing just that. You should develop any unique features you need in your own separate addon using just your own code.

  • Many mobile devices warm up when they're working hard. It's normal and affects any kind of software. For example playing Pokemon Go made my Android phone get pretty warm (and that of course was not made in Construct). A lot of CPU/GPU activity dissipates heat; it's a pretty fundamental aspect of computer hardware.

    Generally optimising the entire game, both in CPU and GPU terms, will help, but so long as the device is having to work moderately hard over long periods of time, you can expect the device to get warm. That applies to all software using any technologies on pretty much any hardware (even desktops warm up too, but they tend to have fans to help, and you tend not to be holding it in your hand!)

  • You do not have permission to view this post

  • I genuinely don't understand the problem here.

    You just need to update your team to the latest version all at the same time. Problem solved.

    In all your posts, you haven't given any reasons why that wouldn't work. So I'm just completely mystified as to why you are still asking about this.

    As I said: people who stay on old versions routinely run in to all sorts of bugs, compatibility issues, performance pitfalls and other problems that we've already fixed. This needlessly increases our support burden as people end up filing issues and contacting support about problems which were already solved. This wastes everyone's time, and is particularly painful for us as a small team with already very limited resources. We want to avoid that, so we auto-update everyone, and I think we have an extremely good track record with backwards compatibility.

  • Press F12 and check for any errors in the browser console.

    Try checking your Internet connection is working properly, clear your browser cache and try again.

  • When an update comes out, just tell your team to all update.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads