Ashley's Forum Posts

  • It's already supported by the official Touch plugin. As documented in the manual:

    Alpha is the compass direction in degrees.

  • It looks like a bug in the site. We should fix it soon. In the mean time just refresh the page and the content will load.

  • Well now you have two 'On start of layout' triggers, one which sets the variable, and another that gets it. It works if it does set then get, but it doesn't work if you get then set. So you've created a dependency on the order on which Construct runs 'On start of layout' triggers. It's best to avoid depending on internal details like that. If you initialise everything in one 'On start of layout' trigger, then you have clear control on the order things happen.

  • You shouldn't need different worlds to do that. The existing features should allow you to do all that already, with collision disabling and per-instance forces.

  • I'm afraid the file is corrupt. I tried to recover it but it's too badly damaged to be able to recover any meaningful part of the project. Perhaps network or hardware failure corrupted the file in transit. Try retrieving the file a different way from the student's device, or use a backup.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • There's no spritefont instances placed anywhere in the project, and none of the events specify a character set. So Construct doesn't know what the sprite font character set is. Just drop in an instance to a layout (even an unused layout) and it will work.

    To make this easier I've updated Construct revert to defaults in this case, if none are placed in the project. But it means you have to use the default character set.

    Also note the events appear to have the same problem as this thread (creating an object in a sub-event, then trying to use it in a sibling event).

  • Try starting with the multiplayer tutorials.

  • I'm still not sure what you mean abot Box2D worlds. I think maybe you're talking about something else?

    However, that's 30 actions, and family doesn't hold physical collision action, is there any faster way to do this?

    Add the behavior to the family, then the physics actions appear for the family.

  • I just did a test Android debug APK build and it worked fine. Maybe it's an issue with your Internet connection?

  • I just tried it and it seemed to work fine. The "step" and "continue" buttons work as expected. What are you seeing?

  • I just tried it and it works as expected: https://www.dropbox.com/s/2m5df288h640h0o/New%20project%20%285%29.c3p?dl=0

    So if something's wrong, it's probably not this.

  • It's difficult to help after the fact. Ideally regular performance testing would identify the particular change that caused a slowdown. It also does not appear conclusive from what you've said that collision checks are the cause of the slowdown. It's possible they're perfectly fast and something else has slowed it down. The only way you can really narrow this down is by trial and error - turn things off and see if it stays fast, and aim to find the one thing that slows things down. Then you can either optimise that, or if you think that Construct is handling it inefficiently, isolate it in a minimal project for further investigation.

  • Construct also now supports exporting Android App Bundles, which is what that message is suggesting you do.

    It's a little unfortunate that they show that message to everyone, because in the case of Construct, there's not currently much benefit at all to using an Android App Bundle. But the message makes it sound important. Maybe there will be other benefits to using Android App Bundles in future though.

  • > The engine does already provide an efficient line-of-sight capability. So it should be possible to customise it to your needs already.

    mm No without hurting Performance huge time, I tried it already before but you have to remove completely the LOS Behaviour and do all the LOS checking by Events

    This is not what I was suggesting. Using events will indeed likely be slower. My suggestion was to use the LOS behavior's feature which can determine LOS between any two points. You can use that to customise visibility as you see fit.

  • With Construct's physics all objects share the same Box2D world, which is what I think you mean? I'm not sure why it would be useful to create different Box2D worlds, because AFAIK objects in different worlds cannot interact with each other at all. And you can already use different settings on different physics objects, so it doesn't seem necessary to use different worlds to achieve that.