a problem with timetable with my own route

General discussions

Moderator: senjer

User avatar
Sjoerd
Posts: 5645
Joined: 26 Dec 2014, 21:14
Location: Alphen aan den Rijn

Re: a problem with timetable with my own route

Post by Sjoerd »

Atomic_WinsS wrote: 28 Jun 2017, 12:35 am i suppose to get this
http://prntscr.com/fp5dh2
There is a bug in the train detection between track 168/171 and 173, as MP85 mentioned two days ago. This bug causes a false 'occupied'-signal in the CVL on the switches after you have left them, as the CVL thinks you are still there.
Meanwhile, you are entering track 173. But as the CVL thinks you haven't left the earlier switch yet, it sees your train on track 173, and thinks you are a new train on the network. It then assigns your train a new train number, in your case F10033.
Now, when you enter a next station, the DRIM is expecting your train with the number you assigned to it in the activity, but instead a train with a new F-number arrives. It does not recognize this, and so it will then display "bestemming onbekend" (destination unknown).

Therefore, you should avoid setting a route between track 171 (or 168) and 173 in all activities, until this bug is (hopefully) fixed in the next release.
CEO of the Rijndam Electrical Transport company :D
Post Reply