Help:VE218 - Revision history

Builderbob: Rephrasing

2019-02-13T02:14:54Z

Rephrasing

← Older revision		Revision as of 02:14, 13 February 2019
Line 7:		Line 7:
	Note that in cases where the track vertices move (such as a turntable or transfer table) it may be possible for this scenario to exist only at specific instants within the animation. Current asset validation will only detect this problem if it occurs in the default state of the asset, meaning that it is possible for such an asset to pass validation but still encounter problems at runtime. The error may be visible as a brief incorrect repositioning of a segment of track that occurs during the animation. This should still be considered a fault in the asset construction.		Note that in cases where the track vertices move (such as a turntable or transfer table) it may be possible for this scenario to exist only at specific instants within the animation. Current asset validation will only detect this problem if it occurs in the default state of the asset, meaning that it is possible for such an asset to pass validation but still encounter problems at runtime. The error may be visible as a brief incorrect repositioning of a segment of track that occurs during the animation. This should still be considered a fault in the asset construction.

	When repairing legacy assets which exhibit this error, the simplistic fix is to remove the ~~duplicate entry~~. Such a change will, however, result in a different number of attached-track entries, which means that existing instances of the asset saved into routes may encounter loader conflicts with the updated asset. A more robust fix is to ~~replace~~ the duplicated ~~entry~~ with a different attachment point so that the number of attached-track entries is unchanged. This fix depends on ~~other~~ attachment ~~points~~ being available at ~~locations~~ within the mesh that ~~allow~~ for a similar path to the original, while not creating duplicate segments.		When repairing legacy assets which exhibit this error, the simplistic fix is to remove the duplicated segment by deleting one of the vertices. Such a change will, however, result in a different number of attached-track entries, which means that existing instances of the asset saved into routes may encounter loader conflicts with the updated asset. A more robust fix is to adjust the duplicated segment by replacing one of the vertices with a different attachment point so that the number of attached-track entries is unchanged. This fix depends on another attachment point being available at a location within the mesh that allows for a similar path to the original, while not creating duplicate segments.

	[[Category:Validation Errors]]		[[Category:Validation Errors]]

Builderbob: Rephrasing.

2019-02-11T01:51:20Z

Rephrasing.

← Older revision		Revision as of 01:51, 11 February 2019
Line 3:		Line 3:
	This error results when a [[KIND SceneryWithTrack]]-derived asset specifies two or more attached tracks between the same pair of track vertices. This construction is never permitted by Trainz, and so the requested configuration cannot be fulfilled.		This error results when a [[KIND SceneryWithTrack]]-derived asset specifies two or more attached tracks between the same pair of track vertices. This construction is never permitted by Trainz, and so the requested configuration cannot be fulfilled.

	~~Note that in cases where the track vertices move (such as a turntable or transfer table) it may be possible for this scenario to exist only at specific instants within~~ the ~~animation. Current asset validation will only detect this problem if it occurs in the default state~~ of the ~~asset, meaning that it is possible for such an asset to pass validation but still encounter problems~~ at ~~runtime. This should still be considered a fault in~~ the ~~asset construction, as Trainz will not correctly honor such a configuration~~.		INDEX is the zero-based sequence number of the vertices container at which the error was detected.

	When repairing legacy assets which exhibit this error, the simplistic fix is to remove the duplicate entry. Such a change will, however, result in a different number of attached-track entries which means that existing instances of the asset saved into routes may encounter loader conflicts with the updated asset. ~~If this is found to cause problems in practice, a~~ more robust fix ~~might be~~ to ~~move~~ the ~~duplicate~~ entry to a ~~"harmless" location which resolves~~ the ~~problem without introducing~~ other ~~concerns~~.		Note that in cases where the track vertices move (such as a turntable or transfer table) it may be possible for this scenario to exist only at specific instants within the animation. Current asset validation will only detect this problem if it occurs in the default state of the asset, meaning that it is possible for such an asset to pass validation but still encounter problems at runtime. The error may be visible as a brief incorrect repositioning of a segment of track that occurs during the animation. This should still be considered a fault in the asset construction.

			When repairing legacy assets which exhibit this error, the simplistic fix is to remove the duplicate entry. Such a change will, however, result in a different number of attached-track entries, which means that existing instances of the asset saved into routes may encounter loader conflicts with the updated asset. A more robust fix is to replace the duplicated entry with a different attachment point so that the number of attached-track entries is unchanged. This fix depends on other attachment points being available at locations within the mesh that allow for a similar path to the original, while not creating duplicate segments.

	[[Category:Validation Errors]]		[[Category:Validation Errors]]

Windwalkr: Created page with "'''Asset has duplicate attached track at track $(INDEX).''' This error results when a KIND SceneryWithTrack-derived asset specifies two or more attached tracks between th..."

2019-01-29T07:02:10Z

Created page with "'''Asset has duplicate attached track at track $(INDEX).''' This error results when a KIND SceneryWithTrack-derived asset specifies two or more attached tracks between th..."

New page

'''Asset has duplicate attached track at track $(INDEX).'''

This error results when a [[KIND SceneryWithTrack]]-derived asset specifies two or more attached tracks between the same pair of track vertices. This construction is never permitted by Trainz, and so the requested configuration cannot be fulfilled.

Note that in cases where the track vertices move (such as a turntable or transfer table) it may be possible for this scenario to exist only at specific instants within the animation. Current asset validation will only detect this problem if it occurs in the default state of the asset, meaning that it is possible for such an asset to pass validation but still encounter problems at runtime. This should still be considered a fault in the asset construction, as Trainz will not correctly honor such a configuration.

When repairing legacy assets which exhibit this error, the simplistic fix is to remove the duplicate entry. Such a change will, however, result in a different number of attached-track entries which means that existing instances of the asset saved into routes may encounter loader conflicts with the updated asset. If this is found to cause problems in practice, a more robust fix might be to move the duplicate entry to a "harmless" location which resolves the problem without introducing other concerns.

[[Category:Validation Errors]]