Aylesbury-Calvert Token Release Button

You are here: Home > Forum > Simulations > Released > Marylebone IECC > Aylesbury-Calvert Token Release Button

Page 1 of 1

Aylesbury-Calvert Token Release Button 14/08/2013 at 22:39 #48380
grahamj42
Avatar
130 posts
The button does not work as described in the manual, making it too easy to leave a train waiting at Calvert (in my case for 5 hours without telephoning !).

1. An up train requests the token, the Token Release button flashes white.

2. Left-clicking on the Token Release button changes it to solid white.

3. The train moves forward and collect the token

4. The Token Out indicator turns solid red. The Token Release button again flashes white.

5. A left-click on the Token Release button at this point receives a 'Cannot Give' message.

6. The train arrives at the loop and returns the token. The Token Release indicator turns hollow red. The Token Release button continues to flash white, as if another train is waiting at Claydon.

7. Left-clicking on the Token Release button changes it to solid white. However, another token cannot be released in the Up direction (not tested in the down direction).

8. Right-clicking on the Token Release button changes it to hollow green, and another token can be requested.

In my opinion, the correct behaviour in conformance with the manual should be either :

4A The Token Out indicator turns solid red. The Token Release button turns hollow green, however another release cannot be given until the token is returned.

Or

4B The Token Out indicator turns solid red. The Token Release button remains solid white.

6B The train arrives at the loop and returns the token. The Token Release indicator turns hollow red. The Token Release button turns hollow green.

(The numbers refer to the steps listed above.)

A telephone call from a train delayed at Calvert would also be nice.

This behaviour was noted in v1.15a. It still occurs in v1.16.2 with a saved game from v1.15a. I haven't had 1.16.2 for long enough to verify if a new game has the same problems.

Log in to reply