Some Performance Questions in C3

0 favourites
  • 5 posts
From the Asset Store
Firebase: Analytics, Dynamic Links, Remote Config, Performance, Crashlytics on Android, iOS & Web Browser
  • Hello all,

    After a long break I picked up a c3 license and am enjoying exploring the new features! I just had a few questions on performance, as I'm building a mobile game and want to get started on the right foot.

    • Is using the 'every tick' system condition generally a bad idea? Obviously, doing stuff like generating a pathfinding obstacle map every tick is a bad idea, but what about things like updating text? Am I better off trying to update things every 0.1 seconds or something similar?
    • Are there any performance implications for splitting up events on multiple event sheets? I've just learned how to do that and it's really helping me organize my project. The ability to create an event sheet just to handle player movement, and include it when needed, has been pretty awesome, but I don't want to continue doing that if it has negative performance implications.

    Thanks for the help!

  • Generally speaking, you should avoid using every tick as much as possible. Programming principals would lean towards not making something that you cant control.

    Adding a simple variable compare is a reasonable solution... within reason. Speaking of within reason, running a set text every tick is reasonable, running many instances every tick, not so much.

    As to sheet includes, there's not been any indication that they have any performance impact.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • newt thanks for the reply. That makes sense.

  • "Every tick" is not a bad idea, what matters is what you put in it. There are a zillion thing that the game engine is running every tick behind the scene, so adding your "every ticks" wont make a huge difference unless you are doing something really crazy like changing 1000 text object every tick.

  • - Is using the 'every tick' system condition generally a bad idea?

    In general, no, unless like you say, you do something particularly expensive in that event. It's easy to find out if it has a performance impact: disable the event and see if performance improves. I'd guess most of the time you won't be able to measure a difference.

    [quote:7pts5odj]- Are there any performance implications for splitting up events on multiple event sheets?

    No, none.

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