HowTo/Scenery/kuid
(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...") |
(→KUID) |
||
| 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 | + | 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 | ||
Revision as of 09:58, 5 February 2022
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 <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 line in your config file for the KUID would be kuid <KUID:000:0000>
or
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. 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 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
