I've learned that pathfinding in multiple instances all at the same time (especially with the A* algorthirm) can kill a game with slowdown. Instead, create a group path, and let the little things handle the rest.
Also, creating mass amounts of instances of an object at the same time can be ghastly. If you have to create a large number of objects, do it a few a step, or deactivate objects outside the view so that the memory will be cleared, allowing more processing for what's important at the moment.
Another thing you can do is increase the priority of your game in the game options. This will make your game run faster, but you'll probably make many users mad when setting it to highest, as all other processes will pretty much be ignored, so this is usually a bad idea unless absolutely necessary.
So now, I ask you a question. What are your techniques for speeding games up? What are some of the functions you know to cause slowdown if used frequently like in the step event? What can you do instead of the afformentioned things to get the same desired affect? Please post any of your answers here.
Edited by xot, 13 April 2008 - 06:13 AM.
** Old Experts Topic **