Optimization Tip Compilation: Post Your Tips

[sleeper_service]

@Kink

Also, and last tips, i always chase for undeleted object : sometimes and i’ve never figured how/why, some object that should be destroyed aren’t (for example you destroy an ennemy, destruction generated 3/4 objects (explosions/lights/etc.) or even your projectile). In the order of event, it should be destroyed, but not… it’s often related to particule objects, and even if you have picked “self destruction” of the object when the capacity number of particles is over … For it, the only solution is to check the debugger objects list, and after try different order/sub order for the events.

Yeah I use global obliterate events between enemy waves, as far as I can tell those catch everything, with most objects having self-destruct conditions already beforehand.

@Kink

It depends on a lot of things, but basically it’s really chronometers : i don’t use anymore actions and conditions related to this, i only use TimeDelta() custom chronometer, wich is really lighter. I also avoid to use mutliple chronos, sometimes you have to create one for each objects when it’s AI related, but for some case, a global chromometer is enough for multiples things (refreshing UI for example).

With chronometers you mean timers thne? Is till use those a lot… good to know that they should be better stripped down. Do you know if pausing unused timers does help?

@Kink

I always have memory leak problem in IDE preview, and it’s related to external events…

I have that too, but the compiled games seem to be unaffected. GDev also crashes a lot if I preview stuff after making changes to large event sheets, I got around that by almost always working in a small sandbox sheet now.

@Kink

I hope this will be helpful.

Most certainly, thanks a lot!