Signals - Revision history

OpenTTD Player9876556789 at 02:43, 22 January 2024

2024-01-22T02:43:54Z

OpenTTD Player9876556789 at 02:35, 22 January 2024

2024-01-22T02:35:04Z

OpenTTD Player9876556789: /* Signal types */

2024-01-22T02:32:22Z

‎Signal types

Lisbon: Just some small edits for typos I caught and reducing ambiguity by changing "standard single signal" to "standard single block signal" in the PBS 1-Way section.

2014-02-28T00:47:34Z

Just some small edits for typos I caught and reducing ambiguity by changing "standard single signal" to "standard single block signal" in the PBS 1-Way section.

Benny: Added cleanup

2013-12-04T09:39:50Z

Added cleanup

Benny: Removed merge proposition

2013-12-04T09:39:21Z

Removed merge proposition

Benny: Merged with signal gaps

2013-12-04T09:37:56Z

Merged with signal gaps

Benny: Added link to PBS page

2013-12-04T09:10:14Z

Added link to PBS page

Benny: Added merge proposition

2013-12-04T08:42:25Z

Added merge proposition

Benny: Added link to presignals page and openttd wiki

2013-12-03T06:52:58Z

Added link to presignals page and openttd wiki

@@ Line 80: / Line 80: @@
 == PBS ==
-Full article: http://wiki.openttdcoop.org/PBS
+Details: http://wiki.openttdcoop.org/PBS
 == Signal Gaps ==

@@ Line 58: / Line 58: @@
 [[Image:Signalling breakpoints.png|right|thumb|200px|Breakpoints]]
 Automatic Signal Completion won't stop at: '''Tunnels''' and '''Bridges'''
-but stops at: Junctions, Stations and Existing Signals
+but stops at: Junctions (inculding merges), Stations, Waypoints, and Existing Signals
 ===Checking anyway===

@@ Line 6: / Line 6: @@
 == Signal types ==
 OpenTTD currently has 4 basic signal types (not counting presignals). These 4 are:
-[[Image:Signals_basic.png|center]]
+[[Image:Signals_basic_fixed.png|center]]
 Each of these 4 signal types has different properties and should be used in different circumstances. An overview:
@@ Line 16: / Line 16: @@
 ! Comments
 |-
-! Standard single
+! One-way block signal
 | Block
 | One-way
 | The standard signal for one-way tracks, and therefore the most-used signal in coop games.
 |-
-! Standard double
+! Two-way block signal
 | Block
 | Two-way
@@ Line 34: / Line 34: @@
 | Path-based
 | Two-way
-| While this path-based signal can be driven two-ways, it does have a preference for one direction. This preferred driving direction is indicated by the single signal pole and is the same as with the PBS 1-Way. Driving a PBS signal the wrong way gives a massive penalty in the pathfinder. This is the reason why we commonly use the reversed versions of these signals as penalties in our games.
+| While this path-based signal can be driven two-ways, it does have a preference for one direction. This preferred driving direction is indicated by the single signal pole and is the same as with the PBS 1-Way. Driving a PBS signal the wrong way gives a fairly massive penalty in the pathfinder. This is the reason why we commonly use the reversed versions of these signals as penalties in our games.
 |}
 The two block signals themselves have specific versions, called pre-signals. More about those can be found in [[Presignal Basics]].
 Path-based signals themselves have their own unique features, which are detailed [[Guides:Advanced_Signals|here]].
 ==Placing Signals==

@@ Line 19: / Line 19: @@
 | Block
 | One-way
-| The standard signal for one-way tracks, and therefor the most-used signal in coop games.
+| The standard signal for one-way tracks, and therefore the most-used signal in coop games.
 |-
 ! Standard double
 | Block
 | Two-way
-| Arguably the hardest signal to use properly. Standard double signals have an EOL property that means that if they are red, the pathfinder considers the signal the End Of a Line, thereby discaring its route. This property can lead to very unexpected and unwelcome behaviour. Use with caution.
+| Arguably the hardest signal to use properly. Standard double signals have an EOL property that means that if they are red, the pathfinder considers the signal the End Of a Line, thereby discarding its route. This property can lead to very unexpected and unwelcome behaviour. Use with caution.
 |-
 ! PBS 1-Way
 | Path-based
 | One-way
-| The bath-based version of the standard single signal. In general, use this instead of the PBS signal. However, whenever path-based signals are nog strictly needed, use the standard single signal instead.
+| The path-based version of the standard single block signal. In general, use this instead of the PBS signal. However, whenever path-based signals are not strictly needed, use the standard single block signal instead.
 |-
 ! PBS

← Older revision		Revision as of 09:39, 4 December 2013
Line 1:		Line 1:
	{{update}}		{{update}}
		+	{{cleanup}}

	See also: http://wiki.openttd.org/Signals		See also: http://wiki.openttd.org/Signals

← Older revision		Revision as of 09:37, 4 December 2013
Line 84:		Line 84:

	Full article: http://wiki.openttdcoop.org/PBS		Full article: http://wiki.openttdcoop.org/PBS
		+
		+	== Signal Gaps ==
		+	[[Image:Signal gap settings.png \| thumb \| 400px \| right \| Configuring auto-signalling]]
		+	A signal gap, or gap for short, is the amount of unsignalled space in a single signal block. Understanding signal gaps is important for maximizing train density on a rail line and ensuring that trains continue to move at the maximum allowable speed. In coop games, we adhere to a maximum signal gap of 1 tile.
		+
		+	In general, use of the term "gap" indicates that a signal gap of length greater than 1 has been detected, and as a result, the efficiency of the network is at risk. Steps should be taken to fix any gaps marked in this manner.
		+
		+	Do not confuse a "signal gap" with a "train gap". A train gap is the minimum space between two trains. Because our signals are 2 spaced tiles apart (also known as [http://wiki.openttd.org/Railway_Designs Signal Density]), there is a minimum gap of 3 (the Signal Density +1).
		+
		+	<br clear=all>
		+	=== Why is understanding gaps important? ===
		+
		+	A rail line is only as fast as its weakest link. If there is any point on the line where traffic must slow down or stop, the disruption will have a domino effect on any following trains, resulting in an inefficient network. As the goal is often to build a highly-efficient, and highly-dense network, these types of disruptions must be avoided at all costs!
		+
		+	<br clear=all>
		+	=== What if I need to create a signal gap larger than 1? ===
		+	[[Image:Signal gap sync.png \| thumb \| 400px \| right \| Make sure alternate routes are in sync]]
		+	To create a signal gap larger than 1, you must provide following trains an alternate route until the gap is restored to 1. Larger gaps are created at station platforms, bridges, and tunnels, since none of these items can be signalled.
		+
		+	To create an alternate route, simply make a new line parallel to the first line. This line should continue until the signal gap can be restored to 1, making sure to keep the trains [[Line sync\|synchronize]]d.
		+
		+	<br clear=all>
		+	=== How to count the length of a gap ===
		+	When using normal block signals, a gap's length is defined as the number of unsignalled spaces between two signals. Normal coop [[mainline]]s use a signal gap of 1, meaning there is only 1 unsignalled tiles between two signalled tiles.
		+
		+	When using pre-signals, the gap is counted from the tile after the first pre-signalled (or combo-signalled) tile through to (but not including) the next normal block signal (exit signals are still counted as part of the gap). If multiple routes exist, the largest value is the gap.
		+
		+	Placing a pre- (or combo-) signal and an exit signal (in that order) on a mainline will create a gap larger than 1, so this type of construction should not be done without creating an alternate route.
		+
		+	When using PBS signals, the gap is counted just like normal block signals: from the tile after the PBS signal through to (but not including) the next signalled tile. If multiple routes exist, the largest value is the gap.
		+	[[Image:Signal gap counting.png \| 400px \| thumb \| left \| Counting signal gaps]] [[Image:Signal gap signals.png \| 400px \| thumb \| left \| Other signals]]
		+
		+	<br clear=all>
		+
		+	=== How many alternate routes do I need to create? ===
		+	[[Image:Signal gap bridges.png \| thumb \| 400px \| right \| Two bridges for this gap is enough for any train length]]
		+	The number of alternate routes is dependent on the length of the gap and the minimum train length that might encounter the gap.
		+
		+	The typical formula used to calculate the maximum gap length for a certain number of lines (LineCount) is
		+
		+	'''SignalGapLength = (TrainLength + 2) * LineCount - (TrainLength - 2)'''
		+
		+	Where TrainLength is the minimum train length to encounter the gap, and LineCount is the sum of the alternate routes provided + 1 (the original route).<br />
		+	(This can be quickly calculated with [[User:KenjiE20/Webster\|Webster's]] @gap)
		+
		+	Conversely:
		+
		+	'''LineCount = (SignalGapLength + TrainLength -2) / (TrainLength+2)'''
		+
		+	Always round any fractions up to the next whole number.<br />
		+	(This can be quickly calculated with the [[IRC Commands\|PublicServer bot's]] !gap)
		+
		+	Refer to the section above for information about how to count a gap properly.
		+
		+	<br clear=all>
		+	==The Evil X ===
		+	[[Image:Signal gap evilx.png \| thumb \| 400px \| right \| The Evil X]]
		+	When two lines cross each other in an oblique (non-perpendicular) way, it creates an "evil X". The main problem with the evil X is that it inherently creates a signal gap of 2.
		+
		+	A simple merge does not create a large gap, as long as the tiles before (on both lines) and after (on the single output line) are signalled.
		+
		+	However, note that when the tracks cross obliquely, it is not possible to signal the output line, creating the gap.
		+
		+	In practically all cases, evil X's should be avoided.
		+

@@ Line 80: / Line 80: @@
 Read more: http://wiki.openttdcoop.org/Guides:Presignals
 [[Category:Guides]]
 [[Category:Basic networking]]

← Older revision		Revision as of 08:42, 4 December 2013
Line 1:		Line 1:
	{{update}}		{{update}}
		+	{{Merge\|Signal gap}}

	See also: http://wiki.openttd.org/Signals		See also: http://wiki.openttd.org/Signals

@@ Line 1: / Line 1: @@
 {{update}}
 == Signal types ==
@@ Line 72: / Line 73: @@
 Read more: http://wiki.openttdcoop.org/Two-way_end_of_line
 [[Category:Guides]]
 [[Category:Basic networking]]