HowTo/Fix Errors and Warnings - Revision history

Darkrose289: /* Notes */ formatting

2025-12-30T21:44:04Z

Notes: formatting

← Older revision		Revision as of 21:44, 30 December 2025
Line 88:		Line 88:
	<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br /><br />		<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br /><br />

	: <span id="Notes3~~" style="color: #FFC300; font-weight: bold;~~">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br /><br />		: <span id="Notes3">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br /><br />

	: <span id="Notes4~~" style="color: #FFC300; font-weight: bold;~~">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br /><br />		: <span id="Notes4">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br /><br />

	: <span id="Notes5~~" style="color: #FFC300; font-weight: bold;~~">5.</span> Before you disable or delete obsolete assets you should:		: <span id="Notes5">5.</span> Before you disable or delete obsolete assets you should:
	::: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.		::: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.
	::: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.		::: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.

Darkrose289: /* Error and Warning messages */ corrections

2025-12-30T21:42:13Z

Error and Warning messages: corrections

← Older revision		Revision as of 21:42, 30 December 2025
Line 42:		Line 42:

	== Error and Warning messages ==		== Error and Warning messages ==
	This is a compilation of validation an messages that occur during asset validation. The first three are from the Trainz Forum under the thread [https://forums.auran.com/threads/can-you-top-this-trs22-patch.177370/ Can you top this TRS22 Patch?]. Thank you to <span style="color: #00b050; font-weight: bold;">K3JohnHO</span> for starting the discussion thread and <span style="color: #00b050; font-weight: bold;">wreeder</span> and <span style="color: #00b050; font-weight: bold;">JCitron</span> for their replies in the thread. Before adding new messages to this table, please check the TS2009 Wiki to see if it has a page already (e.g., [[Validation Errors]]).		This is a compilation, although not an exhaustive list, of validation messages that may occur during asset validation. The first three are from the Trainz Forum under the thread [https://forums.auran.com/threads/can-you-top-this-trs22-patch.177370/ Can you top this TRS22 Patch?]. Thank you to <span style="color: #00b050; font-weight: bold;">K3JohnHO</span> for starting the discussion thread and <span style="color: #00b050; font-weight: bold;">wreeder</span> and <span style="color: #00b050; font-weight: bold;">JCitron</span> for their replies in the thread. Before adding new messages to this table, please check the TS2009 Wiki to see if it has a page already (e.g., [[Validation Errors]]).

	{\| class="wikitable"		{\| class="wikitable"

Darkrose289: /* Notes */ fomatting

2025-12-30T21:39:02Z

Notes: fomatting

← Older revision		Revision as of 21:39, 30 December 2025
Line 82:		Line 82:

	== Notes ==		== Notes ==
	<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.<br /><br />		: <span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.<br /><br />

	<span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V. <br /><br />		: <span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V. <br /><br />

	<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br /><br />		<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br /><br />

	<span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br /><br />		: <span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br /><br />

	<span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br /><br />		: <span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br /><br />

	<span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:		: <span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:
	:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.		::: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.
	:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.		::: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.

Darkrose289: /* Notes */

2025-12-30T21:37:05Z

Notes

← Older revision		Revision as of 21:37, 30 December 2025
Line 82:		Line 82:

	== Notes ==		== Notes ==
	<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.<br />		<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.<br /><br />

	<span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V. <br />		<span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V. <br /><br />

	<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br />		<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br /><br />

	<span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br />		<span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br /><br />

	<span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br />		<span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br /><br />

	<span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:		<span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:
	:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.		:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.
	:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.		:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.
	~~<br />~~

	[[#top\|Top]]		[[#top\|Top]]

Darkrose289: /* Notes */

2025-12-30T21:35:00Z

Notes

← Older revision		Revision as of 21:35, 30 December 2025
Line 82:		Line 82:

	== Notes ==		== Notes ==
	<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.		<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.<br />

	<span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V.		<span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V. <br />

	<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''		<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''<br />

	<span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).		<span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).<br />

	<span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.		<span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.<br />

	<span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:		<span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:
	:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.		:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.
	:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.		:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.
			<br />

	[[#top\|Top]]		[[#top\|Top]]

Darkrose289: /* Notes */ got rid of table for this section

2025-12-30T21:33:51Z

Notes: got rid of table for this section

← Older revision		Revision as of 21:33, 30 December 2025
Line 82:		Line 82:

	== Notes ==		== Notes ==
	~~{\| class="wikitable" width="100%"~~		<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.
	\|-
	\|<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.		<span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V.
	\|-
	\| <span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V.		<span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''
	\|-
	\| <span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''		<span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).
	\|-
	\| <span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).		<span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.
	\|-
	\| <span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.		<span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:
	\|-
	\| <span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:
	:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.		:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.
	:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.		:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.
	\|}

	[[#top\|Top]]		[[#top\|Top]]



	[[Category:How-to_guides\|HowTo Guides]]		[[Category:How-to_guides\|HowTo Guides]]

Darkrose289: /* Notes */

2025-12-30T21:21:12Z

Notes

← Older revision		Revision as of 21:21, 30 December 2025
Line 95:		Line 95:
	\|-		\|-
	\| <span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:		\| <span id="Notes5" style="color: #FFC300; font-weight: bold;">5.</span> Before you disable or delete obsolete assets you should:
	:: a. '''''check for dependencies (recursively)''''' for assets you created and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset. ~~If obsolete assets are listed try to get a~~		:: a. '''''check for dependencies (recursively)''''' for assets you created (especially routes and sessions) and filter the view for obsolete assets; if your asset does not have any obsolete assets listed then it ''may'' be safe to disable or delete a particular asset.
	:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.		:: b. '''''check obsolete assets for dependents''''' and see if your asset shows up in the list; if your asset is listed do not delete until you have updated your asset especially for buildings, tracks, industry, and other assets that are not routes or sessions.
	\|}		\|}

Darkrose289: /* Notes */ corrections and formatting

2025-12-30T21:17:56Z

Notes: corrections and formatting

← Older revision		Revision as of 21:17, 30 December 2025
Line 90:		Line 90:
	\| <span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''		\| <span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''
	\|-		\|-
	\| <span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted ''if it is not used by any other asset''. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 3 and 4 before deleting any asset(s).		\| <span id="Notes3" style="color: #FFC300; font-weight: bold;">3.</span> Items labeled as Obsolete in Content Manager can be safely deleted if it is not used by any other asset. Deleting obsolete assets reduces the amount of hard drive space needed and the number of warnings/errors during a rebuild. See notes 4 and 5 before deleting any asset(s).
	\|-		\|-
	\| <span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.		\| <span id="Notes4" style="color: #FFC300; font-weight: bold;">4.</span> Assets that are "Base", "Built-in", or "Packaged" cannot be deleted (occasionally an "Open for Edit" asset also cannot be deleted). If an obsolete asset does not allow the delete command (i.e., "delete" is gray in the menu), the asset may be disabled from the Content Manager's menu under Content > Disable. Disabling an asset hides it from view in the Content Manager (except for "Base", "Built-in", or "Packaged" assets) and the next time the database is rebuilt, those assets will be ignored thus generating fewer "Skipping validation" warnings.

Darkrose289: /* Error and Warning messages */ Added new warnings

2025-12-30T21:13:44Z

Error and Warning messages: Added new warnings

← Older revision		Revision as of 21:13, 30 December 2025
Line 42:		Line 42:

	== Error and Warning messages ==		== Error and Warning messages ==
	This is a compilation of ~~a few~~ validation messages from the Trainz Forum under the thread [https://forums.auran.com/threads/can-you-top-this-trs22-patch.177370/ Can you top this TRS22 Patch?]. Thank you to <span style="color: #00b050; font-weight: bold;">K3JohnHO</span> for starting the discussion thread and <span style="color: #00b050; font-weight: bold;">wreeder</span> and <span style="color: #00b050; font-weight: bold;">JCitron</span> for their replies in the thread. Before adding new messages to this table, please check the TS2009 Wiki to see if it has a page already (e.g., [[Validation Errors]]).		This is a compilation of validation an messages that occur during asset validation. The first three are from the Trainz Forum under the thread [https://forums.auran.com/threads/can-you-top-this-trs22-patch.177370/ Can you top this TRS22 Patch?]. Thank you to <span style="color: #00b050; font-weight: bold;">K3JohnHO</span> for starting the discussion thread and <span style="color: #00b050; font-weight: bold;">wreeder</span> and <span style="color: #00b050; font-weight: bold;">JCitron</span> for their replies in the thread. Before adding new messages to this table, please check the TS2009 Wiki to see if it has a page already (e.g., [[Validation Errors]]).

	{\| class="wikitable"		{\| class="wikitable"
Line 51:		Line 51:
	\|- style="vertical-align:middle;"		\|- style="vertical-align:middle;"
	\| style="text-align:center;" \| Error		\| style="text-align:center;" \| Error
	\| [[File:ContentMgr_error_icon_105x124.png\|frameless\|28px]] ''Failed to download precached data for package '<span style="color: #a6192e;">sc236s</span>' at version '<span style="color: #a6192e;">97563</span>' for platform '<span style="color: #a6192e;">standard-31</span>' '' [[#Notes1\|<sup>[1]</sup>]]		\| [[File:ContentMgr_error_icon_105x124.png\|frameless\|28px]]''Failed to download precached data for package '<span style="color: #a6192e;">sc236s</span>' at version '<span style="color: #a6192e;">97563</span>' for platform '<span style="color: #a6192e;">standard-31</span>' '' [[#Notes1\|<sup>[1]</sup>]]
	\| Installed asset version number is higher than the expected version number on the sever [[#Notes2\|<sup>[2]</sup>]]		\| Installed asset version number is higher than the expected version number on the sever [[#Notes2\|<sup>[2]</sup>]]
	\| Ignore		\| Ignore
Line 61:		Line 61:
	\|- style="vertical-align:middle;"		\|- style="vertical-align:middle;"
	\| style="text-align:center;" \| Warning		\| style="text-align:center;" \| Warning
	\| ~~''Validating <kuid:[userID]:[assetID]>:''~~		\| [[File:ContentMgr_warning_icon_56x75.png\|frameless\|16px]] ''Skipping validation as asset is locally obsolete.''
	: [[File:ContentMgr_warning_icon_56x75.png\|frameless\|16px]] ''Skipping validation as asset is locally obsolete.''
	\| Both new and old versions of some assets are present in the database.		\| Both new and old versions of some assets are present in the database.
	\| Ignore or Disable/Delete the obsolete assets <sup>[[#Notes3\|[3]]],[[#Notes4\|[4]]],[[#Notes5\|[5]]]</sup>		\| Ignore or Disable/Delete the obsolete assets <sup>[[#Notes3\|[3]]],[[#Notes4\|[4]]],[[#Notes5\|[5]]]</sup>
			\|- style="vertical-align:middle;"
			\| style="text-align:center;" \| Warning
			\| [[File:ContentMgr_warning_icon_56x75.png\|frameless\|16px]] ''TrainzBaseSpec::RestoreAssetLibrariesFromPrebuilt> <kuid:[userID]:[assetID]> forced rebuild''
			\|
			\|
			\|- style="vertical-align:middle;"
			\| style="text-align:center;" \| Warning
			\| [[File:ContentMgr_warning_icon_56x75.png\|frameless\|16px]] ''TrainzMeshCollisionData::CreateNewShapeFromData> vertex count too high, falling back to AABB''
			\|
			\|
			\|- style="vertical-align:middle;"
			\| style="text-align:center;" \| Warning
			\| [[File:ContentMgr_warning_icon_56x75.png\|frameless\|16px]] ''ProductSpec> missing 'icon-texture' tag for product '<kuid:[userID]:[assetID]> "[asset name]"' ''
			\|
			\|
	\|}		\|}

Darkrose289: /* Notes */

2025-12-30T19:50:55Z

Notes

← Older revision		Revision as of 19:50, 30 December 2025
Line 72:		Line 72:
	\|<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.		\|<span id="Notes1">1.</span> The <span style="color: #a6192e;">red text</span> in the sample error indicates that other values are possible for each respective field.
	\|-		\|-
	\| <span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V.		\| <span id="Notes2">2.</span> If the [[How_to_Perform_Database_Repairs\|"Rebuild Database"]] command is automatically executed after patching some DLC packages and reopening Trainz '''''-or-''''' the user executed the "Rebuild Database" command from the Trainz Launcher's or Content Manager's main menu then both scenarios result in the Content Manager rebuilding the database cache and finding package-versions with a higher version number than what the Trainz server has on file. This is a normal behavior as assets are updated to supported build versions published by N3V.
	\|-		\|-
	\| <span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''		\| <span style="color: #FFC300; font-weight: bold;">CAUTION for items 3, 4, and 5:</span> '''It is highly recommended that you do not arbitrarily delete assets due to the potential for seeing more faulty assets, missing asset errors, dependency errors, or making one or more assets unusable. For most users, deleting assets should only be used as a last resort and if there are serious performance issues. Review the [[#When_to_Fix.3F\|"When to Fix?"]] section before continuing.'''