Help:Importing Content - Revision history

Deneban: /* Further Information */

2020-05-19T16:36:16Z

Further Information

← Older revision		Revision as of 16:36, 19 May 2020
Line 113:		Line 113:
	* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.		* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.
	** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.		** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.
	** <b>Rulers</b> are known to lock up the loading of a TS12-created routes into TRS19. It is suggested all rulers in a route be deleted in their native Trainz release before attempting to transfer the route to TANE SP1 or later Trainz releases. As rulers are layer-resident entities, you should unhide and unlock all layers when performing the ruler deletion operation.		** ... that being said, <b>Rulers</b> are known to lock up the loading of a TS12-created routes into TRS19. It is suggested all rulers in a route be deleted in their native Trainz release before attempting to transfer the route to TANE SP1 or later Trainz releases. As rulers are layer-resident entities, you should unhide and unlock all layers when performing the ruler deletion operation.
	* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,		* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,
	** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').		** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').

Deneban: /* Further Information */

2020-05-19T16:34:27Z

Further Information

← Older revision		Revision as of 16:34, 19 May 2020
Line 113:		Line 113:
	* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.		* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.
	** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.		** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.
	** <b>Rulers</b> are known to lock up the loading of a TS12-created routes into TRS19. It is suggested all rulers in a route be deleted in their native Trainz release before attempting to transfer the route to TANE SP1 or later Trainz releases.		** <b>Rulers</b> are known to lock up the loading of a TS12-created routes into TRS19. It is suggested all rulers in a route be deleted in their native Trainz release before attempting to transfer the route to TANE SP1 or later Trainz releases. As rulers are layer-resident entities, you should unhide and unlock all layers when performing the ruler deletion operation.
	* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,		* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,
	** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').		** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').

Deneban: /* Further Information */ added warning about rulers

2020-05-19T16:31:13Z

Further Information: added warning about rulers

← Older revision		Revision as of 16:31, 19 May 2020
Line 113:		Line 113:
	* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.		* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.
	** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.		** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.
			** <b>Rulers</b> are known to lock up the loading of a TS12-created routes into TRS19. It is suggested all rulers in a route be deleted in their native Trainz release before attempting to transfer the route to TANE SP1 or later Trainz releases.
	* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,		* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,
	** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').		** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').

Zikchil at 15:10, 22 January 2020

2020-01-22T15:10:18Z

← Older revision		Revision as of 15:10, 22 January 2020
Line 1:		Line 1:
	TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz so it is possible to import your content from TANE into TRS2019 (and even from one build of TRS2019 into a new one).

	It is important to know that TRS2019 requires the original textures to show correctly in-game, and therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty'). All DLC packs are expected to become available for TRS2019 via the Asset Download tool after TRS2019 is fully released (may not be available during Early Access).

	~~Built-in content from TS2010 and earlier (excluding routes that were new in TS2010) is available from the Download Station.~~

	~~We are in the process of preparing the TS12 and TS2010 routes for downloading.~~


	==Recommended Methods of Transferring Content==		==Recommended Methods of Transferring Content==
	There are several different methods that can be used to transfer content between different installations/versions of Trainz. Some are more suitable for smaller amounts of content, whilst others are suited to large amounts of content.		There are several different methods that can be used to transfer content between different installations/versions of Trainz. Some are more suitable for smaller amounts of content, whilst others are suited to large amounts of content.
Line 14:		Line 5:

	<div style="background-color: #ff9797;border-style: dotted; width:800px; overflow:auto; ">		<div style="background-color: #ff9797;border-style: dotted; width:800px; overflow:auto; ">
	DO NOT attempt to transfer content marked as ‘payware’ or ‘built-in’ manually as it will not include the textures and will show as faulty.<br>		* DO NOT attempt to transfer content marked as ‘payware’ or ‘built-in’ manually as it will not include the textures and will show as faulty.<br>
	This content is downloaded via in-game Asset Download window. <br>		* This content is downloaded via in-game Asset Download window. <br>
	</div>		</div>

Line 108:		Line 99:

	<div style="background-color: #ff9797;border-style: dotted; width:800px; overflow:auto; ">		<div style="background-color: #ff9797;border-style: dotted; width:800px; overflow:auto; ">
	Do NOT attempt to transfer assets from previous versions over into TRS2019 by simply copying your LocalData folders or creating .cdps. The format of the LocalData folders may not be compatible with TRS2019.		* Do NOT attempt to transfer assets from previous versions over into TRS2019 by simply copying your LocalData folders or creating .cdps.
			** The format of the LocalData folders may not be compatible with TRS2019.

			* You must not set TRS19 to use the LocalData folder for Trainz: A New Era or any other version of Trainz.
			** Doing so can cause Trainz to become unstable, or cease to function correctly, and may damage any content in the LocalData folder.

	~~You must not set TRS19 to use~~ the ~~LocalData folder for Trainz~~: ~~A New Era or any other version of Trainz~~. ~~Doing so can cause Trainz to become unstable, or cease to function correctly, and may damage any content in the LocalData folder~~.		*Please note that the following items cannot be imported into TRS2019 directly:
			** .ja files
			** .tzarc files
			</div>

	~~Please note that the following items cannot be imported into TRS2019 directly:~~

	* .~~ja files~~		* TRS2019 has been designed to be backwards compatible with the majority of content from previous versions of Trainz.
	* .~~tzarc files~~		** ...so it is possible to import your content from TANE into TRS2019 and even from one build of TRS2019 into a new one.
	</~~div~~>		* <b>Important</b> : TRS2019 requires the original textures to show correctly in-game,
			** ...therefore built-in content and DLC content, which does not contain source files, cannot be imported directly (or it will become 'faulty').
			* Built-in content from TS2010 and earlier (excluding routes that were new in TS2010) is available from the Download Station.
			** We are in the process of preparing the TS12 and TS2010 routes for downloading.

Gliuk28: /* Transferring via CDP files (Easiest) */

2020-01-16T11:22:30Z

Transferring via CDP files (Easiest)

← Older revision		Revision as of 11:22, 16 January 2020
Line 39:		Line 39:

	==Transferring via CDP files (Easiest)==		==Transferring via CDP files (Easiest)==
	One method you can use is to save your content to a cdp file, or cdp files, and then import this into TRS2019. Note: cdp files should not be made larger than 500MB in size, so as to ensure that the file does not become corrupted and can be imported successfully by Trainz.		One method you can use is to save your content to a cdp file, or cdp files, and then import this into TRS2019.
			Note: '''cdp files should not be made larger than 500MB in size''', so as to ensure that the file does not become corrupted and can be imported successfully by Trainz.

	This method is recommended for transferring smaller numbers of assets, or individual assets.		This method is recommended for transferring smaller numbers of assets, or individual assets.
Line 57:		Line 58:

	The content will then be installed. You can import multiple cdp files at the same time.		The content will then be installed. You can import multiple cdp files at the same time.


	==Transferring via 'Open for Edit' (Better for transferring a large amount of content)==		==Transferring via 'Open for Edit' (Better for transferring a large amount of content)==

Zikchil: /* Transferring via 'Open for Edit' (Better for transferring a large amount of content) */

2019-10-03T13:52:36Z

Transferring via 'Open for Edit' (Better for transferring a large amount of content)

← Older revision		Revision as of 13:52, 3 October 2019
Line 62:		Line 62:
	I. For importing large amounts of content, we recommend the following approach for importing content from your older installation of Trainz:		I. For importing large amounts of content, we recommend the following approach for importing content from your older installation of Trainz:

	# Open Trainz Content or Content Manager in your previous installation of Trainz		#Open Trainz Content or Content Manager (CM) in your previous installation of Trainz
	# Locate an asset you wish to transfer		#Locate an asset you wish to transfer
	# Right click on the asset, then go to 'Open'		#Right click on the asset, then go to 'Open'
	# Click on 'Open for Editing'		#*SHFT+LMB to select multiple assets.
	# Repeat for all other assets you wish to transfer.		#Click on 'Open for Editing'
	*When you have opened for edit every asset you wish to transfer, right click on one of the assets, then go to 'open' and click on 'Show in Explorer' or 'Show in Finder'.		#Repeat for all other assets you wish to transfer.
	*You should then see an Explorer/Finder window open showing the open asset. Go to the 'Address' bar at the top, and click on the folder called 'Editing'. This will show all of the open for edit assets.		#*When you have opened for edit every asset you wish to transfer, right click on <i><b><u>one of the assets</u></b></i>, then go to 'open' and click on 'Show in Explorer' or 'Show in Finder'.
			#*You should then see an Explorer/Finder window open showing the open asset. Go to the 'Address' bar at the top, and click on the folder called 'Editing'. This will show all of the open for edit assets.
			#You may now exit this 'source' version of Trainz.
	<br>		<br>
	II. To import the content, follow these steps:		II. To import the content, follow these steps:
	# Open TRS2019's Trainz Content (content manager) tool by clicking on 'Manage Content' on the launcher		#Open TRS2019's Trainz Content (content manager) tool by clicking on 'Manage Content' on the launcher
	# Select all of the folders within the 'Editing' folder in Explorer/Finder		#Select all of the folders within the 'Editing' folder in Explorer/Finder
	# Drag and Drop these into the Trainz Content window		#Drag and Drop these into the Trainz Content window
	*The content will then be imported into TRS2019.		#*The content will then be imported into TRS2019.
			#*If you plan on maintaining the original copy of Trainz, remember to go back and resolve any 'open for editing' (OFE) assets.
			#*You may do this by custom filtering CM on 'OFE = true' and clicking "revert to original".
	<br>		<br>
	III. ''An alternative option'', once you have opened your assets for edit, is to find the location of your Local Data folder and then import directly from this using the ‘import content folder’ tool. This is done by following these steps:		III. ''An alternative option'', once you have opened your assets for edit, is to find the location of your Local Data folder and then import directly from this using the ‘import content folder’ tool. This is done by following these steps:

	# Open the launcher screen for your previous installation of Trainz		#Open the launcher screen for your previous installation of Trainz
	# Click on Trainz Settings		#Click on Trainz Settings
	# Click on the ‘Install’ tab		#Click on the ‘Install’ tab
	# Your Local Data location will then be shown in the ‘Local Data’ path box. The last folder in the path will be named ‘build xxxxxxxxx’ (the Xs will be random letters and numbers)		#Your Local Data location will then be shown in the ‘Local Data’ path box. The last folder in the path will be named ‘build xxxxxxxxx’ (the Xs will be random letters and numbers)
	# Open the launcher screen for TRS2019		#Open the launcher screen for TRS2019
	# Click on Manage Content		#Click on Manage Content
	# Click on ‘File’ at the top of the screen, then click on ‘import content folder’		#Click on ‘File’ at the top of the screen, then click on ‘import content folder’
	# Go to the location that was shown in the install tab of your previous installation		#Go to the location that was shown in the install tab of your previous installation
	# Click on the ‘Editing’ folder in the ‘build xxxxxxxxx’ folder		#Click on the ‘Editing’ folder in the ‘build xxxxxxxxx’ folder
	# Click on ‘Open’		#Click on ‘Open’
	# Your content will then be imported into TRS2019.		#Your content will then be imported into TRS2019.

	==Dependencies==		==Dependencies==

Zikchil: /* Transferring via 'Open for Edit' (Better for transferring a large amount of content) */

2019-10-01T18:30:34Z

Transferring via 'Open for Edit' (Better for transferring a large amount of content)

← Older revision		Revision as of 18:30, 1 October 2019
Line 87:		Line 87:
	# Go to the location that was shown in the install tab of your previous installation		# Go to the location that was shown in the install tab of your previous installation
	# Click on the ‘Editing’ folder in the ‘build xxxxxxxxx’ folder		# Click on the ‘Editing’ folder in the ‘build xxxxxxxxx’ folder
	# ~~click~~ on ‘Open’		# Click on ‘Open’
	# Your content will then be imported into TRS2019.		# Your content will then be imported into TRS2019.

Zikchil: /* Transferring via 'Open for Edit' (Better for transferring a large amount of content) */

2019-10-01T18:30:03Z

Transferring via 'Open for Edit' (Better for transferring a large amount of content)

← Older revision		Revision as of 18:30, 1 October 2019
Line 60:		Line 60:

	==Transferring via 'Open for Edit' (Better for transferring a large amount of content)==		==Transferring via 'Open for Edit' (Better for transferring a large amount of content)==
	For importing large amounts of content, we recommend the following approach for importing content from your older installation of Trainz:		I. For importing large amounts of content, we recommend the following approach for importing content from your older installation of Trainz:

	# Open Trainz Content or Content Manager in your previous installation of Trainz		# Open Trainz Content or Content Manager in your previous installation of Trainz
Line 67:		Line 67:
	# Click on 'Open for Editing'		# Click on 'Open for Editing'
	# Repeat for all other assets you wish to transfer.		# Repeat for all other assets you wish to transfer.
			*When you have opened for edit every asset you wish to transfer, right click on one of the assets, then go to 'open' and click on 'Show in Explorer' or 'Show in Finder'.
	When you have opened for edit every asset you wish to transfer, right click on one of the assets, then go to 'open' and click on 'Show in Explorer' or 'Show in Finder'.		*You should then see an Explorer/Finder window open showing the open asset. Go to the 'Address' bar at the top, and click on the folder called 'Editing'. This will show all of the open for edit assets.
			<br>
	You should then see an Explorer/Finder window open showing the open asset. Go to the 'Address' bar at the top, and click on the folder called 'Editing'. This will show all of the open for edit assets.		II. To import the content, follow these steps:



	To import the content, follow these steps:
	# Open TRS2019's Trainz Content (content manager) tool by clicking on 'Manage Content' on the launcher		# Open TRS2019's Trainz Content (content manager) tool by clicking on 'Manage Content' on the launcher
	# Select all of the folders within the 'Editing' folder in Explorer/Finder		# Select all of the folders within the 'Editing' folder in Explorer/Finder
	# Drag and Drop these into the Trainz Content window		# Drag and Drop these into the Trainz Content window
			*The content will then be imported into TRS2019.
	The content will then be imported into TRS2019.		<br>
			III. ''An alternative option'', once you have opened your assets for edit, is to find the location of your Local Data folder and then import directly from this using the ‘import content folder’ tool. This is done by following these steps:
	An alternative option, once you have opened your assets for edit, is to find the location of your ~~LocalData~~ folder and then import directly from this using the ‘import content folder’ tool. This is done by following these steps:

	# Open the launcher screen for your previous installation of Trainz		# Open the launcher screen for your previous installation of Trainz
	# Click on Trainz Settings		# Click on Trainz Settings
	# Click on the ‘Install’ tab		# Click on the ‘Install’ tab
	# Your ~~LocalData~~ location will then be shown in the ~~‘LocalData’~~ path box. The last folder in the path will be named ‘build xxxxxxxxx’ (the Xs will be random letters and numbers)		# Your Local Data location will then be shown in the ‘Local Data’ path box. The last folder in the path will be named ‘build xxxxxxxxx’ (the Xs will be random letters and numbers)
	# Open the launcher screen for TRS2019		# Open the launcher screen for TRS2019
	# Click on Manage Content		# Click on Manage Content

Zikchil: /* Recommended Methods of Transferring Content */

2019-07-17T00:03:45Z

Recommended Methods of Transferring Content

← Older revision		Revision as of 00:03, 17 July 2019
Line 18:		Line 18:
	</div>		</div>

	It is also recommended that content marked as ‘installed from DLS’ be downloaded again, see [[#Content from the Download Station\|Content From Download Station]].		It is also recommended that content marked as ‘installed from DLS’ be downloaded again, see section [[#Content from the Download Station\|Content From Download Station]].

Zikchil: /* Recommended Methods of Transferring Content */

2019-07-17T00:02:26Z

Recommended Methods of Transferring Content

← Older revision		Revision as of 00:02, 17 July 2019
Line 18:		Line 18:
	</div>		</div>

	It is also recommended that content marked as ‘installed from DLS’ be downloaded again, see [[#Content from Download Station\|Content From Download Station]].		It is also recommended that content marked as ‘installed from DLS’ be downloaded again, see [[#Content from the Download Station\|Content From Download Station]].