Ashley's Forum Posts

    • Post link icon

    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.

    • Post link icon

    Fooling arround with the settings a lot the issue disapears on PC when i turn off "WebWorker"

    There is a known issue with the Android WebView where it is janky when using worker mode. However the default settings do not use worker mode. You will only run in to this if you manually change the project 'Use worker' setting from 'Auto' to 'Yes'. If you leave it on its default 'Auto' or 'No', it should work OK.

    I'd like to point out that the existence of such a bug does not mean that HTML5 or our hard-working team are somehow useless. In fact I have already done significant work to investigate this very issue in order to file that issue with Google. All software has bugs and nothing is perfect. On the whole I do believe Construct and browser performance are outstanding these days.

    I'd add that a great deal of work has been done on this in the past, and we do work really hard to ensure there is great performance on all platforms. However in this case the bug is caused by the Chromium browser engine and therefore it's out of our control - only Google can fix it. However the issue is easy to work around and the default project settings are not affected. Further please note that in general it is usually impossible to help without the details requested by our bug report guidelines. We need all that information to be able to help, and if it's omitted all we have is guesswork.

  • I'm afraid Construct Animate subscriptions are not yet on sale. The period of being able to use Construct 3 subscriptions with Construct Animate was only for the duration of the public beta, and that is now ending.

  • Some addons don't properly support advanced minification. Our documentation covers what developers need to do to support it. If it doesn't work you'll need to report the problem to the addon developer.

    • Post link icon

    If the problem is with our server, then why is it working for everyone else?

    I'm afraid if neither we nor anyone else is able to reproduce the problem, then the onus is on you to test combinations and try to identify what factors are involved, as nobody else is able to test those things.

    Not all problems in the world are our fault and it's not reasonable to insist that we fix everything, especially when it's not clear it's related to our services which as far as I'm aware are working for everyone else. Unfortunately this type of thing has happened before, where people repeatedly insist we fix things when it's infeasible for us to do so. For this reason our Forum & Community guidelines include:

    Demanding impractical measures or infeasible solutions. If we say we can’t do something, it’s not because we don’t want to, or we’re being difficult, we genuinely can’t do everything!

    I'm sorry that you're experiencing problems but all I can say is I hope you understand it's pretty much impossible for us to help in this kind of situation, and repeatedly insist we do so anyway does not overcome that. So I'm afraid I must emphasise the rules in the Forum & Community guidelines and that everyone is required to follow them at all times no matter how difficult or frustrating the problems may be, and for that reason I'm closing this thread. I'd also point out that I've already highlighted what should be a viable workaround: using the Cordova CLI allows you to complete builds locally without needing the use of the build service.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
    • Post link icon

    I just tried again, and it's still working fine for me. It's been several weeks now and it's been working fine for everyone else. I'm afraid I simply cannot explain what is happening but it sounds like an issue your end. The Internet is extremely complicated and there are lots of non-obvious ways it can fail that will only affect certain users, ISPs or regions. If that is indeed the case, which I think it is, there's no use constantly complaining to us, as it's impossible for us to do anything about it. Did you try contacting your ISP? Have they responded?

  • Try opening it in the latest release of Construct (r327.2).

  • This sounds like a classic case of creating more rendering work than the GPU hardware can handle. You'll need to optimise the game to do less rendering work, e.g. reducing effects and own-texture layers. See Performance Tips.

  • These kinds of glitches are usually actually caused by broken graphics drivers, not the browser or Construct. That's especially likely to be the case with an old system. Your best hope is to install any available system software updates, try updating the graphics drivers, or try turning off hardware acceleration in the browser (but that will also cause poor performance).

  • I'm afraid it's impossible to help without more details. As ever, if you run in to any problems please file an issue following all the guidelines, otherwise there is likely no way for us to be able to investigate.

  • It doesn't really make any sense because saving a single-file project always saves all the files every time. Only folder-based projects allow partial saves that only write changed files.

  • It's difficult to comment as there is little for me to go on here. As ever we need all the information requested by the bug report guidelines because we need all that information for it to be possible for us to investigate issues.

    Is it a folder based project? If you're saving a single file project I would expect saves to be slow with such a large project. Folder based projects are designed to be able to save much quicker.

  • It looks like an oversight that "beforelayoutstart" is missing, as there exist other events for the SDK and events for scripting for all four events. I've added "beforelayoutstart" for the next beta, and will document the other three events at the next stable release too, so you can start using those already.

    • Post link icon

    Update: this information is now available in the effect addon documentation. Please refer to that page for the latest details instead of this thread, which is now closed.

  • I'm afraid there's nothing we can do about this ourselves. You'll need to report it to Virus Total as a false positive.