Ashley's Forum Posts

  • Conditions only check the instances picked by previous conditions. So you can use a condition to filter down the picked instances to just a few, and then the next conditions will only run on those instances.

    Testing overlaps is actually a good way to filter down instances, because it uses the collision cells optimisation to avoid even checking far-away instances. So it can even scale to enormous layouts with thousands of instances and stay efficient.

  • Construct 3 can directly import C2 .capx files.

  • And how can I call their library inside the runtime.js inside the c2runtime folder?

    I don't understand why you're asking - it's all still JavaScript. So, the same way you already are.

  • FYI Construct 3 may well be better suited for this. Firstly the C3 runtime handles image memory much more efficiently. IIRC the C2 runtime always holds all compressed images in memory at all times, so you pay a memory cost for images even if they're not loaded. The C3 runtime avoids storing them in memory at all until they're really loaded, which can save tons of memory for large projects. Secondly the C3 runtime has built-in features to load and unload images for objects which helps manage the memory usage within a layout.

  • My plugin does not have a c2_runtime folder

    You'll need a c2runtime folder with a script named runtime.js in there with the C2 runtime implementation.

    I'd hope sooner or later KaiOS will update the browser engine and then C3 runtime games will work fine on it too!

  • Create an event sheet function with a string return value. Inside the event sheet function, add a script action with: 

    runtime.setReturnValue(testing());

    Now you can call the event sheet function as an expression, and it returns a value from JS.

    The general approach is to "wrap" JS functions with event functions.

  • 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

    Then what about making a beta branch with r265?

    What does that actually solve? You can already roll back to r265 if you want. Just download and install it. It won't open projects saved in newer releases, but if you're willing to modify the project file to allow that, then you can already go ahead and do it.

  • Which platform is that? All major browsers have supported WebGL and WebAssembly for some time now.

  • At this point the vast majority of projects are already using the C3 runtime. You could just skip supporting the C2 runtime.

  • This looks like a bug we already fixed in the latest beta. You should check using the latest beta release to ensure it's not something we already sorted out, otherwise filing a bug report following all the guidelines is the way to go.

  • Unless otherwise noted, everything in the SDK documentation applies to both runtimes.

  • Great to hear! Sounds like an excellent use for Construct. Hope things continue to go well!

  • That should already be fixed in the latest beta release.

    • Post link icon

    I don't want to pretend we're actively doing something if there's nothing we can practically do. Would you rather I mis-represented the situation to make it sound nicer?

    — - it's still not clear which version you're using, so this is simply repeating the confusion I already described. As I mentioned I'd strongly recommend starting a new thread specific to r269 and ensure every single case is comprehensively described.

  • I have to point out that the only way to solve the problem is to fix, or at least work around, the bug in the third-party library. You should contact them for support if necessary. Banning people will reduce but not eliminate the problem.