Is the editor just generally sluggish/slow, or does it freeze completely for several seconds after certain actions? (I had this issue in the past)
This happens to me often and it's very annoying. Did you find the solution?
construct.net/en/forum/construct-3/how-do-i-8/create-local-variable-184639
I would also like to know answers to this interesting question.
Check this: fileport.io/PzPmLPgMRs7R
Hmm good question. The bullet setting adds more steps in the physics engine, so it's probably simply that more steps = more chances that when the collision triggers in Construct there also happens to be a collision in the physics engine.
That makes sense.
Without trying I'd suspect though that it's still not 100% reliant because the physics engine treats the shape as a perfect circle whereas Construct just uses the collision poly.
No, it is not 100% reliant.
In any case, in addition to setting a high value in the "Jump sustain" field, you would only have to replace the "On key pressed" with the "Key is down" condition for the jump:
I just discovered that, curiously, the result improves considerably when I simply check the "Bullet" box in the Physics behavior of the balls:
Maybe some expert knows why.
I assume you are using the Platform behavior.
Set a very high value (eg: 10000000) in this text field:
Develop games in your browser. Powerful, performant & highly capable.
Thanks everyone for your replies.
every tick: -- signal "nextFrame" Ball1: collides with Ball2 -- wait on signal "nextFrame" -- ... get contact info
R0J0hound This fails sometimes.
Ball1.Physics.ContactCount>0
R0J0hound This seems to work fine. Thanks.
WackyToaster Thanks for the idea.
It never works for me, in any game.
Here's a very simple project isolating the problem: fileport.io/4YaDKypQ3nKh
Check it and you will see that those three Physics expressions almost never work.
When the colliding sprites have the "Physics" behavior, are not immovable and their collision mask is set to "Circle", these three expressions do not work because their value is always 0:
You could, simply, check the distance between the center of both objects.
You can easily do it with any decent graphics editor:
Since each grid cell is a sprite, you can use this sprite to create grids (boards) as large or as small as you like, and the game will still run fine. This way, you can create different levels, some easier and some more difficult for the player.