Junction Kit - Revision history

Andi06: Replaced content with "Help and Information on AJS Junction Kit Mark 2 Under Construction Junction Kit Configuration Notes on configuration of Assets"

2013-11-22T19:20:12Z

Replaced content with "Help and Information on AJS Junction Kit Mark 2 Under Construction Junction Kit Configuration Notes on configuration of Assets"

Show changes

Andi06: /* junction-type codes */

2013-11-22T10:13:43Z

junction-type codes

← Older revision		Revision as of 10:13, 22 November 2013
Line 104:		Line 104:
	\|Description		\|Description
	\|-		\|-
	\|0		\| -3
			\|Placeholder used by the script to reference 3 way spline junctions
			\|-
			\| -2
			\|Placeholder used by the script to reference 2 way spline junctions
			\|-
			\| -1
			\|Generic clickable object such as Signal Box Asset
			\|-
			\| 0
	\|Fixed track object with no animations, typically this would be a spacer which has no animations but which which needs scripted ability (such as ballast hiding) to match other assets.		\|Fixed track object with no animations, typically this would be a spacer which has no animations but which which needs scripted ability (such as ballast hiding) to match other assets.
	\|-		\|-
	\|1		\| 1
	\|Diamond crossing		\|Diamond crossing
	\|-		\|-
	\|2		\| 2
	\|Catch point (Derail)		\|Catch point (Derail)
	\|-		\|-
	\|3		\| 3
	\|Two way point		\|Two way point
	\|-		\|-
	\|4		\| 4
	\|Three way point		\|Three way point
	\|-		\|-
	\|5		\| 5
	\|Single slip		\|Single slip
	\|-		\|-
	\|6		\| 6
	\|Double slip		\|Double slip
	\|-		\|-
	\|7		\| 7
	\|Double crossover		\|Double crossover
	\|-		\|-
	\|8		\| 8
	\|Single Crossover		\|Single Crossover (UK Trailing)
			\|-
			\| 9
			\|Single Crossover (UK Leading)
	\|-		\|-
	\|		\|

Andi06 at 10:05, 22 November 2013

2013-11-22T10:05:21Z

← Older revision		Revision as of 10:05, 22 November 2013
Line 17:		Line 17:

	It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>		It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>

	~~==Known Issue==~~
	Any of the original junction kit assets will throw a script exception whenever a new style fixed-track junction is toggled. This doen't affect the operation of either type of asset and requires a simple modification to the original object scripts which I will update when time permits.<br><br> This has now been fixed.

	==Levers==		==Levers==
	Levers are entirely decorative, the junctions are activated by a click on the main mesh. ~~I expect that it will be possible to allow for levers to be separate attached animations.<br><br>~~		Levers are entirely decorative, the junctions are activated by a click on the main mesh.

	==Junction Linking==		==Junction Linking==
	~~This is experimental. To avoid recursive loops the links are one way only, so to set up a single track crossover for instance you will need to add a link to both junctions.~~ Links are ignored by the AI - they only operate when the junctions are manually switched.<br><br>		Links are ignored by the AI - they only operate when the junctions are manually switched.<br><br>

	==Asset Configuration==		==Asset Configuration==

Andi06: /* Script Library Control */

2013-11-22T10:03:52Z

Script Library Control

← Older revision		Revision as of 10:03, 22 November 2013
Line 17:		Line 17:

	It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>		It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>

	~~Keypresses from a train or mouse clicks will toggle junctions unconditionally (even if under another train) this is no different from the behaviour of spline junctions.<br><br>~~

	==Known Issue==		==Known Issue==

Andi06: /* Known Issue */

2013-05-15T03:19:02Z

Known Issue

← Older revision		Revision as of 03:19, 15 May 2013
Line 21:		Line 21:

	==Known Issue==		==Known Issue==
	Any of the original junction kit assets will throw a script exception whenever a new style fixed-track junction is toggled. This doen't affect the operation of either type of asset and requires a simple modification to the original object scripts which I will update when time permits.<br><br>		Any of the original junction kit assets will throw a script exception whenever a new style fixed-track junction is toggled. This doen't affect the operation of either type of asset and requires a simple modification to the original object scripts which I will update when time permits.<br><br> This has now been fixed.

	==Levers==		==Levers==

Andi06: /* config.txt: Tags & Containers */

2013-05-15T03:18:18Z

config.txt: Tags & Containers

← Older revision		Revision as of 03:18, 15 May 2013
Line 34:		Line 34:
	* This is a list of tags and containers which relate to fixed track junctions.		* This is a list of tags and containers which relate to fixed track junctions.
	* Tags in bold type are essential for correct operation of the Library.		* Tags in bold type are essential for correct operation of the Library.
			* You will also need a mesh-table, junction-vertices and attached -track containers.<br><br>
	{{TableHeader\|width=95%\|margin=15px}}		{{TableHeader\|width=95%\|margin=15px}}
	\|-		\|-
Line 82:		Line 83:
	'''junction-type'''<br>		'''junction-type'''<br>
	default-state<br>		default-state<br>
			direction-0<br>
			direction-1<br>
	'''}'''<br>		'''}'''<br>
	'''}'''		'''}'''
	\| <br>		\| <br>
	<br>		<br>
			integer<br>
			integer<br>
	integer<br>		integer<br>
	integer<br>		integer<br>
	<br>		<br>
	<br>		<br>
	\|junction-type (see below) defines the layout and behaviour of the junction.~~<br>~~<br>		\|'''junction-type''' (see below) defines the layout and behaviour of the junction.<br>
	default-state (see below) defines the initial ~~direction~~ of the junction when first placed in Surveyor, this defaults to 0 ~~if the tag is not present. The state~~ can ~~always~~ be altered ~~via~~ the ~~object property interface~~.		'''default-state''' (see below) defines the initial state of the junction when first placed in Surveyor, this defaults to 0 and can be altered in Surveyor.<br>
			'''direction-0''' defines the straight ahead direction for the first node in a single crossover. (0=left, 1=straight, 2=right) Defaults to 0 and applies to Junction-type 8 only.<br>
			'''direction-1''' defines the straight ahead direction for the second node. Defaults to 0. Junction-type 8 only.<br>
	\|}<br>		\|}<br>

Andi06: /* default-state codes */

2013-05-14T23:35:30Z

default-state codes

← Older revision		Revision as of 23:35, 14 May 2013
Line 164:		Line 164:
	\|7		\|7
	\|[[Image:DoubleCrossover.jpg]]		\|[[Image:DoubleCrossover.jpg]]
			\|-
			\|8
			\|0 = straight ahead<br>1 = crossover position
			\|-
	\|}		\|}


	==mesh table containers==		==mesh table containers==

Andi06: /* junction-type codes */

2013-05-14T23:33:33Z

junction-type codes

← Older revision		Revision as of 23:33, 14 May 2013
Line 125:		Line 125:
	\|7		\|7
	\|Double crossover		\|Double crossover
			\|-
			\|8
			\|Single Crossover
	\|-		\|-
	\|		\|

Andi06: /* Script Library Control */

2013-04-24T20:35:21Z

Script Library Control

← Older revision		Revision as of 20:35, 24 April 2013
Line 18:		Line 18:
	It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>		It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>

	Keypresses from a train or mouse clicks will toggle junctions unconditionally (even if under another train) this is no different from the behaviour os spline junctions.<br><br>		Keypresses from a train or mouse clicks will toggle junctions unconditionally (even if under another train) this is no different from the behaviour of spline junctions.<br><br>

	==Known Issue==		==Known Issue==

Andi06: /* config.txt: Tags & Containers */

2013-04-24T20:21:52Z

config.txt: Tags & Containers

← Older revision		Revision as of 20:21, 24 April 2013
Line 1:		Line 1:
			==Notes on the Preview Assets==
			==Default Control==
			By default clicking on a fixed track junction asset will only toggle the first referenced switch, usually item 0 in the junction-vertices table. There is no way that the other nodes can be manually switched without script. However the AI will be able to successfully negotiate the object no matter how many junction-vertices are defined.<br><br>

			The assets do not respond to the junction-direction button on the track tab in Surveyor and they cannot be switched on the minimap.<br><br>

			These drawbacks can only be addressed by Auran.

			==Script Library Control==
			There is a button in the Properties dialogue which allows you to toggle through all of the possible settings to set a new default for the session. These settings are remembered across session saves.<br><br>

			In Driver the AI is left to its own devices and should be able to switch the junctions properly without interference from the script.<br><br>

			Pressing J or ^J from a train will toggle the node nearest to the train and will set up any other junction nodes to suit.<br><br>

			Clicking on the mesh will toggle to the next available state.<br><br>

			It is not possible to detect the difference between a mouse click on the mesh and a keypress from a train approaching the first node with 100% accuracy.<br><br>

			Keypresses from a train or mouse clicks will toggle junctions unconditionally (even if under another train) this is no different from the behaviour os spline junctions.<br><br>

			==Known Issue==
			Any of the original junction kit assets will throw a script exception whenever a new style fixed-track junction is toggled. This doen't affect the operation of either type of asset and requires a simple modification to the original object scripts which I will update when time permits.<br><br>

			==Levers==
			Levers are entirely decorative, the junctions are activated by a click on the main mesh. I expect that it will be possible to allow for levers to be separate attached animations.<br><br>

			==Junction Linking==
			This is experimental. To avoid recursive loops the links are one way only, so to set up a single track crossover for instance you will need to add a link to both junctions. Links are ignored by the AI - they only operate when the junctions are manually switched.<br><br>

			==Asset Configuration==

	==config.txt: Tags & Containers==		==config.txt: Tags & Containers==
	* This is a list of tags and containers which relate to fixed track junctions.		* This is a list of tags and containers which relate to fixed track junctions.