HowTo/Scenery/kuid - Revision history

Glt0145 at 23:45, 8 February 2022

2022-02-08T23:45:32Z

← Older revision		Revision as of 23:45, 8 February 2022
Line 27:		Line 27:

	This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.		This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.
	The word "~~kuid~~" which identifies what it is and tells Trainz to expect three sets of numbers		The word "kuid2" which identifies what it is and tells Trainz to expect three sets of numbers

	The first User_ID is your used ID number that you would have been given when you first registered your Trainz		The first User_ID is your used ID number that you would have been given when you first registered your Trainz

Glt0145: /* KUID */

2022-02-05T04:04:05Z

KUID

← Older revision		Revision as of 04:04, 5 February 2022
Line 33:		Line 33:
	The second Content_ID is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet.		The second Content_ID is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet.

	The third Version_ID is the version number. These normally start with version 0. If you create an update to an asset the next number in sequence would be used example 2. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.		The third Version_ID is the version number. These normally start with version 0. If you create an update to an asset the next number in sequence would be used example 1. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.

	An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:0>. The next one KUID for an updated asset would be <KUID2:0000:00000:1>		An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:0>. The next one KUID for an updated asset would be <KUID2:0000:00000:1>

	Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs		Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs

Glt0145: /* KUID */

2022-02-05T04:03:29Z

KUID

← Older revision		Revision as of 04:03, 5 February 2022
Line 7:		Line 7:
	Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.		Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.

	kuid <~~KUID~~:~~#####~~:~~#####~~>		kuid <kuid:User_ID:Content_ID:>

	This ~~KUID~~ was the original used by the early trainz versions. it consist of there parts		This kuid was the original used by the early trainz versions. it consist of there parts

	The word "~~KUID~~" which identifies what it is.		The word "kuid" which identifies what it is.

	The first ~~####~~ is your used ID number that you would have been given when you first registered your Trainz		The first User_ID is your used ID number that you would have been given when you first registered your Trainz

	The second ~~####~~ is a unique identifier that you create for your asset. Each asset you create must have it's own unique identifier. It easiest to keep track of your identifiers in a spreadsheet		The second Version_ID is a unique identifier that you create for your asset. Each asset you create must have it's own unique identifier. It easiest to keep track of your identifiers in a spreadsheet

	If you use this format for you config file and update to the asset would need to have a new unique identifier.		If you use this format for you config file and update to the asset would need to have a new unique identifier.
Line 24:		Line 24:
	or		or

	kuid <KUID2:~~####~~:~~#####~~:#>		kuid <KUID2:User_ID:Content_ID:Version_ID>

	This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.		This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.
	The word "~~KUID2~~" which identifies what it is and tells Trainz to expect three sets of numbers		The word "kuid" which identifies what it is and tells Trainz to expect three sets of numbers
	~~The first #### is your used ID number that you would have been given when you first registered your Trainz~~
	~~The second #### is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet.~~
	The third is the version number. These normally start with version 1. If you create an update to an asset the next number in sequence would be used example 2. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.

	An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:1>. The next one KUID for an updated asset would be <KUID2:0000:00000:1>		The first User_ID is your used ID number that you would have been given when you first registered your Trainz

			The second Content_ID is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet.

			The third Version_ID is the version number. These normally start with version 0. If you create an update to an asset the next number in sequence would be used example 2. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.

			An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:0>. The next one KUID for an updated asset would be <KUID2:0000:00000:1>

	Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs		Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs

Glt0145 at 01:35, 5 February 2022

2022-02-05T01:35:16Z

← Older revision		Revision as of 01:35, 5 February 2022
Line 2:		Line 2:
	== KUID ==		== KUID ==

	'''This tag is compulsory. ~~Without it the config file and asset is not usable by trainz~~'''		'''This tag is compulsory.'''

Glt0145 at 01:32, 5 February 2022

2022-02-05T01:32:59Z

← Older revision		Revision as of 01:32, 5 February 2022
Line 1:		Line 1:

	== KUID ==		== KUID ==

			'''This tag is compulsory. Without it the config file and asset is not usable by trainz'''


	Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.		Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.

Glt0145: /* KUID */

2022-02-04T23:58:57Z

KUID

← Older revision		Revision as of 23:58, 4 February 2022
Line 3:		Line 3:
	Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.		Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.

	<KUID:#####:#####>		kuid <KUID:#####:#####>

	This KUID was the original used by the early trainz versions. it consist of there parts		This KUID was the original used by the early trainz versions. it consist of there parts

Line 15:		Line 16:

	The text in you config file for this type of KUID has to have the chevrons <> at the start and finish the text string. without them the trainz importer will throw an error		The text in you config file for this type of KUID has to have the chevrons <> at the start and finish the text string. without them the trainz importer will throw an error
	and example of the KUID would be <KUID:000:0000>		and example of the line in your config file for the KUID would be kuid <KUID:000:0000>

	or		or

	<KUID2:####:#####:#>		kuid <KUID2:####:#####:#>

	This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.		This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.
	The word "KUID2" which identifies what it is and tells Trainz to expect three sets of numbers		The word "KUID2" which identifies what it is and tells Trainz to expect three sets of numbers
Line 26:		Line 28:
	The third is the version number. These normally start with version 1. If you create an update to an asset the next number in sequence would be used example 2. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.		The third is the version number. These normally start with version 1. If you create an update to an asset the next number in sequence would be used example 2. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.

	An example of ~~this~~ KUID is <KUID2:0000:00000:1>. The next one for an updated asset would be <KUID2:0000:00000:1>		An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:1>. The next one KUID for an updated asset would be <KUID2:0000:00000:1>

	Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs		Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs

Glt0145: Created page with " == KUID == Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms. This KUID was..."

2022-02-04T23:53:24Z

Created page with " == KUID == Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms. <KUID:#####:#####> This KUID was..."

New page

== KUID ==
Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.

<KUID:#####:#####>
This KUID was the original used by the early trainz versions. it consist of there parts

The word "KUID" which identifies what it is.

The first #### is your used ID number that you would have been given when you first registered your Trainz

The second #### is a unique identifier that you create for your asset. Each asset you create must have it's own unique identifier. It easiest to keep track of your identifiers in a spreadsheet

If you use this format for you config file and update to the asset would need to have a new unique identifier.

The text in you config file for this type of KUID has to have the chevrons <> at the start and finish the text string. without them the trainz importer will throw an error
and example of the KUID would be <KUID:000:0000>

or

<KUID2:####:#####:#>
This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original.
The word "KUID2" which identifies what it is and tells Trainz to expect three sets of numbers
The first #### is your used ID number that you would have been given when you first registered your Trainz
The second #### is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet.
The third is the version number. These normally start with version 1. If you create an update to an asset the next number in sequence would be used example 2. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.

An example of this KUID is <KUID2:0000:00000:1>. The next one for an updated asset would be <KUID2:0000:00000:1>

Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs