"junction-vertices" container - Revision history

Pcas1986: Sp

2014-02-05T04:03:02Z

← Older revision		Revision as of 04:03, 5 February 2014
Line 29:		Line 29:
	=== junction-vertex ===		=== junction-vertex ===
	:Type: Attachment point		:Type: Attachment point
	:Desc: The "junction-vertex" tag is compulsory and determines the track vertex at which this junction is to be ~~create~~. This name must correspond to one of the vertices specified in the [[Attached-track_container\|"attached-track" Container]] and the vertex specified should form a valid junction (ie. should have more than two track stretches attached.)		:Desc: The "junction-vertex" tag is compulsory and determines the track vertex at which this junction is to be created. This name must correspond to one of the vertices specified in the [[Attached-track_container\|"attached-track" Container]] and the vertex specified should form a valid junction (ie. should have more than two track stretches attached.)

Pcas1986: Format change

2014-02-05T03:52:45Z

Format change

← Older revision		Revision as of 03:52, 5 February 2014
Line 1:		Line 1:
	The ~~[["~~junction-vertices~~" Container]]~~ is a ~~top-level [[config.txt file]] entry~~ used by [[KIND ~~SceneryWithTrack~~]] assets.		The junction-vertices container is a list of junction subcontainers with no standalone tags and is used by [[KIND FixedTrack]] assets. Each junction subcontainer uses the following format. Each junction derives its name from the subcontainer's tag name. These names are used to refer to specific junctions from script.

	The [["junction-vertices" Container]] is a list of junction subcontainers with no standalone tags. Each junction subcontainer uses the following format. Each junction derives its name from the subcontainer's tag name. These names are used to refer to specific junctions from script.

			==Junction subcontainer==
			Each junction subcontainer supports the following tags. Each tag is shown here with its default value.

	~~==Supported Tags==~~
	~~Each junction subcontainer supports the following tags. Each tag is shown here with its default value.~~

	~~junction-vertex ""~~
	junction-lever-mesh ""		junction-lever-mesh ""
	junction-mutex ""		junction-mutex ""
			junction-mutex-sharing-forward 0
	junction-mutex-sharing-left 0		junction-mutex-sharing-left 0
	~~junction-mutex-sharing-forward 0~~
	junction-mutex-sharing-right 0		junction-mutex-sharing-right 0
			junction-vertex ""


			=== junction-lever-mesh ===
			:Type: String
			:Desc: The "junction-lever-mesh" tag optionally specifies the name of a [["mesh-table" Container]] entry to use for the junction lever. ''TBD: Animation? Multiple-state junction support?''

			=== junction-mutex ===
			:Type: String
			:Desc: The "junction-mutex" tag optionally specifies the name of a [["mutexes" Container]] entry to use for the junction's mutex. This allows sharing a single mutex between multiple junctions, and requires a detailed understanding of the trainz [[Permit]] system. If ommitted, the junction will use a unqiue mutex.

	The "junction-~~vertex~~" ~~tag is compulsory~~ and ~~determines~~ the ~~track vertex at which this~~ junction ~~is to~~ be ~~create~~. ~~This name must correspond to one of~~ the ~~vertices specified in~~ the ~~[[Attached-track_container\|"attached-track" Container]] and the vertex~~ specified ~~should form a valid junction~~ (ie. ~~should have more than two track stretches attached~~.)		=== junction-mutex-sharing-forward ===
			=== junction-mutex-sharing-left ===
			=== junction-mutex-sharing-right ===
			:Type: Integer
			:Desc: The "junction-mutex-sharing-left", "junction-mutex-sharing-forward", and "junction-mutex-sharing-right" tags describe sharing masks for the junction's mutex. Two or more permits may be granted for a junction simultaneously if a ''bitwise and'' of their sharing masks gives a non-zero result. When a permit is requested by script for this junction's mutex, the appropriate sharing masks is selected based on the requested direction. If no direction is specified (eg. a legacy script is in use) then a sharing mask of zero is used.

	The "junction-~~lever-mesh~~" tag ~~optionally specifies~~ the name of a [["~~mesh~~-~~table~~" Container]] ~~entry to use for~~ the junction ~~lever~~. ~~''TBD: Animation? Multiple-state junction support?''~~		=== junction-vertex ===
			:Type: Attachment point
			:Desc: The "junction-vertex" tag is compulsory and determines the track vertex at which this junction is to be create. This name must correspond to one of the vertices specified in the [[Attached-track_container\|"attached-track" Container]] and the vertex specified should form a valid junction (ie. should have more than two track stretches attached.)

	The "junction-mutex" tag optionally specifies the name of a [["mutexes" Container]] entry to use for the junction's mutex. This allows sharing a single mutex between multiple junctions, and requires a detailed understanding of the trainz [[Permit]] system. If ommitted, the junction will use a unqiue mutex.

	The "junction-mutex-sharing-left", "junction-mutex-sharing-forward", and "junction-mutex-sharing-right" tags describe sharing masks for the junction's mutex. Two or more permits may be granted for a junction simultaneously if a ''bitwise and'' of their sharing masks gives a non-zero result. When a permit is requested by script for this junction's mutex, the appropriate sharing masks is selected based on the requested direction. If no direction is specified (eg. a legacy script is in use) then a sharing mask of zero is used.

	==Junction-vertices Example==		==Junction-vertices Example==
Line 40:		Line 50:

	==Categories==		==Categories==
	[[Category:Config Container]]		[[Category:Config Container\|J]]

Pw3r: /* Supported Tags */

2011-10-04T04:46:20Z

Supported Tags

← Older revision		Revision as of 04:46, 4 October 2011
Line 15:		Line 15:


	The "junction-vertex" tag is compulsory and determines the track vertex at which this junction is to be create. This name must correspond to one of the vertices specified in the [["attached-track" Container]] and the vertex specified should form a valid junction (ie. should have more than two track stretches attached.)		The "junction-vertex" tag is compulsory and determines the track vertex at which this junction is to be create. This name must correspond to one of the vertices specified in the [[Attached-track_container\|"attached-track" Container]] and the vertex specified should form a valid junction (ie. should have more than two track stretches attached.)

	The "junction-lever-mesh" tag optionally specifies the name of a [["mesh-table" Container]] entry to use for the junction lever. ''TBD: Animation? Multiple-state junction support?''		The "junction-lever-mesh" tag optionally specifies the name of a [["mesh-table" Container]] entry to use for the junction lever. ''TBD: Animation? Multiple-state junction support?''
Line 22:		Line 22:

	The "junction-mutex-sharing-left", "junction-mutex-sharing-forward", and "junction-mutex-sharing-right" tags describe sharing masks for the junction's mutex. Two or more permits may be granted for a junction simultaneously if a ''bitwise and'' of their sharing masks gives a non-zero result. When a permit is requested by script for this junction's mutex, the appropriate sharing masks is selected based on the requested direction. If no direction is specified (eg. a legacy script is in use) then a sharing mask of zero is used.		The "junction-mutex-sharing-left", "junction-mutex-sharing-forward", and "junction-mutex-sharing-right" tags describe sharing masks for the junction's mutex. Two or more permits may be granted for a junction simultaneously if a ''bitwise and'' of their sharing masks gives a non-zero result. When a permit is requested by script for this junction's mutex, the appropriate sharing masks is selected based on the requested direction. If no direction is specified (eg. a legacy script is in use) then a sharing mask of zero is used.



	==Junction-vertices Example==		==Junction-vertices Example==

Windwalkr (legacy 2550): "junction-vertices" Container moved to "junction-vertices" container

2010-03-08T12:30:50Z

"junction-vertices" Container moved to "junction-vertices" container

← Older revision	Revision as of 12:30, 8 March 2010
(No difference)

Windwalkr: 1 revision

2010-02-03T13:58:17Z

1 revision

← Older revision	Revision as of 13:58, 3 February 2010
(No difference)

Windwalkr at 04:51, 20 August 2008

2008-08-20T04:51:19Z

New page

The [["junction-vertices" Container]] is a top-level [[config.txt file]] entry used by [[KIND SceneryWithTrack]] assets.

The [["junction-vertices" Container]] is a list of junction subcontainers with no standalone tags. Each junction subcontainer uses the following format. Each junction derives its name from the subcontainer's tag name. These names are used to refer to specific junctions from script.

==Supported Tags==
Each junction subcontainer supports the following tags. Each tag is shown here with its default value.

junction-vertex ""
junction-lever-mesh ""
junction-mutex ""
junction-mutex-sharing-left 0
junction-mutex-sharing-forward 0
junction-mutex-sharing-right 0

The "junction-vertex" tag is compulsory and determines the track vertex at which this junction is to be create. This name must correspond to one of the vertices specified in the [["attached-track" Container]] and the vertex specified should form a valid junction (ie. should have more than two track stretches attached.)

The "junction-lever-mesh" tag optionally specifies the name of a [["mesh-table" Container]] entry to use for the junction lever. ''TBD: Animation? Multiple-state junction support?''

The "junction-mutex" tag optionally specifies the name of a [["mutexes" Container]] entry to use for the junction's mutex. This allows sharing a single mutex between multiple junctions, and requires a detailed understanding of the trainz [[Permit]] system. If ommitted, the junction will use a unqiue mutex.

The "junction-mutex-sharing-left", "junction-mutex-sharing-forward", and "junction-mutex-sharing-right" tags describe sharing masks for the junction's mutex. Two or more permits may be granted for a junction simultaneously if a ''bitwise and'' of their sharing masks gives a non-zero result. When a permit is requested by script for this junction's mutex, the appropriate sharing masks is selected based on the requested direction. If no direction is specified (eg. a legacy script is in use) then a sharing mask of zero is used.

==Junction-vertices Example==
The following is an example of a simple [["junction-vertices" Container]] which declares two named junctions.

junction-vertices
{
one-junction
{
junction-vertex "a.track0a"
}
another-junction
{
junction-vertex "a.track2a"
}
}

==Categories==
[[Category:Config Container]]