SoC Ideas SpriteSheets

From The Battle for Wesnoth Wiki
Revision as of 12:42, 28 March 2010 by Crab (talk | contribs) (Description)


This page is related to Summer of Code 2010
See the list of Summer of Code 2010 Ideas



This is a Summer of Code 2010 Idea



Description

Allow wesnoth to support spritesheets

Wesnoth units are made of thousands of small png files, each containing the image of the unit in a given stance. This has the advantage of (arguably) being easier for artists. However this has a huge cost in term of memory usage. The point of this SoC would be to allow wesnoth to support spritesheets : huge images containing a mosaic of all images and related tools/code support

There are 4 student proposals for this idea

Shuger - sprite sheet support

I want add sprite sheet support to Wesnoth. The general idea is to assemble multiple small images into few bigger
See GSoC Sprite Sheets Shuger for more information.

Gabba - Sprite Sheets

I developed an approach to introduce sprite sheets to Wesnoth with minimal hassle for artists, and as little modifications to game code as possible. I support generation of various sizes of optimized sprite sheets, so we can adapt to various platform and memory/disk requirements. My system will rely on a single external tool based on an existing open-source solution.

Updated 04/09/2010
See GSoC-SpriteSheets Gabba for more information.

Titouu - Sprite Sheet Support

I'm interested in adding Sprite Sheet support to Wesnoth because the value it gives to the game in terms of performance. I'm also thinking of adding a tool to port existing and new contents to this format.
See Summer of Code Proposal by Titouu for more information.

Hagaren - Allowing use of spritesheets

I am interested in writing module which allow usage of spritesheets and will allow to convert easily old small images into new format.
See SummerOfCodeProposal Hagaren/ for more information.

Additional Information

currently, all the wesnoth unit animations are based on png images, each image representing the unit in a single pose. In a spritesheet approch, 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 spritesheet approch has huge gains in term of memory consumption, but there are a couple of problems that need to be solved

  • 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 approch to the problem will not work