SoC Ideas Sprite Sheets2011: Difference between revisions
From The Battle for Wesnoth Wiki
mNo edit summary |
|||
| Line 25: | Line 25: | ||
The sprite sheet approach has huge gains in term of memory consumption, but | The sprite sheet approach has huge gains in term of memory consumption, but | ||
there are a couple of problems that need to be solved | there are a couple of problems that need to be solved to implement it. | ||
= Additional Information = | = Additional Information = | ||
Revision as of 20:26, 8 March 2011
| This page is related to Summer of Code 2011 |
| See the list of Summer of Code 2011 Ideas |
| This is a Summer of Code 2011 Idea |
Submitted proposals:
There are no submitted student proposals for this idea
Description
Allow wesnoth to support spritesheets
Page for the idea: SoC_Ideas_Sprite_Sheets2011
Currently, all the Wesnoth unit animations are based on thousands of small png images, each image representing the unit in a single pose. In a sprite sheet approach, each unit is represented by a single, huge, image where all the unit images are put on a mosaïc pattern and the game knows where to look for a given image.
The sprite sheet approach has huge gains in term of memory consumption, but there are a couple of problems that need to be solved to implement it.
Additional Information
- How to build those huge sheets from our current images set?
- Wesnoth does not have a fixed number of frames per unit, nor does it have a fixed size for each unit frame. A naïve approach to the problem will not work.
Whom to bug about this
This page was last edited on 8 March 2011, at 20:26.