Ashley's Forum Posts

    • 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!

  • Because.. if I start my code within Construct and try to play a sound (or mutliple sounds) after initialization of my layout, nothing happens.. I need to press a key (or input in general) first.. then all sounds start playing.

    That is the fix. Chrome doesn't let pages autoplay without interaction any more. Previously you might not have heard any audio at all.

    FWIW Google just announced that they will revert the autoplay change... and then reinstate it in October. This is totally bananas because it will just repeat the same problem, but later. Still, you have more time to re-publish content now.

  • The runtime makes canvas positioning calculations assuming there is no canvas border. If you add one, it might break that.

  • Editing official addons causes compatibility nightmares, so it's a deliberate decision to not make the code available. It's not necessary, either. The Instant Games SDK puts 'FBInstant' in the global namespace. So you can create a separate, independent plugin that makes extra Instant Games calls without needing to modify the official addon. Extensibility without compatibility nightmares!

  • There's no way to change it, unless you write a plugin that changes it on startup using JavaScript. What do you need this for?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The full Instant Games SDK is pretty big. It covers things like bots, multiplayer matchmaking, localization, IAP, advanced analytics, etc. It would be a considerable amount of work to fully implement it at the expense of everything else we have to do, and meanwhile I'm pretty sure some of those features would go largely unused too. It is much more feasible to implement feature requests if they are small and specific. For example if a suggestion asks "implement IAP for instant games", I could entertain the idea of making some time to work on that at some point fairly soon; but if a suggestion asks "implement the full SDK" then that is such a big job with questionable utility that I'd probably put it off as long as possible, which might mean none of it is done. We have to ruthlessly prioritise. Accordingly, the best suggestions are scoped to just the most useful part.

  • We strive to ensure every update is 100% backwards compatible. We are very careful when making any code changes to ensure that existing projects are guaranteed to work identically. This is for the most part verified by the lack of bug reports indicating regressions and we have a good track record on this. Any time we make breaking changes, we carefully document this and describe it in the release notes, although these cases are few and far between. Looking at the recent releases, I cannot think of any technical reason that would cause any significant changes to projects. If you do encounter issues, please file an issue following all the guidelines and we can take a look. Otherwise my best guess is the changes are caused by something else other than the updates.

  • The bottleneck is really that we only have a few developers and we're all extremely busy with everything else that is going on. I'd like to do this, but it's hard to make time for it without telling someone else their bugs/features are going to be delayed. I'll see if I can get a Mac version sorted out when the next Chrome release (67) comes out, which is due in a couple of weeks.

  • Please post any further feature requests to https://construct3.ideas.aha.io/. We'd love to do every feature suggested, but we only have a few developers, and we're extremely busy, dealing with thousands of bug reports and hundreds of other feature requests.

  • It's still a bug. It should at least return an empty value rather than show that error.

  • Well, please file a bug for that then!

  • The other loader styles should work on mobile. What gave you the impression the "Construct 3 splash" was the only one supported on mobile? You could also use a loader layout to completely customise it.