Ashley's Forum Posts

  • nemezes - it works OK for me here.

    • Post link icon

    See the discussion in this thread.

  • V-sync involves very time-sensitive operations (it must prepare a frame in 16ms, otherwise it drops a frame). It's possible that if the OS does some background work, it schedules work away from the game just long enough to drop a frame. I'm pretty sure it varies depending on the system configuration (OS, driver, background work, compositor mode, etc) which makes it hard to reproduce consistently.

    FWIW other engines with native code have similar issues which are similarly hard to pin down (e.g. see this thread), so I don't think this is anything specific to HTML5 or browsers.

  • The reason browsers can't write files anywhere to disk is because that would be a security nightmare. (Hopefully this is obvious if you think about it - you could overwrite user documents, possibly replace system files, etc.) You can either set the browser to ask you every time as suggested, or use the desktop build of C3.

  • Did you draw the image each time or is it based on importing a C2 project to C3? Either way I think you should file a bug on the tracker following all the guidelines.

    • Post link icon

    I regularly use Construct 2 on Windows 10 and have not seen any such issues myself. If you have any issues, please file a bug report following all the guidelines with as much information as possible to help us reproduce the problem. If we can't reproduce the issue, there is very little we can do about it. The thread linked to earlier relates specifically to an issue with dialogs taking longer than usual to open in the event sheet; this should now be resolved (in the sense it is improved sufficiently to no longer be an issue; performance-related issues can never be fixed to the point of taking zero time, since it will always take some amount of time). As our bug report guidelines state that there should be one report for one issue, please make new threads for separate issue reports. The fact other issues were mentioned in the same thread is not helpful, we need separate reports per issue, as the guidelines state. I'm afraid if the guidelines are not followed, there is very little chance we can help.

  • Can't reproduce, it loads fine here. Please see the bug report guidelines, closing.

  • The problem is a recent iOS security update to mitigate the Spectre vulnerability was botched and breaks WebAssembly in Safari. We use WebAssembly to decode Opus audio in Safari because it doesn't natively support it. I filed an issue with Apple about 2 weeks ago: https://bugs.webkit.org/show_bug.cgi?id=181598 I can't believe that Apple still haven't fixed it. We might be forced to hack around it and disable WebAssembly in Safari.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'd add that for over 5 years we've advised plugin developers not to fork (copy-paste and edit) official plugins/behaviors: https://www.scirra.com/forum/please-do-not-adjust-official-plugins-or-behaviors_t71650

    This is because we've always known doing so causes all sorts of compatibility problems, just like the one in this thread. Other difficult compatibility problems that can happen include bugs being fixed in the official addon but not the fork, new features being added in the official addon but not the fork, and in the long run, the official addon gaining the same features as the fork therefore making the fork redundant, but leaving you with the awkward job of removing the fork from your project and recreating all the events that use it.

    My advice to users would be avoid any third-party addons that are based on a copy of an official addon. You're basically signing up for these compatibility problems.

    I am happy to work with addon developers to come up with alternative extensibility options, but I rarely see any discussion of this - most addon developers ignore our advice and fork official addons anyway. To try to avoid the problem in C3 we've done our best to hide the addon source code so it's simply not an option.

    I would also add I appreciate all the work addon developers do, and it's great for the community. I only make an exception for this specific case of copy-pasting an official addon and changing it. I wish people wouldn't do that.

  • The work to support Construct on Mac is so difficult it involves rewriting the entire editor. We already did that, and it's called Construct 3, and it works on Mac.

  • Shouldn't you report this to Duet then?

  • At this point we are only maintaining C2 - any new features will be C3 only. As you mention, much of what you requested has already been implemented in C3.

  • understandable but consider us construct 2 user to give us a way to build without going elsewhere

    You can do your own builds with the Cordova CLI, which is free.

  • I got a reply from Renato Rivero - they claim to have made a mistake. I'm not sure we know what really happened, but they said they won't contribute any more anyway, and I have already removed their access to the translation.

    I compared the current state of the translation to the last update I used and the current state is further ahead. It looks like it preserved all new translations when I restored the old translation, and there is no significant loss. So I don't think anyone's work has been lost. Also thanks to nemezes, it looks like there are no more mistakes currently. So right now Portuguese is on 80% (3% further ahead than the translation I restored) and everything looks OK.

    Unfortunately I can't find a way to recover the contribution counts; I'll contact POEditor's support and see if they can restore those. As long as they can tell us the count as it was on January 23rd, we will simply add those contributions to the results when it's completed.

    Thanks for your patience everyone and sorry for the inconvenience. I think it's safe to keep contributing; after everything that happened it doesn't look like we lost any actual translations, so even if it happens again it looks like we should be able to restore everything. However it's definitely understandable if anyone wants to wait a couple of days before continuing to make sure it's settled down.

  • Closing, if you're not sure if it's a bug perhaps post somewhere else in the forum first.