New Player Pointers - Revision history

Maqifrnswa: /* TREES */

2016-08-12T20:15:38Z

‎TREES

Maqifrnswa: /* JAM PROOF Signals */

2016-08-12T15:33:43Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-12T15:05:24Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-12T15:04:54Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-12T14:53:08Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-12T14:33:23Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-12T13:57:56Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-10T14:13:45Z

‎JAM PROOF Signals

Maqifrnswa: /* JAM PROOF Signals */

2016-08-10T13:57:04Z

‎JAM PROOF Signals

Maqifrnswa: /* TREES */

2016-08-10T13:46:57Z

‎TREES

@@ Line 84: / Line 84: @@
   Entry-> split - >SIGNAL 1 -> X number of spaces -> SIGNAL 2 -> split-> SIGNAL 3
 That means if X< train length, SIGNAL 1 should be a combo, SIGNAL 2 should be a combo (or NOTHING), SIGNAL 3 should be exit. If X >= train length, SIGNAL 1 should be an exit, SIGNAL 2 should be entry, and SIGNAL 3 should be determined by what follows using the same logic. There should be normal signals (with normal spacing) between any exit and the next entry signal.
-* in between two consecutive combos, fill with normal gap combos. This sends a stronger signal to pathfinder about what's going on
+* in between two consecutive combos, two philosophies: do not signal versus normal signal.
 ==== PBS TREES ====
 * using a pbs to split, pretend like the output is an exit signal in the normal presignal tree: leave one train length before next signal. If you can't fit a train length - it is similar to the combo signal in pre-signaling. If using a PBS, DON'T PUT ANY SIGNALS between the first entry PBS and wherever you can put the exit signal. Subtle difference - PBS splits start counting after the PBS signal, while pre-signals start counting at the location of the exit pre-signal.
 * don't mix PBS and pre-signals in same tree

@@ Line 65: / Line 65: @@
 * Keep signals every 2 squares (that is, signal-blank-signal).
 * signal right before and after splits
-* SAFEST: After split, leave one train length of no signals to guarantee that no train will block the split.
+* SAFEST: After split, leave one train length of no signals to guarantee that no train will block the split. If trains do back up, you can place a signal at the back of the last train after the split to let another train fit after it
 * FASTEST: More accurately, you need to leave an integer number of train lengths worth of signals immediately before the next place a train can stop (i.e., the next split). The number of signals should then be a multiple of
   TL_in_signals = ceil(TL/SD)
@@ Line 81: / Line 81: @@
 === TREES ===
-* after a presignal tree (entry->zero or more combo->exit), leave exactly one train space of no signals after last exit before next signal to prevent blocking of the split. Start counting at the exit pre-signal. If you can't fit one train length, it means you need to use a combo signal and move the exit after the next split!!  With a train length of 5, if you have
+* after a presignal tree (entry->zero or more combo->exit), leave exactly one train space of no signals after last exit before next signal to prevent blocking of the split. Start counting at the exit pre-signal. This gap should not slow down the network since you split, and there is a second line! Basically, you are using the gap itself as a signaling mechanism. If you can't fit one train length, it means you need to use a combo signal and move the exit after the next split!!  With a train length of 5, if you have
   Entry-> split - >SIGNAL 1 -> X number of spaces -> SIGNAL 2 -> split-> SIGNAL 3
 That means if X< train length, SIGNAL 1 should be a combo, SIGNAL 2 should be a combo (or NOTHING), SIGNAL 3 should be exit. If X >= train length, SIGNAL 1 should be an exit, SIGNAL 2 should be entry, and SIGNAL 3 should be determined by what follows using the same logic. There should be normal signals (with normal spacing) between any exit and the next entry signal.

@@ Line 72: / Line 72: @@
 So a TL = 7 and SD of 2 needs ceil(7/2) = 4 signals for one train length. (you always start with a signal, then each train starts with a no signal square and ends on a signal square, the last signal is removed = 1+ ceil(TL/SD-1)
 ** So drop a signal, auto-complete it backwards, cound number of signals - and make sure it is a multiple of TL_in_signals
-** or put a signal at the last safe place a train can stop
+** or put a signal at the last square of the last train that can fit while waiting
 === synced splits (bridge tunnel) ===

@@ Line 72: / Line 72: @@
 So a TL = 7 and SD of 2 needs ceil(7/2) = 4 signals for one train length. (you always start with a signal, then each train starts with a no signal square and ends on a signal square, the last signal is removed = 1+ ceil(TL/SD-1)
 ** So drop a signal, auto-complete it backwards, cound number of signals - and make sure it is a multiple of TL_in_signals
 === synced splits (bridge tunnel) ===

@@ Line 67: / Line 67: @@
 * SAFEST: After split, leave one train length of no signals to guarantee that no train will block the split.
 * FASTEST: More accurately, you need to leave an integer number of train lengths worth of signals immediately before the next place a train can stop (i.e., the next split). The number of signals should then be a multiple of
-  TL_in_signals = floor(TL/SD)+1
+  TL_in_signals = ceil(TL/SD)
   TL =train length
   SD = signal distance
-So a TL = 7 and SD of 2 needs floor(7/2)+1 = 3+1 = 4 signals for one train length.
+So a TL = 7 and SD of 2 needs ceil(7/2) = 4 signals for one train length. (you always start with a signal, then each train starts with a no signal square and ends on a signal square, the last signal is removed = 1+ ceil(TL/SD-1)
 ** So drop a signal, auto-complete it backwards, cound number of signals - and make sure it is a multiple of TL_in_signals

@@ Line 65: / Line 65: @@
 * Keep signals every 2 squares (that is, signal-blank-signal).
 * signal right before and after splits
-* After split, leave one train length of no signals to guarantee that no train will block the split.
+* SAFEST: After split, leave one train length of no signals to guarantee that no train will block the split.
 === synced splits (bridge tunnel) ===
 * signal immediately before and after split at the entrance -- and immediately before and after join. Entrance: entry pre-sig -> exit presig. Exit: normal -> normal.
-* After the exit presignal on the entrance of the doubled bridge, leave one train length before starting signaling again (see reasoning in TREES below)
+* After the exit presignal on the entrance of the doubled bridge, leave a signal gap as described above
 ** "You should never have a signal between the exit signal and the bridge as this breaks the entire workings of the pre-signals and the bridges may break horribly" https://blog.openttdcoop.org/2010/07/27/building-101-double-bridges-and-you/
 * You really need three signals at start and end. If you're missing one, it won't work some times. Use PBS on entrance side if limited on space, but you must have both tracks of the output end signaled, otherwise both bridges will will be on the same block

← Older revision		Revision as of 14:13, 10 August 2016
Line 80:		Line 80:
	==== PBS TREES ====		==== PBS TREES ====
	* using a pbs to split, pretend like the output is an exit signal in the normal presignal tree: leave one train length before next signal. If you can't fit a train length - it is similar to the combo signal in pre-signaling. If using a PBS, DON'T PUT ANY SIGNALS between the first entry PBS and wherever you can put the exit signal		* using a pbs to split, pretend like the output is an exit signal in the normal presignal tree: leave one train length before next signal. If you can't fit a train length - it is similar to the combo signal in pre-signaling. If using a PBS, DON'T PUT ANY SIGNALS between the first entry PBS and wherever you can put the exit signal
		+	* don't mix PBS and pre-signals in same tree