SoC Ideas Sprite Sheets2011 - Revision history

Boucman: /* Additional Information */

2011-03-31T21:54:18Z

‎Additional Information

2011-03-09T21:34:14Z

‎Whom to ask about this

2011-03-08T21:39:53Z

2011-03-08T21:30:42Z

‎Whom to bug about this

2011-03-08T20:53:42Z

idea update

2011-03-08T20:26:26Z

‎Description

2011-03-08T20:26:03Z

2011-02-27T11:44:21Z

add description

2011-02-27T11:04:56Z

add template

2011-02-27T11:02:57Z

add DPL for proposals

@@ Line 37: / Line 37: @@
 * 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 =
 * Boucman (developer for the unit animation engine)
 * thespaceinvader (artist, for usability questions)

← Older revision		Revision as of 21:34, 9 March 2011
Line 39:		Line 39:

	= Whom to ask about this =		= Whom to ask about this =
		+	* Boucman (developer for the unit animation engine)
		+	* thespaceinvader (artist, for usability questions)

@@ Line 1: / Line 1: @@
 {{Template:SoC2011Idea}}
 = Description =
@@ Line 35: / Line 22: @@
 solution and discuss that with the developers during the application period.
 = Additional Information =

← Older revision		Revision as of 21:30, 8 March 2011
Line 40:		Line 40:
	* 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.		* 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 =	+	= Whom to ask about this =

@@ Line 18: / Line 18: @@
 Page for the idea: [[SoC_Ideas_Sprite_Sheets2011]]
-Currently, all the Wesnoth unit animations are based on thousands of small png images, each
+Currently, all the Wesnoth unit animations are based on thousands of small png
-image representing the unit in a single pose. In a sprite sheet approach,
+images, each image representing the unit in a single pose. For terrains the
-each unit is represented by a single, huge, image where all the unit images
+situation is the same, it has a base image with a lot of transitions to other
-are put on a mosaïc pattern and the game knows where to look for a given
+terrains, which are now stored as seperate images.
 image.
 = Additional Information =

@@ Line 25: / Line 25: @@
 The sprite sheet approach has huge gains in term of memory consumption, but
-there are a couple of problems that need to be solved by the students
+there are a couple of problems that need to be solved to implement it.
 = Additional Information =

@@ Line 13: / Line 13: @@
   |format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
 }}
 =Additional Information=

← Older revision		Revision as of 11:02, 27 February 2011
Line 1:		Line 1:
	{{SoC2011Idea}}		{{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/>,
		+	}}
		+
	=Additional Information=		=Additional Information=