1: Getting Started
2: Building Logic
5: Game Mechanics
6: Advanced Topics
7: Testing & Tuning
8: The Last 10%
M1: Mobile - Intro
M2: Mobile - Basics
M3: Mobile - Services
M4: Mobile - Publishing
B: How-To Guides
3.0 Drafts (In Progress)
Optimizing Game Performance
Part of game development is creating logic that not only works but is optimized for fast, smooth gameplay that meets or exceeds the 60 frames per second mark. In Stencyl, there are many ways to improve your game's performance.
Avoid Too Many Collisions at Once
Stencyl uses Box2D for its physics engine, and the more Stencyl makes use of Box2D, the more calculations it's performing in a given frame. Since collisions means the physics engine is working, more collisions means potential slowdown.
To avoid this, make sure the actors that are capable of colliding have something to do with the gameplay you're going for.
For example, unless you want bullets in your game to act like actual bullets, you can safely change their physics settings so they don't make more than basic use of Box2D when they collide with actors.
You can change the physics settings on the Physics > General page for an Actor.
Notice how we've set the collision style to "Cannot be pushed" and disabled both gravity and rotations.
Remove Print Statements Before Publishing
If you're using print statements in your game for debugging purposes, you need to remove these before publishing your game. Even when testing, having multiple print statements can really drag down your game's performance.
(Note: In Stencyl 3.0 and above, printing in published games is automatically suppressed.)
Limit How Often Actors Use Always Active / Simulate
Although it's often helpful for actors to function while off screen (which is what Always Active allows), consider when you really need to do this in your game and when you can avoid it. The more actors that are running all of their Behaviors off screen, the worse your game's performance will be.
Limit the Number of Actors on Screen
This can be tough when you want a game with a lot going on, but if you do need a lot of actors on screen, make sure you use actors you can recycle, i.e. those created with the Create Recycled Actor block.
The following article, Optimizing Actor Performance, explains ways to improve actor performance in detail.
Avoid Expensive Calculations Every Frame
In the Always event block, you need to be careful about the types of calculations you choose to run here. The Always event block executes logic every frame, so running calculations that take use a lot of processing power each frame will slow down your game. Examples of calculations to avoid using in the Always event block include trigonometric calculations, random number generation, calculating the square root of a value, and those involving exponents.
Limit Use of Effects
The actor effect blocks can slow down your game, especially when applied to a number of actors on screen. These blocks are best used for temporary changes to an actor rather than having them always on. The example of blocks below shows overuse of effects.
Limit Use of Custom Drawing
The Drawing blocks under the Drawing category in Design Mode allow you to draw custom shapes on screen.
Using them takes up a lot of processing power, though, so take into consideration how many custom shapes you're drawing on screen at any given time. Consider pre-rendering your effects instead.
Don't Draw Multiple Things in the Same Place
When you draw anything on screen, avoid drawing things on top of one another. Doing this wastes processing power since you're drawing over the same spot multiple times.
Now it's your turn. Share your Tips.
What have you found, in your experiences, boosts performance of your games when you're in a bind? Use the comments area below to share your stories.
Last Updated: 2013-01-29 by Jon
21354 have read this article
Disclaimer: The Stencyl Team does not actively monitor comments on articles. If you're seeking help for your game, please ask a question on the forums. Thanks!