"track-lod-tree" container - Revision history

Laurinlaki: /* lod-season-index */ Added note about lod-season-index tag

2019-07-26T20:53:28Z

lod-season-index: Added note about lod-season-index tag

← Older revision		Revision as of 20:53, 26 July 2019
Line 87:		Line 87:

	:The ''lod-season-index'' isn't really a LOD scheme but instead allows for the display of seasonal meshes. When a specific season index (as per the [["Season-selector" container]]) is specified, this tag causes the high "detail" path to be chosen when that season is current.		:The ''lod-season-index'' isn't really a LOD scheme but instead allows for the display of seasonal meshes. When a specific season index (as per the [["Season-selector" container]]) is specified, this tag causes the high "detail" path to be chosen when that season is current.

			Note: It appears that the high "detail" path is not only chosen when the current season is equal but also when it is greater than the season specified in this tag.

	====lod-piece-position====		====lod-piece-position====

2016-10-05T01:56:23Z

← Older revision		Revision as of 01:56, 5 October 2016
Line 90:		Line 90:
	====lod-piece-position====		====lod-piece-position====

	:~~Tag~~ introduced at trainz-build 4.5.		:''This tag was introduced at trainz-build 4.5.''
	:The ''lod-piece-position'' isn't really a LOD scheme but instead allows for the display of different meshes at the end of track. If present, valid options include "first", "last", and "first-or-last" which activate the high "detail" path when this mesh is (respectively) the first, last, or either the first or last mesh in the track (ie. the mesh is adjacent to an endcap position, regardless of whether an endcap mesh is present).		:The ''lod-piece-position'' isn't really a LOD scheme but instead allows for the display of different meshes at the end of track. If present, valid options include "first", "last", and "first-or-last" which activate the high "detail" path when this mesh is (respectively) the first, last, or either the first or last mesh in the track (ie. the mesh is adjacent to an endcap position, regardless of whether an endcap mesh is present).


	==Examples==		==Examples==

2016-10-05T01:55:01Z

← Older revision		Revision as of 01:55, 5 October 2016
Line 3:		Line 3:
	The container defines a track-lod-tree which describes a binary tree structure. When stitching the track geometry, Trainz breaks the spline up into smaller parts (determined by the track's ''mesh-length'' tag) and then parses the track-lod-tree using the current view distance to determine which meshes to use.		The container defines a track-lod-tree which describes a binary tree structure. When stitching the track geometry, Trainz breaks the spline up into smaller parts (determined by the track's ''mesh-length'' tag) and then parses the track-lod-tree using the current view distance to determine which meshes to use.

	This page describes [[trainz-build]] 3.7.		This page describes [[trainz-build]] 4.5.

2016-10-05T01:13:21Z

← Older revision		Revision as of 01:13, 5 October 2016
Line 17:		Line 17:
	lod-is-surveyor 0		lod-is-surveyor 0
	lod-season-index 255		lod-season-index 255
			piece-position "none"
	high-detail		high-detail
	{		{
Line 86:		Line 87:

	:The ''lod-season-index'' isn't really a LOD scheme but instead allows for the display of seasonal meshes. When a specific season index (as per the [["Season-selector" container]]) is specified, this tag causes the high "detail" path to be chosen when that season is current.		:The ''lod-season-index'' isn't really a LOD scheme but instead allows for the display of seasonal meshes. When a specific season index (as per the [["Season-selector" container]]) is specified, this tag causes the high "detail" path to be chosen when that season is current.

			====lod-piece-position====

			:Tag introduced at trainz-build 4.5.
			:The ''lod-piece-position'' isn't really a LOD scheme but instead allows for the display of different meshes at the end of track. If present, valid options include "first", "last", and "first-or-last" which activate the high "detail" path when this mesh is (respectively) the first, last, or either the first or last mesh in the track (ie. the mesh is adjacent to an endcap position, regardless of whether an endcap mesh is present).

	==Examples==		==Examples==

2016-08-16T05:56:01Z

Major update. Remove references to recursion (it's actually a binary tree) and add complex example, with commentary.

2016-08-03T02:34:36Z

lod-distance

← Older revision		Revision as of 02:34, 3 August 2016
Line 61:		Line 61:
	====lod-distance====		====lod-distance====

	:The ''lod-distance'' tag determines the distance (meters) at which Trainz will ~~swap~~ to ~~using~~ the ~~lower~~ detail path. This distance is a guideline and may be affected by user performance settings.		:The ''lod-distance'' tag determines the maximum distance (meters) at which Trainz will use the high detail path of the tree, before changing to the low detail path. This distance is a guideline and may be affected by user performance settings.

	====lod-length====		====lod-length====

2016-01-25T15:06:31Z

Mesh Node

← Older revision		Revision as of 15:06, 25 January 2016
Line 35:		Line 35:

	The ''subdivisions'' tag causes the mesh to be repeated the specified number of times.		The ''subdivisions'' tag causes the mesh to be repeated the specified number of times.


	==Branch Node==		==Branch Node==

2014-02-12T03:01:20Z

Added sort criterion

2013-04-12T01:01:44Z

Examples

← Older revision		Revision as of 01:01, 12 April 2013
Line 111:		Line 111:
	}		}

	The following example illustrates how to use the ~~season~~-selector container to select a seasonal mesh for a track/spline/road (providing lod-season-index 1 refers to winter):		The following example illustrates how to use the [["Season-selector" container]] to select a seasonal mesh for a track/spline/road (providing lod-season-index 1 refers to winter):

	track		track

2013-04-12T01:00:49Z

Examples