Help:Delete Missing Assets - Revision history

Pw3r at 02:35, 10 November 2021

2021-11-10T02:35:26Z

← Older revision		Revision as of 02:35, 10 November 2021
Line 36:		Line 36:


	~~===~~Return To:~~===~~		'''Return To:'''
	*[[Help:Surveyor_MenuTools\|Surveyor MenuTools]]		*[[Help:Surveyor_MenuTools\|Surveyor MenuTools]]
	*[[Help:Replacing_Missing_Assets\|Replace Missing Assets]]		*[[Help:Replacing_Missing_Assets\|Replace Missing Assets]]

Pw3r at 02:34, 10 November 2021

2021-11-10T02:34:24Z

← Older revision		Revision as of 02:34, 10 November 2021
Line 36:		Line 36:


	Return To:		===Return To:===
	*[[Help:Surveyor_MenuTools\|Surveyor MenuTools]]		*[[Help:Surveyor_MenuTools\|Surveyor MenuTools]]
	*[[Help:Replacing_Missing_Assets\|Replace Missing Assets]]		*[[Help:Replacing_Missing_Assets\|Replace Missing Assets]]

Pw3r at 02:34, 10 November 2021

2021-11-10T02:34:10Z

@@ Line 1: / Line 1: @@
 ==Delete Missing Assets==
 Delete Missing Assets (DMA) is a Surveyor command that performs a number of Route/Session repair tasks. The most obvious of these is to remove references to assets which are not available in the local installation (i.e. "Missing Assets"), but there's a lot more to it than that.
 ===Missing Assets===
@@ Line 31: / Line 33: @@
 ===Extra Notes===
-After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption. No part of DMA supports undo and the operation runs over the entire map, so a backup should always be made before it is used.
+After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption.

Pw3r: /* Named Object Table */

2021-11-10T02:33:15Z

Named Object Table

← Older revision		Revision as of 02:33, 10 November 2021
Line 29:		Line 29:
	====Named Object Table====		====Named Object Table====
	The Named Object Table is a system in Trainz code/script which stores data about certain object types. Think of it as a phone book for objects, which script can use to list objects of particular types/names, or to find specific objects in the world. The final step of DMA is to rebuild this table, in case it's been corrupted, objects have moved tiles, etc.		The Named Object Table is a system in Trainz code/script which stores data about certain object types. Think of it as a phone book for objects, which script can use to list objects of particular types/names, or to find specific objects in the world. The final step of DMA is to rebuild this table, in case it's been corrupted, objects have moved tiles, etc.


	===Extra Notes===		===Extra Notes===
	After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption. No part of DMA supports undo and the operation runs over the entire map, so a backup should always be made before it is used.		After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption. No part of DMA supports undo and the operation runs over the entire map, so a backup should always be made before it is used.

Pw3r: /* Track Status */

2021-11-10T02:31:47Z

Track Status

← Older revision		Revision as of 02:31, 10 November 2021
Line 20:		Line 20:

	====Track Status====		====Track Status====
	A number of track stretch and track vertex status flags will also be validated during DMA. This can be used to fix cases of corrupt/invalid data caused by having previously loaded and saved the map with missing dependencies~~, but such~~ cases are not too common and usually ~~fairly minor in consequence~~. Examples include gradient flagging on track/vertices and bridge/tunnel status.		A number of track stretch and track vertex status flags will also be validated during DMA. This can be used to fix cases of corrupt/invalid data caused by having previously loaded and saved the map with missing dependencies. Such cases are not too common and usually have minimal consequences, but are easy for DMA to fix. Examples include gradient flagging on track/vertices and bridge/tunnel status.

	In addition, the game will also validate track stretch length, and remove stretches which are overly long (currently >15km).		In addition, the game will also validate track stretch length, and remove stretches which are overly long (currently >15km).

Pw3r: /* Track Status */

2021-11-10T02:30:55Z

Track Status

← Older revision		Revision as of 02:30, 10 November 2021
Line 20:		Line 20:

	====Track Status====		====Track Status====
	A number of track stretch and track vertex status flags will also be validated during DMA. This can be used to fix cases of ~~corruption~~/invalid-data caused by having previously loaded and saved the map with missing dependencies, but such cases are not too common and usually fairly minor in consequence. Examples include gradient flagging on track/vertices and bridge/tunnel status.		A number of track stretch and track vertex status flags will also be validated during DMA. This can be used to fix cases of corrupt/invalid data caused by having previously loaded and saved the map with missing dependencies, but such cases are not too common and usually fairly minor in consequence. Examples include gradient flagging on track/vertices and bridge/tunnel status.

	In addition, the game will also validate track stretch length, and remove stretches which are overly long (currently >15km).		In addition, the game will also validate track stretch length, and remove stretches which are overly long (currently >15km).

Pw3r: /* Track Status */

2021-11-10T02:30:38Z

Track Status

← Older revision		Revision as of 02:30, 10 November 2021
Line 20:		Line 20:

	====Track Status====		====Track Status====
	A number of track stretch and track vertex status flags will also be validated during DMA. This can be used to fix cases of corruption/invalid data caused by having previously loaded and saved the map with missing dependencies, but such cases are not too common and usually fairly minor in consequence. Examples include gradient flagging on track/vertices and bridge/tunnel status.		A number of track stretch and track vertex status flags will also be validated during DMA. This can be used to fix cases of corruption/invalid-data caused by having previously loaded and saved the map with missing dependencies, but such cases are not too common and usually fairly minor in consequence. Examples include gradient flagging on track/vertices and bridge/tunnel status.

	In addition, the game will also validate track stretch length, and remove stretches which are overly long (currently >15km).		In addition, the game will also validate track stretch length, and remove stretches which are overly long (currently >15km).

Pw3r at 02:29, 10 November 2021

2021-11-10T02:29:26Z

← Older revision		Revision as of 02:29, 10 November 2021
Line 10:		Line 10:
	In addition to removing missing assets DMA runs a number of map repair tasks, detailed further below. Some of these tasks may modify the Route in ways that will break dependent Sessions, so always make a backup		In addition to removing missing assets DMA runs a number of map repair tasks, detailed further below. Some of these tasks may modify the Route in ways that will break dependent Sessions, so always make a backup

	====Asset ~~versions~~====		====Asset Versions====
	During DMA items may be updated to reference the currently loaded asset version. This can be handy for ensuring the map is dependent on the actual content versions being used by the route creator, rather than some older asset version, but it also means that other players may need to download new dependent content in order to use an update map.		During DMA items may be updated to reference the currently loaded asset version. This can be handy for ensuring the map is dependent on the actual content versions being used by the route creator, rather than some older asset version, but it also means that other players may need to download new dependent content in order to use an update map.

Pw3r at 02:28, 10 November 2021

2021-11-10T02:28:08Z

← Older revision		Revision as of 02:28, 10 November 2021
Line 1:		Line 1:
	==Delete Missing Assets==		==Delete Missing Assets==
	Delete Missing Assets (DMA) is a Surveyor command that performs a number of Route/Session repair tasks. The most obvious of these is to remove references to assets which are not available in the local installation (i.e. "Missing Assets"), but there's a lot more to it than that~~. No part of DMA supports undo and the operation runs over the entire map, so a backup should always be made before it is used.~~		Delete Missing Assets (DMA) is a Surveyor command that performs a number of Route/Session repair tasks. The most obvious of these is to remove references to assets which are not available in the local installation (i.e. "Missing Assets"), but there's a lot more to it than that.

	After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption.

	===Missing Assets===		===Missing Assets===
Line 31:		Line 29:
	====Named Object Table====		====Named Object Table====
	The Named Object Table is a system in Trainz code/script which stores data about certain object types. Think of it as a phone book for objects, which script can use to list objects of particular types/names, or to find specific objects in the world. The final step of DMA is to rebuild this table, in case it's been corrupted, objects have moved tiles, etc.		The Named Object Table is a system in Trainz code/script which stores data about certain object types. Think of it as a phone book for objects, which script can use to list objects of particular types/names, or to find specific objects in the world. The final step of DMA is to rebuild this table, in case it's been corrupted, objects have moved tiles, etc.


			===Extra Notes===
			After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption. No part of DMA supports undo and the operation runs over the entire map, so a backup should always be made before it is used.

Pw3r at 02:27, 10 November 2021

2021-11-10T02:27:15Z

← Older revision		Revision as of 02:27, 10 November 2021
Line 3:		Line 3:

	After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption.		After DMA completes it will display a dialog showing details of any corruption that was found and fixed. It's a good idea to examine this thoroughly, as it may provide important information about follow up work you may need to undertake to repair removed corruption.


	===Missing Assets===		===Missing Assets===
Line 9:		Line 8:

	As noted, any failure to load an asset will result in things being removed, the asset does not have to be literally "missing". This includes assets which are uninstalled, faulty, missing dependencies, unauthorised (payware), incompatible (due to build number or other restrictions), or even just locally disabled.		As noted, any failure to load an asset will result in things being removed, the asset does not have to be literally "missing". This includes assets which are uninstalled, faulty, missing dependencies, unauthorised (payware), incompatible (due to build number or other restrictions), or even just locally disabled.


	===Other Repair Tasks===		===Other Repair Tasks===