Hundreds of features to explore
Games made in Construct
Your questions answered
Popular & trusted by schools and Universities world-wide
Students do not need accounts with us
Our educational partners
Free education resources to use in the classroom
World class complete documentation
Official and community submitted guides
Learn and share with other game developers
Upload and play games from the Construct community
Game development stories & opinions
I have one project I am testing multiple arrays per object via ownership traits.. but it is a question for the devs, is it most effecient to have one large array per object or a few smaller arrays.. how much increase in CPU is it per call per array and what do the devs do themselves for their games?
I've done the one array per object thing, and I never noticed an impact on performance. Array loops and array data seem infinitely small compared to some other stuff, like object count and conditions like "for each"
Answer your own performance questions with measurements
Develop games in your browser. Powerful, performant & highly capable.
ok I see, everyone must have different experiences then thanks