summaryrefslogtreecommitdiff
path: root/known-bugs.txt
diff options
context:
space:
mode:
authorfonsinchen <fonsinchen@openttd.org>2013-11-16 17:52:00 +0000
committerfonsinchen <fonsinchen@openttd.org>2013-11-16 17:52:00 +0000
commite6668f24b508b079aa4525d06abd2ea5aa9e641d (patch)
tree1131c83af8530d3e897201e02f0d92b735988bf9 /known-bugs.txt
parent6fc653d2d729d8a5c0efeba9f588e6523c3ea13d (diff)
downloadopenttd-e6668f24b508b079aa4525d06abd2ea5aa9e641d.tar.xz
(svn r26013) -Revert (r25495) [FS#5684]: Having trains miss a platform that is just being modified is less of a problem than having trains stop twice without moving.
Diffstat (limited to 'known-bugs.txt')
-rw-r--r--known-bugs.txt10
1 files changed, 10 insertions, 0 deletions
diff --git a/known-bugs.txt b/known-bugs.txt
index a8591e965..36cae15aa 100644
--- a/known-bugs.txt
+++ b/known-bugs.txt
@@ -434,3 +434,13 @@ Inconsistent catchment areas [FS#5661]:
search from a station could be changed to use the actual tiles, but
that would require considering checking 10 by 10 tiles for each of
the tiles of a station, instead of just once.
+
+Trains might not stop at platforms that are currently being changed [FS#5553]:
+ If you add tiles to or remove tiles from a platform while a train is
+ approaching to stop at the same platform, that train can miss the place
+ where it's supposed to stop and pass the station without stopping. This
+ is caused by the fact that the train is considered to already have stopped
+ if it's beyond its assigned stopping location. We can't let the train stop
+ just anywhere in the station because then it would never leave the station
+ if you have the same station in the order list multiple times in a row or
+ if there is only one station in the order list (see FS#5684).