HowTo/Update an existing asset on the DownloadStation - Revision history

Retro00064: /* Return to How To Index */ added Category:How-to guides.

2011-09-05T01:35:45Z

Return to How To Index: added Category:How-to guides.

← Older revision		Revision as of 01:35, 5 September 2011
Line 65:		Line 65:

	[[HowToGuides]]		[[HowToGuides]]

			[[Category:How-to guides]]

Pw3r: Debugging, test edit, please ignore

2010-12-03T04:42:41Z

Debugging, test edit, please ignore

← Older revision		Revision as of 04:42, 3 December 2010
Line 65:		Line 65:

	[[HowToGuides]]		[[HowToGuides]]


	~~Debugging, test edit, please ignore~~

Pw3r: Debugging, test edit, please ignore

2010-12-03T04:42:25Z

Debugging, test edit, please ignore

← Older revision		Revision as of 04:42, 3 December 2010
Line 65:		Line 65:

	[[HowToGuides]]		[[HowToGuides]]


			Debugging, test edit, please ignore

Windwalkr (legacy 2550) at 12:27, 8 March 2010

2010-03-08T12:27:24Z

← Older revision		Revision as of 12:27, 8 March 2010
Line 1:		Line 1:
	Assets need no be final once they are uploaded to the [[Download Station]] and can be easily updated. This guide details how to create a new version of an asset within [[Content Manager]].		Assets need not be final once they are uploaded to the [[Download Station]] and can be easily updated. This guide details how to create a new version of an asset within [[Content Manager]].


Line 10:		Line 10:
	===== KUID Version =====		===== KUID Version =====

	An ~~assets~~ [[KUID]] is used to uniquely identify an asset in the Trainz world. The KUID2 format introduced a version number to this identifier, allowing content creators to create a new version of an asset that would replace all older versions. When a new asset version is created [[Content Manager]] increments the version number by one.		An asset's [[KUID]] is used to uniquely identify an asset in the Trainz world. The KUID2 format introduced a version number to this identifier, allowing content creators to create a new version of an asset that would replace all older versions. When a new asset version is created [[Content Manager]] increments the version number by one.

	For example, if the original asset had a [[KUID]] of <KUID:123456:1000> the new version will be created with a [[KUID]] of <KUID2:123456:1000:1>. The 'KUID2' at the beginning indicates that this KUID is versioned, and the trailing '1' is the version number. Likewise the next version of the asset would have the [[KUID]] <KUID2:123456:1000:2>.		For example, if the original asset had a [[KUID]] of <KUID:123456:1000> the new version will be created with a [[KUID]] of <KUID2:123456:1000:1>. The 'KUID2' at the beginning indicates that this KUID is versioned, and the trailing '1' is the version number. Likewise the next version of the asset would have the [[KUID]] <KUID2:123456:1000:2>.
Line 18:		Line 18:

	===== Obsolete Table =====		===== Obsolete Table =====
	If you want to update an asset but have reached the maximum [[KUID]] version number you can do so using the [[~~TagName_obsolete~~-table~~\|obsolete table~~]]. This is done by first creating a new asset, with a new [[KUID]], then adding an [[~~TagName_obsolete~~-table~~\|obsolete table~~]].		If you want to update an asset but have reached the maximum [[KUID]] version number you can do so using the [["Obsolete-table" container]]. This is done by first creating a new asset, with a new [[KUID]], then adding an [["Obsolete-table" container]].

	The obsolete table takes the following format in the [[Config~~.txt_file\|config~~.txt]] file:		The obsolete table takes the following format in the [[Config.txt file]] file:
	obsolete-table		obsolete-table
	{		{
Line 31:		Line 31:
	== Restrictions ==		== Restrictions ==

	It is not allowable for multiple assets to obsolete a single source. In other words two assets cannot obsolete <KUID:123456:1000>, this would create undefined ~~and possibly unstable~~ behavior in game.		It is not allowable for multiple assets to obsolete a single source. In other words two assets cannot both obsolete <KUID:123456:1000>, this would create undefined behavior in game depending on what content is locally installed.

	Care must also be taken to ensure circular obsolescence is not created. An asset must not obsolete itself, either directly or indirectly. For example, consider the following [[Config~~.txt_file\|config~~.txt]] ~~files~~:		Care must also be taken to ensure circular obsolescence is not created. An asset must not obsolete itself, either directly or indirectly. For example, consider the following [[Config.txt file]]s:

	kuid <KUID2:123456:1000:1>		kuid <KUID2:123456:1000:1>
Line 47:		Line 47:
	}		}

	Creating two assets like this that obsolete each other can lead to unpredictable behavior. It must be avoided ~~with care~~.		Creating two assets like this that obsolete each other can lead to unpredictable behavior. It must be avoided.

	== Uploading Your New Version ==		== Uploading Your New Version ==

Pw3r: Creation of asset updating how to guide

2010-03-04T11:40:36Z

Creation of asset updating how to guide

New page

Assets need no be final once they are uploaded to the [[Download Station]] and can be easily updated. This guide details how to create a new version of an asset within [[Content Manager]].

== Creating a New Version ==
[[Image:CM_Create_New_Version.jpg|462px|thumb|right]]
To update an asset you have uploaded to the [[Download Station]], first select it in the main list view in [[Content Manager]]. Once selected, simply right click on the asset and choose "Create New Version".

This will create an exact copy of the asset and then update it to obsolete the old version. This is done in one of two ways:

===== KUID Version =====

An assets [[KUID]] is used to uniquely identify an asset in the Trainz world. The KUID2 format introduced a version number to this identifier, allowing content creators to create a new version of an asset that would replace all older versions. When a new asset version is created [[Content Manager]] increments the version number by one.

For example, if the original asset had a [[KUID]] of <KUID:123456:1000> the new version will be created with a [[KUID]] of <KUID2:123456:1000:1>. The 'KUID2' at the beginning indicates that this KUID is versioned, and the trailing '1' is the version number. Likewise the next version of the asset would have the [[KUID]] <KUID2:123456:1000:2>.

The maximum [[KUID]] version number is 127, beyond this you must use the obsolete table.

===== Obsolete Table =====
If you want to update an asset but have reached the maximum [[KUID]] version number you can do so using the [[TagName_obsolete-table|obsolete table]]. This is done by first creating a new asset, with a new [[KUID]], then adding an [[TagName_obsolete-table|obsolete table]].

The obsolete table takes the following format in the [[Config.txt_file|config.txt]] file:
obsolete-table
{
0 <KUID2:123456:1000:127>
1 <KUID2:123456:1001:127>
}

Each asset listed in the obsolete table will be replaced by the new asset in game. A single asset can obsolete as many assets as you like but should be of the same kind, basic functionality and appearance.

== Restrictions ==

It is not allowable for multiple assets to obsolete a single source. In other words two assets cannot obsolete <KUID:123456:1000>, this would create undefined and possibly unstable behavior in game.

Care must also be taken to ensure circular obsolescence is not created. An asset must not obsolete itself, either directly or indirectly. For example, consider the following [[Config.txt_file|config.txt]] files:

kuid <KUID2:123456:1000:1>
obsolete-table
{
0 <KUID:123456:2222>
}

kuid <KUID:123456:2222>
obsolete-table
{
0 <KUID2:123456:1000:1>
}

Creating two assets like this that obsolete each other can lead to unpredictable behavior. It must be avoided with care.

== Uploading Your New Version ==

Other than obsoleting the original, the new asset will be an exact replica. You can make any changes you like and upload the new version to the [[Download Station]] as normal. New asset versions should not change the behavior or style of the content in any way, they are used to make improvements and fix errors only.

For more information on uploading assets to the [[Download Station]], see the how to guide [[HowTo/Upload_a_new_asset_to_the_DownloadStation|here]].

== See Also ==
* [[HowTo/Upload a new asset to the DownloadStation]]
* [[KUID]]
* [[Download Station]]
* [[Content Manager]]

== Return to How To Index ==

[[HowToGuides]]