0 Favourites

Check Collisions per tick ?

  • I was wondering what is the ideal number of collisions per tick?

    When i say ideal i mean the ideal check collisions per tick to run a game smooth.

    300 check collisions per tick, should i worry or not?

    So yeah, that is my question.

  • I was wondering what is the ideal number of collisions per tick?

    When i say ideal i mean the ideal check collisions per tick to run a game smooth.

    300 check collisions per tick, should i worry or not?

    So yeah, that is my question.

    It depends on different factors, In the debbuger you can see both type of collisions checks:

    -Collision checks: It is a quick bounding box collision test, if this test is true, then it does the polygons check to see if the collision is truly happening.

    -Poly checks: a costly collision check, based on the collision polygon, this one should be as low as possible IMO.

    I think that the best is to not have useless collision checks, for exemple, is it useful to check every tick the collision between a giant slow canon bullet and a slow moving target (I mean in a case that they'll overlap during 10 tick in any case)? I think in some cases, you could try to filter those cases where the collision doesn't have to happen each tick (maybe by disabling collisions), but only if needed, also the collision cells can really help so filtering instances isn't always the best.

    As for the quantities of collision checks, I guess it depends of the targeted platform, just try to not check useless things if that helps

  • To improve performance you can include:

    Disable collisions for all objects.

    Create conditions for objects of families

    Collisions enabled >Is onscreen

    for objects requiring collision.

    This increase memory assuming your objects exist off screen.

  • Well thanks for the answers .

    But I was not asking for a way to improve the perfomance.

    Thanks for the tips anyway.

    I am new in this community and in Constract and i was wondering how well construct can handle the collisions.

    I mean in numbers.

    300 collisions checks per tick is a huge number of collision checks or not ?

    What is the number of collision checks to avoid?

    Thanx again and i am sorry for the bump.

  • I have more than 15,000 collisions checks per tick on my game and i don't know if it bad or not?

  • I have more than 15,000 collisions checks per tick on my game and i don't know if it bad or not?

    PC game? Well if you test it and it runs fine then no worries.

    Likewise, a number is meaningless, test your game on devices that you are targeting and keep testing it as you progress.

  • Collision checks are a major factor in performance, so the amount to aim for is the total of 100% necessary collision checks...

  • i have about 120.000 collision checks per sec and it runs at 60 fps on my pc. so i guess everything is relevant depending on which platform you want to publish.

  • Construct 3

    Buy Construct 3

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

    Buy Now Construct 3 users don't see these ads
  • It depends entirely on the CPU power. Be careful not to mix up the per-tick and per-second measurements - 15,000 checks per tick is a lot, but per second it would be fine.

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