Mesh/Avatar Shape XML Format - Revision history

Darien Caldwell: clarify what SSA is

2016-03-28T19:20:23Z

clarify what SSA is

← Older revision		Revision as of 12:20, 28 March 2016
Line 69:		Line 69:

	== SSA Extensions ==		== SSA Extensions ==
	The Two main changes with ~~SSA~~ are the addition of '''many''' new <code>param</code> nodes , and the inclusion of new data in all <code>param</code> nodes.		The Two main changes with [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] are the addition of '''many''' new <code>param</code> nodes , and the inclusion of new data in all <code>param</code> nodes.
	*The additional <code>param</code> nodes now cover more than just the avatar's body shape and texture. Now, there is data for every possible avatar appearance modifier, including all clothes layers, alpha layers, tattoo layers, all internal morphs, and all settings for these items. In short there is every bit of data needed to completely recreate the entire avatar's 'look'.		*The additional <code>param</code> nodes now cover more than just the avatar's body shape and texture. Now, there is data for every possible avatar appearance modifier, including all clothes layers, alpha layers, tattoo layers, all internal morphs, and all settings for these items. In short there is every bit of data needed to completely recreate the entire avatar's 'look'.
	*The new parameters included in the <code>param</code> nodes is ''in addition to'' the original parameters. All of the originally available parameters are still provided. The new parameters are as follows:		*The new parameters included in the <code>param</code> nodes is ''in addition to'' the original parameters. All of the originally available parameters are still provided. The new parameters are as follows:

Darien Caldwell: Repair Syntax Highlighting from new Wiki software version.

2015-03-19T02:02:39Z

Repair Syntax Highlighting from new Wiki software version.

← Older revision		Revision as of 19:02, 18 March 2015
Line 8:		Line 8:
	The file is standard XML, with 3 parameters:		The file is standard XML, with 3 parameters:

	* <xml><?xml version="1.0" encoding="US-ASCII" standalone="yes"?></~~xml~~>		* <source lang="xml"><?xml version="1.0" encoding="US-ASCII" standalone="yes"?></source>
	** The <code>version</code> parameter sets the version of the XML markup. (should always be 1.0)		** The <code>version</code> parameter sets the version of the XML markup. (should always be 1.0)
	** The <code>encoding</code> parameter sets the character encoding for the file. (should always be US-ASCII)		** The <code>encoding</code> parameter sets the character encoding for the file. (should always be US-ASCII)
Line 19:		Line 19:
	The root node is of type <code>linden_genepool</code> with one parameter:		The root node is of type <code>linden_genepool</code> with one parameter:

	* <xml><linden_genepool version="1.0"></~~xml~~>		* <source lang="xml"><linden_genepool version="1.0"></source>
	** The <code>version</code> parameter sets the version of the data contained in the node. Currently LL's data is version 1.0. Future revisions may increment this version, so any implementation should check this version number before using the data.		** The <code>version</code> parameter sets the version of the data contained in the node. Currently LL's data is version 1.0. Future revisions may increment this version, so any implementation should check this version number before using the data.

Line 26:		Line 26:
	The Root node contains one node of type <code>archetype</code> with one parameter.		The Root node contains one node of type <code>archetype</code> with one parameter.

	*<xml><archetype name="???"></~~xml~~>		*<source lang="xml"><archetype name="???"></source>
	** The <code>name</code> parameter is a information parameter, and can contain anything, or nothing. Most commonly populated with 3 question marks.		** The <code>name</code> parameter is a information parameter, and can contain anything, or nothing. Most commonly populated with 3 question marks.

Line 43:		Line 43:

	<code>param</code> nodes correspond to sliders in the appearance pane. Each has 3 parameters:		<code>param</code> nodes correspond to sliders in the appearance pane. Each has 3 parameters:
	*Example: <xml><param id="649" name="torso muscles" value="0.500"/></~~xml~~>		*Example: <source lang="xml"><param id="649" name="torso muscles" value="0.500"/></source>
	** The <code>id</code> parameter corresponds to an internal viewer table of possible sliders. These numbers are guaranteed to be unique, and always correspond to the same slider.		** The <code>id</code> parameter corresponds to an internal viewer table of possible sliders. These numbers are guaranteed to be unique, and always correspond to the same slider.
	** The <code>name</code> parameter corresponds to internal 'driving elements' in the viewer. This can vary depending on the type of param. For shapes, it's often the name of the morph being controlled. For skins or eyes, it's usually a material that's being changed (color etc). For hair, a combination of both are present. These are '''not''' always unique. For example, there are two parameters called "torso muscles", with different IDs (one for male, one for female).		** The <code>name</code> parameter corresponds to internal 'driving elements' in the viewer. This can vary depending on the type of param. For shapes, it's often the name of the morph being controlled. For skins or eyes, it's usually a material that's being changed (color etc). For hair, a combination of both are present. These are '''not''' always unique. For example, there are two parameters called "torso muscles", with different IDs (one for male, one for female).
Line 51:		Line 51:

	<code>texture</code> nodes correspond to textures applied via the appearance pane. Each has two parameters:		<code>texture</code> nodes correspond to textures applied via the appearance pane. Each has two parameters:
	*Example: <xml><texture te="3" uuid="00000000-0000-4000-8000-000000000000"/></~~xml~~>		*Example: <source lang="xml"><texture te="3" uuid="00000000-0000-4000-8000-000000000000"/></source>
	** The <code>te</code> parameter corresponds to an internal viewer table of possible textures. These numbers are guaranteed to be unique.		** The <code>te</code> parameter corresponds to an internal viewer table of possible textures. These numbers are guaranteed to be unique.
	** The <code>uuid</code> parameter corresponds to the [[UUID]] of the texture applied at the time of the XML creation.		** The <code>uuid</code> parameter corresponds to the [[UUID]] of the texture applied at the time of the XML creation.
Line 59:		Line 59:
	== Comments ==		== Comments ==

	Comments are styled in the standard HTML style, with the string <xml><!--</~~xml~~> denoting the start of a comment, and <xml>--></~~xml~~> denoting the end of a comment. This is per the XML specification.		Comments are styled in the standard HTML style, with the string <source lang="xml"><!--</source> denoting the start of a comment, and <source lang="xml">--></source> denoting the end of a comment. This is per the XML specification.
	*Example: <xml><!-- wearable: shape --></~~xml~~>		*Example: <source lang="xml"><!-- wearable: shape --></source>

	== File Termination ==		== File Termination ==
Line 66:		Line 66:
	The file is terminated by the closing of the <code>archetype</code> and <code>linden_genepool</code> nodes:		The file is terminated by the closing of the <code>archetype</code> and <code>linden_genepool</code> nodes:

	*<xml></archetype></linden_genepool></~~xml~~>		*<source lang="xml"></archetype></linden_genepool></source>

	== SSA Extensions ==		== SSA Extensions ==

Solak Ohtobide: /* History */ spelling

2015-02-14T17:30:23Z

History: spelling

← Older revision		Revision as of 10:30, 14 February 2015
Line 3:		Line 3:
	The Shape XML format has been ingrained in the viewer since the early days, long before mesh existed. However, with the addition of rigged mesh and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".		The Shape XML format has been ingrained in the viewer since the early days, long before mesh existed. However, with the addition of rigged mesh and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".

	With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, ~~it's~~ XML version number is still 1.0, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.		With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, its XML version number is still 1.0, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.

	== Header ==		== Header ==

Darien Caldwell: Undo revision 1186198 by Kireji Haiku (Talk)

2014-01-08T23:56:04Z

Undo revision 1186198 by Kireji Haiku (Talk)

Darien Caldwell: Undo revision 1186194 by Kireji Haiku (Talk)

2014-01-08T23:55:24Z

Undo revision 1186194 by Kireji Haiku (Talk)

← Older revision		Revision as of 16:55, 8 January 2014
Line 1:		Line 1:
	{{Navbox/Mesh\|tech}}		{{Navbox/Mesh\|tech}}
	== History ==		== History ==
	The Shape XML format has been ingrained in the viewer since the early days, long before ~~[[Mesh]]~~ existed. However, with the addition of ~~[[Mesh/Rigging_Fitted_Mesh\|~~rigged mesh]] and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".		The Shape XML format has been ingrained in the viewer since the early days, long before mesh existed. However, with the addition of rigged mesh and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".

	With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still <code>1.0</code>, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.		With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still <code>1.0</code>, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.

Kireji Haiku at 18:50, 2 January 2014

2014-01-02T18:50:16Z

Kireji Haiku: fixed typo

2014-01-02T18:45:54Z

fixed typo

← Older revision		Revision as of 11:45, 2 January 2014
Line 11:		Line 11:
	** The <code>version</code> parameter sets the version of the XML markup. (should always be 1.0)		** The <code>version</code> parameter sets the version of the XML markup. (should always be 1.0)
	** The <code>encoding</code> parameter sets the character encoding for the file. (should always be US-ASCII)		** The <code>encoding</code> parameter sets the character encoding for the file. (should always be US-ASCII)
	** The <code>~~standaline~~</code> parameter informs that the file is self-containted, and not dependent on any external files. (should always be yes)		** The <code>standalone</code> parameter informs that the file is self-containted, and not dependent on any external files. (should always be yes)

	'''Note that some viewers''' set <code>standalone="true"</code>. This is technically incorrect via the XML standard. It should be <code>standalone="yes"</code>.		'''Note that some viewers''' set <code>standalone="true"</code>. This is technically incorrect via the XML standard. It should be <code>standalone="yes"</code>.

Kireji Haiku: added intra-wiki links

2014-01-02T18:45:01Z

added intra-wiki links

← Older revision		Revision as of 11:45, 2 January 2014
Line 1:		Line 1:
	{{Navbox/Mesh\|tech}}		{{Navbox/Mesh\|tech}}
	== History ==		== History ==
	The Shape XML format has been ingrained in the viewer since the early days, long before ~~mesh~~ existed. However, with the addition of rigged mesh and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".		The Shape XML format has been ingrained in the viewer since the early days, long before [[Mesh]] existed. However, with the addition of [[Mesh/Rigging_Fitted_Mesh\|rigged mesh]] and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".

	With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still 1.0, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.		With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still 1.0, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.

Kireji Haiku: highlight as xml code

2014-01-02T18:40:37Z

highlight as xml code

Show changes

Darien Caldwell at 18:29, 7 September 2013

2013-09-07T18:29:47Z

← Older revision		Revision as of 11:29, 7 September 2013
Line 58:		Line 58:

	*</archetype></linden_genepool>		*</archetype></linden_genepool>

			== SSA Extensions ==
			The Two main changes with SSA are the addition of many new 'Param' nodes , and the inclusion of new data in all 'Param' nodes.
			*The additional 'param' nodes now cover more than just the avatar's body shape and texture. Now, there is data for every possible avatar appearance modifier, including all clothes layers, alpha layers, tattoo layers, all internal morphs, and all settings for these items. In short there is every bit of data needed to completely recreate the entire avatar's 'look'.
			The new parameters included in the 'Param' nodes is in addition to* the original parameters. All of the originally available parameters are still provided. The new parameters are as follows:
			**The 'u8' parameter is a short integer normalized representation of the displayed slider value. Whereas before some complex math was necessary to determine what 0-100 slider value was indicated by the morph value in the 'value' parameter, now you can simply take the u8 value, divide it by 255, then multiply that value by 100. That will give you the displayed slider values. 255 would be a slider value of 100, 128 would be a slider value of 50, and 0 would of course be 0.
			**The 'type' parameter is a rough indication of what kind of data the 'param' entry is associated with. There seem to be 5 distinct values, which likely correspond to entries in the [[Avatar_Appearance#Linden_avatar_definition_file\|Linden Avatar Definition File]] (avatar_lad.xml)
			*** param_morph, param_driver, param_skeleton, param_color, param_alpha
			** The 'wearable' parameter further groups 'param' entries into distinct groups. These clearly indicate what avatar component the 'param' node is associated with. There seem to be 16 distinct values:
			*** shape, hair, invalid, gloves, eyes, skin, pants, shoes, shirt, jacket, socks, underpants, undershirt, skirt, tattoo, physics
			** The 'invalid' wearable indicates a morph.

← Older revision		Revision as of 16:56, 8 January 2014
Line 3:		Line 3:
	The Shape XML format has been ingrained in the viewer since the early days, long before mesh existed. However, with the addition of rigged mesh and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".		The Shape XML format has been ingrained in the viewer since the early days, long before mesh existed. However, with the addition of rigged mesh and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".

	With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still ~~<code>~~1.0~~</code>~~, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.		With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still 1.0, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.

	== Header ==		== Header ==
Line 9:		Line 9:

	* <xml><?xml version="1.0" encoding="US-ASCII" standalone="yes"?></xml>		* <xml><?xml version="1.0" encoding="US-ASCII" standalone="yes"?></xml>
	** The <code>version</code> parameter sets the version of the XML markup. (should always be ~~set to <code>~~1.0~~</code>~~)		** The <code>version</code> parameter sets the version of the XML markup. (should always be 1.0)
	** The <code>encoding</code> parameter sets the character encoding for the file. (should always be ~~set to <code>~~US-ASCII~~</code>~~)		** The <code>encoding</code> parameter sets the character encoding for the file. (should always be US-ASCII)
	** The <code>standalone</code> parameter informs that the file is self-containted, and not dependent on any external files. (should always be ~~set to <code>~~yes~~</code>~~)		** The <code>standalone</code> parameter informs that the file is self-containted, and not dependent on any external files. (should always be yes)

	'''Note that some viewers''' set <code>standalone="true"</code>. This is technically incorrect via the XML standard. It should be <code>standalone="yes"</code>.		'''Note that some viewers''' set <code>standalone="true"</code>. This is technically incorrect via the XML standard. It should be <code>standalone="yes"</code>.
Line 20:		Line 20:

	* <xml><linden_genepool version="1.0"></xml>		* <xml><linden_genepool version="1.0"></xml>
	** The <code>version</code> parameter sets the version of the data contained in the node. Currently LL's data is version ~~<code>~~1.0~~</code>~~. Future revisions may increment this version, so any implementation should check this version number before using the data.		** The <code>version</code> parameter sets the version of the data contained in the node. Currently LL's data is version 1.0. Future revisions may increment this version, so any implementation should check this version number before using the data.

	== Data Body ==		== Data Body ==

← Older revision		Revision as of 11:50, 2 January 2014
Line 3:		Line 3:
	The Shape XML format has been ingrained in the viewer since the early days, long before [[Mesh]] existed. However, with the addition of [[Mesh/Rigging_Fitted_Mesh\|rigged mesh]] and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".		The Shape XML format has been ingrained in the viewer since the early days, long before [[Mesh]] existed. However, with the addition of [[Mesh/Rigging_Fitted_Mesh\|rigged mesh]] and customized clothing, the file has become invaluable to creators. Sometimes called an "archetype file" due to it's default name "new_archetype.xml".

	With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still 1.0, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.		With the release of [[Project_Sunshine-Server_Side_Appearance\|Server Side Appearance]] in Early 2013, The XML format has inherited additional information. However, it's XML version number is still <code>1.0</code>, and it is still backward compatible with the original terse format. The additions will be outlined separately in the SSA Extensions section.

	== Header ==		== Header ==
Line 9:		Line 9:

	* <xml><?xml version="1.0" encoding="US-ASCII" standalone="yes"?></xml>		* <xml><?xml version="1.0" encoding="US-ASCII" standalone="yes"?></xml>
	** The <code>version</code> parameter sets the version of the XML markup. (should always be 1.0)		** The <code>version</code> parameter sets the version of the XML markup. (should always be set to <code>1.0</code>)
	** The <code>encoding</code> parameter sets the character encoding for the file. (should always be US-ASCII)		** The <code>encoding</code> parameter sets the character encoding for the file. (should always be set to <code>US-ASCII</code>)
	** The <code>standalone</code> parameter informs that the file is self-containted, and not dependent on any external files. (should always be yes)		** The <code>standalone</code> parameter informs that the file is self-containted, and not dependent on any external files. (should always be set to <code>yes</code>)

	'''Note that some viewers''' set <code>standalone="true"</code>. This is technically incorrect via the XML standard. It should be <code>standalone="yes"</code>.		'''Note that some viewers''' set <code>standalone="true"</code>. This is technically incorrect via the XML standard. It should be <code>standalone="yes"</code>.
Line 20:		Line 20:

	* <xml><linden_genepool version="1.0"></xml>		* <xml><linden_genepool version="1.0"></xml>
	** The <code>version</code> parameter sets the version of the data contained in the node. Currently LL's data is version 1.0. Future revisions may increment this version, so any implementation should check this version number before using the data.		** The <code>version</code> parameter sets the version of the data contained in the node. Currently LL's data is version <code>1.0</code>. Future revisions may increment this version, so any implementation should check this version number before using the data.

	== Data Body ==		== Data Body ==