"attached-splines" container - Revision history

Zecmurphy: /* Supported Tags */

2017-05-05T09:59:45Z

Supported Tags

← Older revision		Revision as of 09:59, 5 May 2017
Line 17:		Line 17:
	spline-kuid <NULL>		spline-kuid <NULL>
	visual-only 0		visual-only 0
	spline~~-follows~~-gradient 1		follows-spline-gradient 1
	start-gap 0		start-gap 0
	end-gap 0		end-gap 0
Line 60:		Line 60:

	''This tag was introduced at trainz-build 4.5.''		''This tag was introduced at trainz-build 4.5.''


	=Performance Notes=		=Performance Notes=

Windwalkr at 01:57, 5 October 2016

2016-10-05T01:57:49Z

← Older revision		Revision as of 01:57, 5 October 2016
Line 50:		Line 50:
	This tag is valid only for 'visual-only' children and should not be present otherwise.		This tag is valid only for 'visual-only' children and should not be present otherwise.
	Endcaps (if present) will also be inset by the specified distance.		Endcaps (if present) will also be inset by the specified distance.

	''This tag was introduced at trainz-build 4.5.''		''This tag was introduced at trainz-build 4.5.''

Line 57:		Line 58:
	This tag is valid only for 'visual-only' children and should not be present otherwise.		This tag is valid only for 'visual-only' children and should not be present otherwise.
	Endcaps (if present) will also be inset by the specified distance.		Endcaps (if present) will also be inset by the specified distance.

	''This tag was introduced at trainz-build 4.5.''		''This tag was introduced at trainz-build 4.5.''

Windwalkr at 01:55, 5 October 2016

2016-10-05T01:55:44Z

← Older revision		Revision as of 01:55, 5 October 2016
Line 3:		Line 3:
	The container provides a mechanism for having child splines attached which run parallel to the shape of a parent spline at a slight 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 of their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.		The container provides a mechanism for having child splines attached which run parallel to the shape of a parent spline at a slight 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 of their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.

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


Line 50:		Line 50:
	This tag is valid only for 'visual-only' children and should not be present otherwise.		This tag is valid only for 'visual-only' children and should not be present otherwise.
	Endcaps (if present) will also be inset by the specified distance.		Endcaps (if present) will also be inset by the specified distance.
			''This tag was introduced at trainz-build 4.5.''


Line 56:		Line 57:
	This tag is valid only for 'visual-only' children and should not be present otherwise.		This tag is valid only for 'visual-only' children and should not be present otherwise.
	Endcaps (if present) will also be inset by the specified distance.		Endcaps (if present) will also be inset by the specified distance.
			''This tag was introduced at trainz-build 4.5.''

Windwalkr at 01:26, 5 October 2016

2016-10-05T01:26:04Z

← Older revision		Revision as of 01:26, 5 October 2016
Line 17:		Line 17:
	spline-kuid <NULL>		spline-kuid <NULL>
	visual-only 0		visual-only 0
	}		spline-follows-gradient 1
	1		start-gap 0
	{		end-gap 0
	~~lateral-offset 0.0~~
	~~use~~-~~same~~-~~direction~~ 1
	~~spline~~-~~kuid <NULL>~~
	~~visual~~-~~only~~ 0
	}		}
	etc...		etc...
Line 48:		Line 44:
	====follows-spline-gradient====		====follows-spline-gradient====
	If set (1), this boolean tag causes the child spline to follow the gradient of this spline rather than leaving the child to determine whether it should follow the spline gradient or the ground height. This is useful when the child is an asset which would normally follow the ground height (such as a regular track) but where the attachment location on the parent does not follow the ground height (such as on a bridge.)		If set (1), this boolean tag causes the child spline to follow the gradient of this spline rather than leaving the child to determine whether it should follow the spline gradient or the ground height. This is useful when the child is an asset which would normally follow the ground height (such as a regular track) but where the attachment location on the parent does not follow the ground height (such as on a bridge.)


			====start-gap====
			Defines the distance in meters between the start of the spline and the start of the child's geometry, as measured along the path of the spline. Defaults to 0m, which means that the geometry starts with the spline. Positive numbers inset the geometry within the spline. Negative numbers are not permitted. If the 'start-gap' and 'end-gap' offsets cause the geometry length to drop to zero, no spline geometry is rendered, however any endcaps will still be rendered.
			This tag is valid only for 'visual-only' children and should not be present otherwise.
			Endcaps (if present) will also be inset by the specified distance.


			====end-gap====
			Defines the distance in meters between the end of the child's geometry and the end of the spline, as measured along the path of the spline. Defaults to 0m, which means that the geometry ends with the spline. Positive numbers inset the geometry within the spline. Negative numbers are not permitted. If the 'start-gap' and 'end-gap' offsets cause the geometry length to drop to zero, no spline geometry is rendered, however any endcaps will still be rendered.
			This tag is valid only for 'visual-only' children and should not be present otherwise.
			Endcaps (if present) will also be inset by the specified distance.

Frogpipe at 00:09, 17 August 2016

2016-08-17T00:09:50Z

← Older revision		Revision as of 00:09, 17 August 2016
Line 9:		Line 9:
	The "attached-splines" container is a list of subcontainers with no standalone tags. Each attached-splines subcontainer supports the following tags. Each tag is shown here with its default value.		The "attached-splines" container is a list of subcontainers with no standalone tags. Each attached-splines subcontainer supports the following tags. Each tag is shown here with its default value.

	lateral-offset 0.0		attached-splines
	use-same-direction 1		{
	spline-kuid <NULL>		0
	visual-only 0		{
			lateral-offset 0.0
			use-same-direction 1
			spline-kuid <NULL>
			visual-only 0
			}
			1
			{
			lateral-offset 0.0
			use-same-direction 1
			spline-kuid <NULL>
			visual-only 0
			}
			etc...
			}

	====lateral-offset====		====lateral-offset====

Windwalkr at 23:59, 18 February 2014

2014-02-18T23:59:31Z

← Older revision		Revision as of 23:59, 18 February 2014
Line 42:		Line 42:
	* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.		* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.

	[[Category:Config Container]]		[[Category:Config Container\|A]]

Windwalkr: test

2014-02-18T23:59:08Z

test

← Older revision		Revision as of 23:59, 18 February 2014
Line 42:		Line 42:
	* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.		* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.

	[[Category:Config Container\|A]]		[[Category:Config Container]]

Pcas1986: Added sort criterion

2014-02-12T02:52:41Z

Added sort criterion

← Older revision		Revision as of 02:52, 12 February 2014
Line 42:		Line 42:
	* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.		* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.

	[[Category:Config Container]]		[[Category:Config Container\|A]]

Windwalkr at 15:10, 28 October 2012

2012-10-28T15:10:00Z

← Older revision		Revision as of 15:10, 28 October 2012
Line 2:		Line 2:

	The container provides a mechanism for having child splines attached which run parallel to the shape of a parent spline at a slight 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 of their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.		The container provides a mechanism for having child splines attached which run parallel to the shape of a parent spline at a slight 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 of their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.

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


Line 28:		Line 30:
	If set (1), this boolean tag causes the child spline to exist only while being actively rendered. This also removes all functional aspects of the child spline (such as carz, the use of the spline as railway track, connection of other splines, etc.)		If set (1), this boolean tag causes the child spline to exist only while being actively rendered. This also removes all functional aspects of the child spline (such as carz, the use of the spline as railway track, connection of other splines, etc.)
	If clear (0), the child spline is fully instantiated along with the parent. Manual editing of the child spline is prevented in Surveyor but in all other aspects the child spline reacts as if placed manually.		If clear (0), the child spline is fully instantiated along with the parent. Manual editing of the child spline is prevented in Surveyor but in all other aspects the child spline reacts as if placed manually.


			====follows-spline-gradient====
			If set (1), this boolean tag causes the child spline to follow the gradient of this spline rather than leaving the child to determine whether it should follow the spline gradient or the ground height. This is useful when the child is an asset which would normally follow the ground height (such as a regular track) but where the attachment location on the parent does not follow the ground height (such as on a bridge.)

Windwalkr: Created page with "The "attached-splines" container is a top-level config.txt file entry used by the KIND Track content type. The container provides a mechanism for having child spl..."

2012-09-24T06:59:28Z

Created page with "The "attached-splines" container is a top-level config.txt file entry used by the KIND Track content type. The container provides a mechanism for having child spl..."

New page

The [["attached-splines" container]] is a top-level [[config.txt file]] entry used by the [[KIND Track]] content type.

The container provides a mechanism for having child splines attached which run parallel to the shape of a parent spline at a slight 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 of their rendering behaviour, or they may be fully functional splines whose only specialty is that they move and delete with their parent.

=Supported Tags=
The "attached-splines" container is a list of subcontainers with no standalone tags. Each attached-splines subcontainer supports the following tags. Each tag is shown here with its default value.

lateral-offset 0.0
use-same-direction 1
spline-kuid <NULL>
visual-only 0

====lateral-offset====
This decimal tag defines the number of meters that the child spline is offset sideways from its parent's position. The parent is at position 0.0, with positive offsets to the right, and negative offsets to the left.

====use-same-direction====
If set (1), this boolean tag causes the child spline to face in the same direction as the parent
If clear (0), the child faces backward (180° rotation) to the parent.

====spline-kuid====
This KUID tag defines the asset type to use for the child spline. A parent spline may have multiple children, which may be of the same or differing types.

====visual-only====
If set (1), this boolean tag causes the child spline to exist only while being actively rendered. This also removes all functional aspects of the child spline (such as carz, the use of the spline as railway track, connection of other splines, etc.)
If clear (0), the child spline is fully instantiated along with the parent. Manual editing of the child spline is prevented in Surveyor but in all other aspects the child spline reacts as if placed manually.

=Performance Notes=
* It is strongly recommended to avoid nesting of multiple layers of splines (eg. a single parent asset should have one or more child assets, and no grandchildren.)
* Visual-only splines should be used where possible, as this gives a substantial performance benefit.
* Any use of attached splines comes with a performance penalty. Where possible, a single spline which includes all the necessary features is preferred.
* There is no connection between the LOD level of a parent spline, and the LOD level of a child spline. Do not assume that they will change LOD levels at the same time.

[[Category:Config Container]]