Ashley's Forum Posts

  • It looks like a crash in NW.js, but we can't reproduce it. I filed an issue with the NW.js developers already but there's not enough information to act on. If you can find any way to reliably reproduce the issue, that would probably be enough to fix it, but until then we're stuck.

  • You could use "letterbox integer scale" mode, which preserves per-pixel scaling by adding black borders if the canvas doesn't exactly scale.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • If you pick one A, it also picks the associated B automatically. That's how containers work!

  • Just re-export and re-publish the app with the latest version of C2. See this thread which explains the same issue.

  • SnipG - the project you provided in your last post now runs 55% faster in the C3 runtime with the latest beta.

  • I don't think Chrome extensions can do this, either. The extension APIs don't appear to provide file type associations, nor unsandboxed file system access. I also can't find anything that covers any of the other features only available in the desktop build, like copy-paste for images or launching external software. So I can't see any capabilities at all that it would be useful to add via an extension. This is why we have the desktop build, which provides all these features (and potentially more if we need them).

  • It's the same idea, yes - you need a user input event to unmute audio. However the difference is Construct automatically unmutes audio for you at the first opportunity. So you might not need a "click to start" preloader, unless you want to avoid sounds being cut off prior to the first input.

    NW.js won't ever implement this - they've already turned off user input requirements, e.g. you can request fullscreen at any time in NW.js, whereas the browser requires an input event.

    • Post link icon

    Many users are worried about other people reverse-engineering their projects, so exported projects are actually deliberately designed to be as hard to reverse-engineer as possible. So I'm afraid you've learned the hard way why you need to keep backups. These days just copying it to Dropbox/Google Drive/OneDrive etc. is a free and easy way to make a reliable backup.

  • I'm afraid it's not possible at the moment. Web pages can't directly access files on disk for security reasons, and currently there's no other API for web pages to register a file type association. The desktop build can do it if you manually associate it with .c3p files.

  • It's a great idea, but the API surface is huge and it could potentially take months to develop to a useful point. Given we only have three developers and have hundreds of other feature requests while also dealing with thousands of bugs, I'm not sure we'll have the development bandwidth to take this on at this time. I guess it's more of a long-term idea.

  • It should work offline with the latest iOS 11.3. Have you updated the iPad to that version?

    • Post link icon

    This is a very blaze attitude on the part of the founder. No coding experience needed? Ha!

    Heh. Try learning C then. You might find that it actually is a lot easier in Construct.

    People routinely blame Construct for things that aren't its fault, like the fact fractional calculations aren't exactly perfect. That literally comes down to the circuitry in the CPU, and is ultimately because computers don't have an infinite amount of memory.

    People often question some piece of behavior that is actually deliberately designed as a careful tradeoff between contradictory requirements of two different groups of users.

    Some of what has been mentioned is simply false. For example, you can have unlimited music tracks, even in the free edition.

    Anyway, I think this discussion is in bad faith since there doesn't appear to be any attempt to understand the reasoning behind this, or generally the limitations of the laws of physics, so locking.

  • The conclusion at the linked C3 issue is that you just need to re-export and republish. Have you tried that? I think it's something that changed affecting old Cordova versions or something, since nobody could reproduce it with a fresh project.

  • Just use the screen size expressions in the Browser plugin. The screen size is in CSS pixels, which use a fixed DPI, so it's a reasonable approximation of the physical size.

  • The C3 runtime SDK download for plugins and behaviors is now available. The addon downloads now include C3 runtime ports to demonstrate how they work. Find the downloads here: https://www.construct.net/make-games/manuals/addon-sdk

    (Note the effects SDK has no changes; it's 100% compatible with the C3 runtime already, because it doesn't involve any JavaScript code.)

    The initial version of the C3 runtime API documentation is available here: https://www.construct.net/make-games/manuals/addon-sdk/runtime-reference

    The runtime has a very large API surface. The documentation does not yet cover everything, but it should be a good start.

    For more information on how to make an addon for the C3 runtime, please see the new section on Runtime scripts in the guide. This is not yet 100% complete - it still needs to cover how to access DOM features when hosted in a worker, but there's no way to test that yet, so it's not covered for the time being. Please also note the section about use of private or undocumented API calls; you should not use these, we won't provide support for them, and we can't guarantee they will be kept backwards-compatible.

    Hopefully this is enough to allow addon developers to start porting to the new C3 runtime. If you have any questions about the new C3 runtime SDK, or need any particular areas that aren't covered at all to be documented, please let me know!