Things you should have read but I know you didn't you sneaky little snake

3

Features on these Courses

Stats

1,503 visits, 1,947 views

Tools

Translations

This tutorial hasn't been translated.

License

This tutorial is licensed under CC BY 4.0. Please refer to the license text if you wish to reuse, share or remix the content contained within this tutorial.

Published on 28 Aug, 2019. Last updated 29 Aug, 2019

I cannot state this enough, RTFM

scirra.com/manual/1/construct-2

construct.net/en/make-games/manuals/construct-3

Once that is done, read this too:

scirra.com/manual/134/performance-tips

construct.net/en/blogs/construct-official-blog-1/optimisation-dont-waste-time-768

construct.net/en/blogs/construct-official-blog-1/common-mis-used-events-gotchas-822

construct.net/en/blogs/construct-official-blog-1/remember-not-waste-memory-796

Most of the time beginners encounter performance issues, it's an easy fix and is mainly due to a lack of understanding of how the engine works.

I'm not saying that you should dive head first in the runtime code for C2 and C3 (even though, if you can, you probably should do it because it's fun), but to at least read the resources that have been provided to you by the people who wrote the software. And by "people who wrote the software", I mean Ashley because all of these articles are super old but still relevant today.

Finally, I'm absolutely not the first dude from the community to give performance tips, so you should probably spend some time reading these as well:

(Please note that these were made for C2, before C3 was even revealed and should be read with that in mind if you're using C3)

construct.net/en/tutorials/performance-tips-for-mobile-games-163

mega.nz (this e-book contains info about the dead IntelXDK service. Just ignore that part)

  • 1 Comments

  • Order by
Want to leave a comment? Login or Register an account!
  • I am happy to have read this more than a dozen times, and I continue to read it. (remember-not-waste-memory). It is very pertinent ...