SoC Ideas Sprite Sheets2011: Difference between revisions

From The Battle for Wesnoth Wiki
Crab (talk | contribs)
Crab (talk | contribs)
mNo edit summary
Line 1: Line 1:
{{Template:SoC2011Idea}}
{{Template:SoC2011Idea}}
= Submitted proposals: =
{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2011 Student Page&SoC Ideas Sprite Sheets2011
|notcategory=SoC 2011 Not Submitted To Google
|include=#Description
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}


= Description =
= Description =
Line 35: Line 22:
solution and discuss that with the developers during the application period.
solution and discuss that with the developers during the application period.


{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2011 Student Page&SoC Ideas Sprite Sheets2011
|notcategory=SoC 2011 Not Submitted To Google
|include=#Description
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}


= Additional Information =
= Additional Information =

Revision as of 21:39, 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



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. For terrains the situation is the same, it has a base image with a lot of transitions to other terrains, which are now stored as seperate images.

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 advantage of having a large image with all positions is that it's more efficient in memory. Also one large file is more effecient on the harddisk and faster to load than a lot of smaller files. So the change to spritesheets will have a lot of advantages.

Regarding the implementation the student is free to come up with his/her own solution and discuss that with the developers during the application period.

There are no submitted student proposals for this idea

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 ask about this

This page was last edited on 8 March 2011, at 21:39.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.