Ashley's Forum Posts

  • You do not have permission to view this post

  • It's not currently possible for web content to limit the FPS in a way that correctly handles both CPU and GPU overload. For example if you want to limit to 30 FPS, but the GPU is overloaded and running at 25 FPS, it's not possible to handle that properly in JavaScript code without it descending in to a janky mess. You can code something that tries to skip frames or some such, but it won't handle cases like that properly.

    Star this Chrome issue to show support for proper FPS limiting in browsers.

    However if your only goal is to save battery on high-framerate mobile devices, AFAIK these devices already drop the framerate in power saving mode. So if that's your only reason to limit the FPS then I'd argue it's not necessary as it's already handled by the system.

  • Here are a few points for consideration!

    • If you are using event sheets and don't want to program, then a tool like Construct makes it possible for you to make your game whereas otherwise it could have been impossible.
    • A vast range of high-level features speed up development time a great deal, such as built-in physics, pathfinding, line-of-sight, platform movement, etc.
    • Being web-based makes it uniquely good for integrating HTML and CSS for things like forms and data tables, which can be tricky in other tools.
    • There is genuinely an identical codebase for all platforms meaning cross-platform issues amongst the supported export options are rare.
    • Browser performance is outstanding these days - many people still assume it's slow but it is in fact so fast now it can far out-perform competing tools
    • Publishing to the web provides a way around paying 15-30% of your revenue to a platform owner
    • Web technology is the future! Construct started when everyone was still using Flash, and the editor itself is fully web-based, and I believe that's the direction everything is going in long-term.

  • I don't believe we have made any changes to Construct that would cause such a large increase in the build size - it would have been a major problem for a lot of people if we had done so. In fact we've introduced features like WebP image support that allow further reducing the exported size.

    Almost all the build size is likely taken up by your own project's content - perhaps you accidentally imported some resource or perhaps even a third-party addon that increased the size a great deal.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Thanks, I've starred the issue so I'll also be notified of updates in case I can provide any assistance.

    I'm not sure if anyone is able to narrow it down to a specific time, or even Chrome release, where this issue first started happening (if that's the case and it hasn't been there forever), but if you could that would potentially be a key detail to help the Chrome developers figure it out, in case they made some important change to something around that time.

  • The advice doesn't say "never update Construct". It means you should not try to use source control when everyone's on different versions. The solution is to make sure everyone on your team updates the version of Construct they are using at the same time, and then everything should work fine. Construct prompts you when a new version is available, so when you first see that, just remind everyone on the team to update as well.

  • Thank you, it now successfully passes our automated review process, and the updated translation will be available in the next beta release. It will remain under review for several weeks so please be patient, but we will issue rewards once review is completed.

  • Issues like this are tricky to deal with as it's difficult to fully follow the bug report guidelines. However if you file an issue as best you can anyway, hopefully they can look in to it. I don't believe I've ever observed this issue, and usually dealing with a bug report involves a back and forth as the developers ask questions or suggest things to try and the person affected responds to those; if I don't see the issue there's no way for me to respond to those questions, and so if I file the issue all it does is slow down the process and make it less likely to get fixed. If you post the link to the bug that's filed here I can follow it and answer any Construct-specific questions if they come up.

  • Web apps have no control over garbage collection at all. It's entirely part of the browser. I think the best approach would be to file a bug with Google at crbug.com as perhaps there is an issue with Chrome's garbage collector that can cause lengthy pauses.

  • The Turkish translation recently reached 100%. Thank you to all contributors! However there are some outstanding translation errors that need correcting before the translation in Construct is updated and rewards issued. These are listed in the log here: https://www.dropbox.com/s/cthktyhl6hz4d50/tr-TR-2023-02-07.txt?dl=0

    PLEASE NOTE: Do not use machine translation, like Google Translate, when translating Construct. It is an inappropriate tool that results in poor quality translations. These translations will then fail later quality reviews and have to be re-done, resulting in wasted effort and taking longer before the translation is ready and rewards not being issued.

    Unfortunately threads like this become entirely unmanageable as it has combined several entirely different topics: a known issue with worker mode with a workaround, general performance questions, compatibility concerns, Construct Animate, staffing, feature requests, new export options, and piracy. Such threads become too confused to be useful, which is why our Forum & Community guidelines include as a reason to lock threads:

    Chaotic changing of subject or mashing together different concerns, so there is no clear topic of conversation. There should be separate threads for separate topics.

    Therefore I'm closing this thread. I believe the original point of this thread is resolved by the worker mode known issue. However everyone is welcome to start new threads with different topics of conversation.

  • You can purchase the signalling server in the asset store and run your own server. However be warned that you should be familiar with server administration and networking topics, otherwise it could end up unreachable or less reliable than the official Scirra signalling server.

    If you want to experiment with an alternate Android export option, try Trusted Web Activities. That is very much a web export with the proper Chrome browser wrapped up as an app you can publish to Google Play. However it's not clear how ads or IAP would work with that. So it might work well for free apps but monetised apps probably still need to go with Cordova.

    I'm happy to profile and optimise Construct projects if something isn't running well! Sometimes there are easy changes that can be made to the project to improve performance, and sometimes I can optimise Construct. These days even phones several years old can manage 10,000+ sprites on-screen and still get 30 FPS, so most modern devices generally seem to be pretty fast. However I must caution that sometimes there are problems like crappy GPU drivers that ruin performance - a long-standing scourge of the industry affecting all technologies, not just Construct - and it's not always feasible to work around. But usually those are device-specific and not something that causes a performance issue on all devices. Still I'm willing to look in to cases of poor performance if anyone shares them.

  • Apologies for the inconvenience - earlier we increased the server hardware specification in order to improve the quality of service, but after the VM restarted a fault on the Azure host prevented any traffic reaching it. We immediately reached out to our hosting support who investigated and resolved the problem by moving the VM to a different Azure host. The service was down for about 1 hour 40 minutes. It should be working fine again now and we don't expect to need to do anything similar for a long time.

    I was under the impression Android performance was generally working fine for most people, as my own tests look fine and I hadn't seen any complaints about it for a long time. The problem in this thread appears to be enabling worker mode, which runs in to a known issue. Turning it off (which is the default) should mean problem solved.

    If not, please file an issue following all the guidelines! I'm not telepathic so I can't solve problems by reading descriptions or watching videos, we need the details requested by the bug report guidelines to investigate, and I don't believe any Android performance issues have been submitted that way lately, so as it stands we have nothing to investigate.

    Think we should have more staff to work on Construct? Then we need to grow the business, and a new product is potentially a great way to do that. If it went well it could double the size of the business - perhaps even more if it's a hit - and we could hire more developers as a result. Alternatively we can do nothing and remain a smaller company with limited resources. So if you want us to grow, it makes sense to be in favor of new ventures like Construct Animate.