Difference between revisions of "Line sync"

From #openttdcoop wiki

Jump to: navigation, search
m (Initial Draft)
 
 
(11 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{reqscreenshot}}
 
 
== Definition ==
 
== Definition ==
 
Line sync, or '''sync''' for short, is a term used in coop games when splitting a line (in most cases, a [[mainline]]).  The split lines are "in sync" if they are the same length, and "out of sync" if one is shorter than the other.
 
Line sync, or '''sync''' for short, is a term used in coop games when splitting a line (in most cases, a [[mainline]]).  The split lines are "in sync" if they are the same length, and "out of sync" if one is shorter than the other.
Line 12: Line 11:
  
 
[[Image:Tunnel_Flow.png|250px|frame|left|In Sync]]
 
[[Image:Tunnel_Flow.png|250px|frame|left|In Sync]]
[[Image:image_needed.png|250px|frame|right|(REPLACE)Out of Sync]]<br clear=all>
+
[[Image:Desync.png|250px|frame|right|Out of Sync]]<br clear=all>
  
 
== Checking Line Sync ==
 
== Checking Line Sync ==
 
The easiest way to check line sync is to use OpenTTD's measuring tool.  Starting at the split, count the number of straight tracks on each route until the lines merge again.  Also count the number of diagonal tracks.  If all routes have the same number of straight tracks and the same number of diagonal tracks, the lines are in sync.  Due to the difference in length between a straight and diagonal track, it is not always safe to assume that two diagonal tracks count as one straight track (especially on very dense networks).
 
The easiest way to check line sync is to use OpenTTD's measuring tool.  Starting at the split, count the number of straight tracks on each route until the lines merge again.  Also count the number of diagonal tracks.  If all routes have the same number of straight tracks and the same number of diagonal tracks, the lines are in sync.  Due to the difference in length between a straight and diagonal track, it is not always safe to assume that two diagonal tracks count as one straight track (especially on very dense networks).
  
[[Image:image_needed.png|250px|frame|left|Measuring Line Sync]]<br clear=all>
+
[[Image:Measuring.png|250px|frame|left|Measuring Line Sync]]<br clear=all>
  
 
== Multi-line Sync ==
 
== Multi-line Sync ==
 
In cases where more than 2 tracks must be sync'd, it is often helpful to remember that trains should enter and leave the set of tracks from alternate corners of the bounding rectangle.  If they enter from the southwest, they should all leave via the northeast corner.
 
In cases where more than 2 tracks must be sync'd, it is often helpful to remember that trains should enter and leave the set of tracks from alternate corners of the bounding rectangle.  If they enter from the southwest, they should all leave via the northeast corner.
  
[[Image:image_needed.png|250px|frame|left|Multi-line Sync]]<br clear=all>
+
[[Image:Multiline_sync.png|250px|frame|left|Multi-line Sync]]<br clear=all>
 
+
== Station Sync ==
+
Line sync also applies to stations.  If station platforms are out of sync, the resulting slowdown could impact station throughput.
+
 
+
[[Image:image_needed.png|250px|frame|left|Station Sync]]<br clear=all>
+
  
 
== Synchronized corners ==
 
== Synchronized corners ==
Line 35: Line 29:
  
 
== X-Sync ==
 
== X-Sync ==
Below is a special sync case.  It uses an X crossing between two split tracks to maintain line sync.  Note that while this [[Signal gap|evil-X]] is typically frowned upon, this case is ok because both tracks *should* not be in use at the same time (because trains came from the same original track).
+
Below is a special sync case.  It uses an X crossing between two split tracks to maintain line sync.  Note that while an [[Signal gap|evil-X]] is typically frowned upon, this case is ok because both tracks should not be in use at the same time (because trains came from the same original track).
  
 
[[Image:X-Sync.png|250px|frame|left|X-sync]]<br clear=all>
 
[[Image:X-Sync.png|250px|frame|left|X-sync]]<br clear=all>
 +
 +
== See Also ==
 +
* [[Mainline]]
 +
* [[User:KenjiE20/Webster#Line_split_.28tunnels.29_calculator|Webster's helper function]]
 +
 +
[[Category:Guides]]
 +
[[Category:Basic networking]]

Latest revision as of 03:37, 31 March 2015

Definition

Line sync, or sync for short, is a term used in coop games when splitting a line (in most cases, a mainline). The split lines are "in sync" if they are the same length, and "out of sync" if one is shorter than the other.

Sync is especially important on dense networks (lots of trains on the same line) to ensure that the line continues to flow at maximum speed without interruption.

Lines that are in sync will typically shift one or more tiles (N-1, where N is the number of routes from before the shift to the end of the shift).

Seeing the Difference

Below are two screenshots. One contains lines that are "in sync", and the other contains lines that are "out of sync".

In Sync
Out of Sync

Checking Line Sync

The easiest way to check line sync is to use OpenTTD's measuring tool. Starting at the split, count the number of straight tracks on each route until the lines merge again. Also count the number of diagonal tracks. If all routes have the same number of straight tracks and the same number of diagonal tracks, the lines are in sync. Due to the difference in length between a straight and diagonal track, it is not always safe to assume that two diagonal tracks count as one straight track (especially on very dense networks).

Measuring Line Sync

Multi-line Sync

In cases where more than 2 tracks must be sync'd, it is often helpful to remember that trains should enter and leave the set of tracks from alternate corners of the bounding rectangle. If they enter from the southwest, they should all leave via the northeast corner.

Multi-line Sync

Synchronized corners

When synchronizing tracks that go around corners, take special care to count the diagonal tracks. In some cases, it may be impossible to create an accurate sync.

File:Image needed.png
Sync around corners

X-Sync

Below is a special sync case. It uses an X crossing between two split tracks to maintain line sync. Note that while an evil-X is typically frowned upon, this case is ok because both tracks should not be in use at the same time (because trains came from the same original track).

X-sync

See Also

Powered by MediaWiki
  • This page was last modified on 31 March 2015, at 03:37.