Railway/Train path finding: Revision history

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

16 December 2023

24 September 2023

31 August 2021

1 June 2021

25 February 2021

3 February 2021

8 December 2020

5 December 2020

3 December 2020

26 September 2020

17 July 2020

16 July 2020

29 April 2020

25 March 2020

12 October 2019

16 July 2019

  • curprev 12:5712:57, 16 July 2019Bilka talk contribs 6,400 bytes +187 Updated using source code - later point means *needed signal* - the signal in your example simply wasn't needed (not within breaking distance)

10 July 2019

  • curprev 03:0403:04, 10 July 2019Supply talk contribsm 6,213 bytes −137 couldn't observe this in 0.17.55, train did not reroute simply by entering a (very, very long) block, and only did so a few seconds later when the braking point reached the red signal
  • curprev 02:3402:34, 10 July 2019Supply talk contribsm 6,350 bytes −42 updated for 0.17.38 (tested in 0.17.55 at least). note that the recalculation is not instant, but takes around half a second (a train was observed decelerating from ~210km/h to ~160km/h before rerouting and accelerating again)
  • curprev 02:2502:25, 10 July 2019Supply talk contribsm 6,392 bytes −12 Undo revision 174227 by Supply (talk) nevermind, I misunderstood 'invalidate' as 'close' Tag: Undo
  • curprev 02:2002:20, 10 July 2019Supply talk contribsm 6,404 bytes +12 disambiguation (path and route are being used interchangeably here). only braking distance seems to matter as of 0.17.55

22 May 2019

28 November 2018

4 October 2018

16 January 2018

30 December 2017

23 December 2017

9 November 2017

23 October 2017

21 December 2016

28 June 2016

7 March 2015

26 February 2015

9 January 2015