KIND Track - Revision history

Jbartus: /* attached-splines */ +Earliest available validity is TS12, trainz-build 3.4

2020-05-18T18:26:40Z

attached-splines: +Earliest available validity is TS12, trainz-build 3.4

← Older revision		Revision as of 18:26, 18 May 2020
Line 62:		Line 62:

	==attached-splines==		==attached-splines==
			: Earliest available validity is TS12, trainz-build 3.4
	The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.		The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.

Pw3r: /* Season-selector */

2018-08-21T06:43:02Z

Season-selector

← Older revision		Revision as of 06:43, 21 August 2018
Line 64:		Line 64:
	The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.		The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.

	==~~Season~~-selector==		==season-selector==
	The [["Season-selector" container]] allows for the selection of a season index, which may be used by the [["track-lod-tree" container]].		The [["Season-selector" container]] allows for the selection of a season index, which may be used by the [["track-lod-tree" container]].

Pw3r: /* Supported Tags */

2018-08-21T06:42:35Z

Supported Tags

@@ Line 35: / Line 35: @@
+  {
+  }
   track-sound
+  {
+  }
-  traffic-speed 10.0
+ is_silent              0
-  tunnel-roof-height 0.0
+ istrack                0
@@ Line 65: / Line 66: @@
 ==Season-selector==
 The [["Season-selector" container]] allows for the selection of a season index, which may be used by the [["track-lod-tree" container]].
 ==carrate==
@@ Line 71: / Line 94: @@
 The game waits between 1 and 3 times this value (in seconds) between generating traffic on this road.
-==isroad==
+==traffic-speed==
-If set (1), splines of this type are considered roads. Roads support the generation of Carz. Roads are flagged as blocked by [[KIND MOCrossing]] while the crossing gate is closed. Road splines can generally be joined, even if they are different assets.
+(Only applicable to splines which have 'isroad' set.)
-If not otherwise specified, assets with the 'isroad' tag set are members of the "Road Spline Group" [[KIND_Asset-group#Known Asset-groups|<kuid:30501:100045>]].
+Defines the carz speed limit of the road in meters per second. Carz currently travel at up to 80%-110% (depending on the car) of the speed limit, except when overtaking. This tag does not relate to trains in any way.
 ==isfreeway==
@@ Line 80: / Line 103: @@
 If set (1), this boolean tag causes a multilane road to act as a freeway. This allows carz to change lanes at will, and causes all traffic to flow in the spline's forward direction only. Overtaking is still allowed on non-freeway roads.
 ==numlanes==
@@ Line 91: / Line 109: @@
 Defines the number of carz lanes on a road. Each lane is considered to be 1.7 meters wide. If the road is a freeway, all traffic flows in the same direction.
 TBD: What, if anything, does this mean for a non-freeway road?
 If not otherwise specified, assets with the 'istrack' tag set are members of the "Track Spline Group" [[KIND_Asset-group#Known Asset-groups|<kuid:30501:100043>]].
@@ Line 113: / Line 124: @@
 Some types of vehicle particle emitter are disabled while the vehicle is in a tunnel.
 ==tunnel-roof-height==
@@ Line 143: / Line 138: @@
 ==enable-pfx-collisions==
 Bool value, defaults to 1 and is not compulsory. Defines whether or not this track object should be used for collision detection against particles (e.g. smoke, steam). Disabling it for objects that are unlikely to interact with particles is a good idea.
 =Meshes=

Pw3r: /* Supported Tags */

2018-08-21T06:36:51Z

Supported Tags

← Older revision		Revision as of 06:36, 21 August 2018
Line 53:		Line 53:
	==mesh-table==		==mesh-table==
	The [["mesh-table" Container]] provides details about the track and end-cap meshes which comprise this asset. Most advanced mesh-table options are not available for use at the current time. The important thing is to specify the meshes. Specifically, the 'mesh' tag should be used to specify an IM file, and the 'mesh-asset' tag can be used to specify an alternative source asset for the mesh.		The [["mesh-table" Container]] provides details about the track and end-cap meshes which comprise this asset. Most advanced mesh-table options are not available for use at the current time. The important thing is to specify the meshes. Specifically, the 'mesh' tag should be used to specify an IM file, and the 'mesh-asset' tag can be used to specify an alternative source asset for the mesh.


	==track==		==track==
	The "track" tag is compulsory and determines how the spline geometry is formed from meshes. It is specified as a [[Track Part Container]].		The "track" tag is compulsory and determines how the spline geometry is formed from meshes. It is specified as a [[Track Part Container]].


	==endcap-prev & endcap-next==		==endcap-prev & endcap-next==
	The "endcap-prev" and "endcap-next" tags are specified in the same way as "track", but are not compulsory. If present, these end caps are inserted past the ends of the spline in each direction unless the spline flows onto another spline segment of the same asset. This allows the content creator to "seal" the spline geometry without having to introduce inefficient sealing polygons at each subdivision. The endcaps obey the normal fit-to-spline behavior except that they continue straight in the instantaneous direction of the end of the spline. If present, the endcaps inherit their default settings from the asset's "track" tag but any individual values may be overridden as desired.		The "endcap-prev" and "endcap-next" tags are specified in the same way as "track", but are not compulsory. If present, these end caps are inserted past the ends of the spline in each direction unless the spline flows onto another spline segment of the same asset. This allows the content creator to "seal" the spline geometry without having to introduce inefficient sealing polygons at each subdivision. The endcaps obey the normal fit-to-spline behavior except that they continue straight in the instantaneous direction of the end of the spline. If present, the endcaps inherit their default settings from the asset's "track" tag but any individual values may be overridden as desired.


	==attached-splines==		==attached-splines==
	The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.		The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.


	==Season-selector==		==Season-selector==
	The [["Season-selector" container]] allows for the selection of a season index, which may be used by the [["track-lod-tree" container]].		The [["Season-selector" container]] allows for the selection of a season index, which may be used by the [["track-lod-tree" container]].


	==carrate==		==carrate==
Line 80:		Line 75:

	If not otherwise specified, assets with the 'isroad' tag set are members of the "Road Spline Group" [[KIND_Asset-group#Known Asset-groups\|<kuid:30501:100045>]].		If not otherwise specified, assets with the 'isroad' tag set are members of the "Road Spline Group" [[KIND_Asset-group#Known Asset-groups\|<kuid:30501:100045>]].


	==isfreeway==		==isfreeway==
Line 86:		Line 80:

	If set (1), this boolean tag causes a multilane road to act as a freeway. This allows carz to change lanes at will, and causes all traffic to flow in the spline's forward direction only. Overtaking is still allowed on non-freeway roads.		If set (1), this boolean tag causes a multilane road to act as a freeway. This allows carz to change lanes at will, and causes all traffic to flow in the spline's forward direction only. Overtaking is still allowed on non-freeway roads.


	==is_silent==		==is_silent==
Line 92:		Line 85:

	If set (1), this boolean tag disables the playing of per-axle sounds for vehicles on the spline.		If set (1), this boolean tag disables the playing of per-axle sounds for vehicles on the spline.


	==numlanes==		==numlanes==
Line 99:		Line 91:
	Defines the number of carz lanes on a road. Each lane is considered to be 1.7 meters wide. If the road is a freeway, all traffic flows in the same direction.		Defines the number of carz lanes on a road. Each lane is considered to be 1.7 meters wide. If the road is a freeway, all traffic flows in the same direction.
	TBD: What, if anything, does this mean for a non-freeway road?		TBD: What, if anything, does this mean for a non-freeway road?


	==istrack==		==istrack==
Line 109:		Line 100:

	If not otherwise specified, assets with the 'istrack' tag set are members of the "Track Spline Group" [[KIND_Asset-group#Known Asset-groups\|<kuid:30501:100043>]].		If not otherwise specified, assets with the 'istrack' tag set are members of the "Track Spline Group" [[KIND_Asset-group#Known Asset-groups\|<kuid:30501:100043>]].


	==istunnel==		==istunnel==
Line 123:		Line 113:

	Some types of vehicle particle emitter are disabled while the vehicle is in a tunnel.		Some types of vehicle particle emitter are disabled while the vehicle is in a tunnel.


	==surveyor-only==		==surveyor-only==
Line 130:		Line 119:
	==visible-on-minimap==		==visible-on-minimap==
	If clear (0), hides this spline from the minimap. Splines with non-render-only children are never shown on the minimap. Note that this tag does not have a fixed default value, but rather defaults to the opposite of the 'surveyor-only' tag.		If clear (0), hides this spline from the minimap. Splines with non-render-only children are never shown on the minimap. Note that this tag does not have a fixed default value, but rather defaults to the opposite of the 'surveyor-only' tag.


	==track-sound==		==track-sound==
Line 136:		Line 124:

	An optional [["track-sound" container]] which assists in calculating which sound to play while a train vehicle is on this track.		An optional [["track-sound" container]] which assists in calculating which sound to play while a train vehicle is on this track.


	==traffic-speed==		==traffic-speed==
Line 142:		Line 129:

	Defines the carz speed limit of the road in meters per second. Carz currently travel at up to 80%-110% (depending on the car) of the speed limit, except when overtaking. This tag does not relate to trains in any way.		Defines the carz speed limit of the road in meters per second. Carz currently travel at up to 80%-110% (depending on the car) of the speed limit, except when overtaking. This tag does not relate to trains in any way.


	==tunnel-roof-height==		==tunnel-roof-height==
Line 154:		Line 140:

	If not otherwise specified, assets with the 'istunnel' tag set are members of the "Tunnel Spline Group" [[KIND_Asset-group#Known Asset-groups\|<kuid:30501:100044>]].		If not otherwise specified, assets with the 'istunnel' tag set are members of the "Tunnel Spline Group" [[KIND_Asset-group#Known Asset-groups\|<kuid:30501:100044>]].


	==enable-pfx-collisions==		==enable-pfx-collisions==
	Bool value, defaults to 1 and is not compulsory. Defines whether or not this track object should be used for collision detection against particles (e.g. smoke, steam). Disabling it for objects that are unlikely to interact with particles is a good idea.		Bool value, defaults to 1 and is not compulsory. Defines whether or not this track object should be used for collision detection against particles (e.g. smoke, steam). Disabling it for objects that are unlikely to interact with particles is a good idea.


	=Meshes=		=Meshes=

Pw3r: /* carrate */

2018-08-21T06:12:02Z

carrate

← Older revision		Revision as of 06:12, 21 August 2018
Line 74:		Line 74:
	(Only applicable to splines which have 'isroad' set.)		(Only applicable to splines which have 'isroad' set.)

	The game waits between ~~1x to 3x~~ this ~~decimal~~ value between generating ~~carz~~ on this road.		The game waits between 1 and 3 times this value (in seconds) between generating traffic on this road.


	==isroad==		==isroad==

Pw3r: /* surveyor-only */

2018-03-05T05:40:23Z

surveyor-only

← Older revision		Revision as of 05:40, 5 March 2018
Line 127:		Line 127:

	==surveyor-only==		==surveyor-only==
	If set (1), this boolean value causes the asset to be ~~invisible and non-functional in Driver~~. ~~This is typically used for splines which provide editing assistance~~, such as ~~templates, markers or rulers~~.		If set (1), this boolean value causes the asset to only be visible Surveyor. Where applicable, traincars placed on such splines will operate as normal in Driver etc.


	==visible-on-minimap==		==visible-on-minimap==

Windwalkr at 01:31, 5 October 2016

2016-10-05T01:31:07Z

← Older revision		Revision as of 01:31, 5 October 2016
Line 4:		Line 4:
	'''KIND Track''' provides the sole asset kind for spline-based assets from [[Trainz-build]] version 2.9 and up. Contrary to the name, just as a Road type used to be defined as a Track asset, assets of this kind now include simple track, multitrack, bridges, tunnels, hedges, roads, walls, embankments, local power lines, high-voltage power lines, and so on. Assets of this kind use a rendering technique previously known as "stitched track". Now that all other spline rendering is obsolete, it is simply known as "track".		'''KIND Track''' provides the sole asset kind for spline-based assets from [[Trainz-build]] version 2.9 and up. Contrary to the name, just as a Road type used to be defined as a Track asset, assets of this kind now include simple track, multitrack, bridges, tunnels, hedges, roads, walls, embankments, local power lines, high-voltage power lines, and so on. Assets of this kind use a rendering technique previously known as "stitched track". Now that all other spline rendering is obsolete, it is simply known as "track".

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

	Update: With the release of T:ANE ([[trainz-build]] 4.2) we officially support [[KIND Procedural track]]. There is a page under construction at [[How_To/Build_Procedural_Track_for_T:ANE]] providing reference and this, along with source assets, will be made available in the near future.

	=KIND Hierarchy=		=KIND Hierarchy=
Line 13:		Line 11:

	==Child Classes==		==Child Classes==
	*[[~~Attached-~~track]] is ~~an asset embedded in an industry asset which inherits track characteristics from an~~ track which is ~~attached to it's end vertices~~.		*[[KIND Procedural track]] is a rail-track-specific spline type introduced at trainz-build 4.2 which is procedurally built from components.


Line 59:		Line 57:
	==track==		==track==
	The "track" tag is compulsory and determines how the spline geometry is formed from meshes. It is specified as a [[Track Part Container]].		The "track" tag is compulsory and determines how the spline geometry is formed from meshes. It is specified as a [[Track Part Container]].


			==endcap-prev & endcap-next==
			The "endcap-prev" and "endcap-next" tags are specified in the same way as "track", but are not compulsory. If present, these end caps are inserted past the ends of the spline in each direction unless the spline flows onto another spline segment of the same asset. This allows the content creator to "seal" the spline geometry without having to introduce inefficient sealing polygons at each subdivision. The endcaps obey the normal fit-to-spline behavior except that they continue straight in the instantaneous direction of the end of the spline. If present, the endcaps inherit their default settings from the asset's "track" tag but any individual values may be overridden as desired.


	==attached-splines==		==attached-splines==
	The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.		The [["attached-splines" container]] provides a mechanism for having child splines attached which follow the shape of this parent spline at a slightly offset. Attached splines are used where a spline with one set of rendering or functional behaviour needs to be coupled with a spline with a different set of rendering or functional behaviours. For example, a bridge (scenery) with attached track (functional), or a set of pylons (no stretching or shearing) with some wires strung between them (shearing and stretching to fit.) The attached splines may be render-only splines which effectively don't exist beyond their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.


	~~==endcap-prev & endcap-next==~~
	The "endcap-prev" and "endcap-next" tags are specified in the same way, but are not compulsory. If present, these end caps are inserted past the ends of the spline in each direction unless the spline flows onto another spline of the same type. This allows the content creator to "seal" the spline geometry without having to introduce inefficient sealing polygons at each subdivision. The endcaps obey the normal fit-to-spline behavior except that they continue straight in the instantaneous direction of the end of the spline. The endcaps inherit their default settings from the asset's "track" tag but any individual values may be overridden as desired.

Windwalkr: fix some mangled formatting

2016-01-18T08:30:48Z

fix some mangled formatting

@@ Line 10: / Line 10: @@
 =KIND Hierarchy=
 ==Parent Classes==
-* [[KIND TrainzBaseSpec]] ,  [[Category-class]]  tag definitions of the sets
+* [[KIND TrainzBaseSpec]]
 ==Child Classes==
@@ Line 224: / Line 212: @@
 * etc.
 =Downloads=

Andi06: /* Spline Placement */

2015-06-12T15:47:09Z

Spline Placement

← Older revision		Revision as of 15:47, 12 June 2015
Line 207:		Line 207:
	=Spline Placement=		=Spline Placement=

	Meshes may be specified to follow their placement spline as closely as possible (previously: bendy) or to stay straight but shear to prevent seams. This is discussed in detail in the [["track~~-lod-tree"~~ container]].		Meshes may be specified to follow their placement spline as closely as possible (previously: bendy) or to stay straight but shear to prevent seams. This is discussed in detail in the [[Track_Part_Container\|track part container]].

	Vertices on the mesh may fall into one of two height categories:		Vertices on the mesh may fall into one of two height categories:
Line 213:		Line 213:
	* Spline - The vertex positioning is based on the placement spline.		* Spline - The vertex positioning is based on the placement spline.
	The height category of a vertex is determined from it's relative height within the mesh - if it is less than or equal to the per-mesh-specified grounding height, it is considered grounded.		The height category of a vertex is determined from it's relative height within the mesh - if it is less than or equal to the per-mesh-specified grounding height, it is considered grounded.


	=Performance=		=Performance=

Tonyhilliam: /* KIND Track */

2015-05-08T04:21:29Z

KIND Track

← Older revision		Revision as of 04:21, 8 May 2015
Line 6:		Line 6:
	This page describes [[trainz-build]] 4.1.		This page describes [[trainz-build]] 4.1.

	Update: With the release of T:ANE ([[trainz-build]] 4.2) we officially support KIND Procedural track. There is a page under construction at [[How_To/Build_Procedural_Track_for_T:ANE]] providing reference and this, along with source assets, will be made available in the near future.		Update: With the release of T:ANE ([[trainz-build]] 4.2) we officially support [[KIND Procedural track]]. There is a page under construction at [[How_To/Build_Procedural_Track_for_T:ANE]] providing reference and this, along with source assets, will be made available in the near future.

	=KIND Hierarchy=		=KIND Hierarchy=