Every X Seconds with Collision Cells?

  • If you put:

    every x seconds

    enemy is overlapping player

    Will it use the collision cells even though it's not the top event? If not, how would one do a "check overlapping" less often than every tick while using collision cells?

  • Yes, it will use collision cells. The collision condition only needs to be the first condition in the event referring to those object types. "Every X seconds" is a system condition so does not refer to any object types. If you had a condition before it picking any "enemy" or "player" instances, that would force it to skip collision cells.

  • Ashley - perfect. thank you!

  • Yes, it will use collision cells. The collision condition only needs to be the first condition in the event referring to those object types. "Every X seconds" is a system condition so does not refer to any object types. If you had a condition before it picking any "enemy" or "player" instances, that would force it to skip collision cells.

    is that mean to make the event like that ?

    is overlapping object

    every X seconds

    or

    every X seconds

    is overlapping object

    ?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • matrixreal, you can use lots of different types of pre-conditions providing none of them involve objects that comprise the subsequent collision check. Every x seconds, a Variable equals, and so on.

  • matrixreal - the second one - the first one checks every tick if its overlapping and only does the actions every x seconds, where as the 2nd one checks is overlapping every x seconds.

  • matrixreal - both ways use collision cells, but it is faster to check "Every X seconds" first. Then it only does the collision check on the timer. If you check the collision then have "Every X seconds", it will wastefully check the collision every tick, and ignore the result every tick apart from the times "Every X seconds" is true.

  • wow its amazing thanks ashley for confirm that

    my result with "every 0.1 seconds + is overlap " instead of "is overlap" alone are

    fsp : 55 instead of 49

    cpu usage : 17% instead of 28%

    collisions checks : 110 intead of 450

    its clearly different and i see that we earn a huge performances

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)