Ashley's Forum Posts

  • At this point C2 is only being maintained and will not get any new features. C3 already has the feature.

  • Huh, I just realised it's kind of inconsistent - you will get a warning if you delete an individual object type, but not a folder of them. I guess we need to go through a few places and make this more consistent. Please go ahead and file a bug for that.

  • In the past other users have asked us to remove such warnings because they're annoying, especially when there are no references to the thing being deleted in the project. Unfortunately due to the frequent use of layer name references by expressions, the editor usually can't determine for certain whether a layer has references or not, which makes it difficult to bypass a no-references warning. So I suspect we could not ever bypass the warning, and then the next suggestion would be to remove it...

  • Of course. Have you tried it?

  • To make it stable, taking FPS into account is important

    That's the wrong solution, and uses an extremely coarse measurement anyway. You probably should use something like requestIdleCallback instead. Besides in the C3 runtime layout loading is now asynchronous so may not jank the game any more while loading. Also the whole idea of preloading an entire other layout will spike the memory usage high, significantly increasing the risk of out-of-memory crashes... it kind of defeats the point of the layout-by-layout memory management that aims to keep peak memory usage low.

    I'm not sure why this needs to have anything to do with loadingprogress either - why not just give the plugin its own expression? The more you hack in to the runtime code, the more brittle it is in the face of future changes. The best architecture is to keep as much code as possible entirely independent of the runtime.

  • Why do you need them for a preloader addon? What does it do and why can't you do it without these? In particular requiring the FPS for this seems particularly weird.

    Given we are obligated to permanently support all APIs we document with backwards-compatibility forever, I'd prefer to keep the SDK to the essential minimum.

  • Why do you need them?

  • Construct manages memory layout-by-layout, so the most memory-efficient way is to use separate layouts.

  • Please use the existing feature request/bug report systems. We are busy with a couple of long-term projects, regular bug reports, and hundreds of existing feature requests so I can't really promise anything from a forum post.

  • 1 - What are the BIGGEST differences between C2 Runtime to C3 Runtime?

    The C3 runtime is a complete rewrite with a whole new architecture, much better performance, and new features (e.g. BBcode in Text objects).

    2 - Is C3 Runtime much more POWERFUL compare to C2 Runtime or there are only minor changes?

    The C3 runtime is much more powerful. It already has major new features. In future major new features will also only be written for the C3 runtime, and its new architecture makes that far easier and allows for much more significant changes.

    3 - How can I Test/Feel some differences right now on my game using the current C3 Runtime stable release? (R111)

    Performance tests in intensive games should significantly improve, or you can already test the new features.

    4 - Should I keep working with C2 Runtime for now on my official game project? or not? and why?

    The C3 runtime is still experimental so you should probably stick to the C2 runtime until we announce that it is out of beta and officially recommend that projects start switching to it. It's still useful to try testing your project with it though to see if it works and report any bugs that come up. You can then switch back to the C2 runtime providing you didn't add any features only available in the C3 runtime.

    5 - Will C3 Runtime be complete and default soon? and is it already safe to use it on official project?

    The C3 runtime is pretty much already code-complete. The only remaining major step is to finish the C3 debugger (again being rewritten), and keep fixing bugs which will probably keep coming up for a while since it's still relatively new. But yes, we should be ready to launch it soon, in the next few months hopefully.

  • You shouldn't need this for compatibility with other plugins that need jQuery - those plugins can just call SetUsesJquery(true) to bring back jQuery. (Of course the ideal solution is to remove jQuery completely!)

  • As per the bug report guidelines you should only test the latest version to avoid reporting issues we've already fixed. Likewise I always test the latest version.

  • What do I do to reproduce the problem? If I install the addon and open wTween.c3p it runs fine with no errors.

  • I can't see any reason this would happen. I think I'd need to see running code to investigate.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • FWIW the GDPR issue is actively being worked on. There are comments from Iain on the GitHub issues discussing some of the complications and his approach to solving them. Unfortunately sometimes things end up being more complicated than anticipated, but I think we've been reasonably open about what's happening with that.

    Believe it or not we have other developers who continue working on other things in the mean time. In fact the new templates were developed by Kyatric and not one of the main Construct developers, so that didn't really take up any of our developer time at all. The idea we should hold back anything new even if it's done just because there might be other issues seems pretty bizarre to me.

    I think we've done a great job with Construct 3 and I'm really happy with the way things are going overall. Most of our development resources have been taken up with work on the C3 runtime and the new timeline, both of which are major, long-term projects. I think by the end of this year a lot of that work will be approaching done and we'll have more time to accelerate work on new features.