Upcoming Games

LTS mid-morning 21/10/2018 20:00:00 - 9pN1SEAp

Add a game

Upcoming Events

17/11/2018 12:00:00
01/06/2019 12:00:00

Chaining with Exeter

You are here: Home > Forum > Simulations > Released > Westbury > Chaining with Exeter

Page 1 of 1

Chaining with Exeter 11/10/2018 at 23:09 #112588
AlexRail575
Avatar
16 posts
As the title says, I've tried to chain the two sims together (on the same computer). However, in doing so, I find myself unable to set the route from Westbury signal 160 (that last signal controlled by the box, on the Down Athelney line) to signal E12 (which, in addition to being the last signal actually displayed (grey, along with the repeater E12R) at Westbury, is also the first signal controlled from Exeter).

Attempting to set a route in the opposite direction from Exeter to Westbury (Up Athelney, signals E93 to W41) works completely normally.

With Westbury alone, the route can be set normally.


Another, unrelated bug is that the only trigger for the slot for the Melksham line seems to be the occupancy of the track circuit right before signal 70 - this even for trains which have just left the Melksham line or trains which are not using it (i.e. going straight through, of which there are a few examples in the default WTT)

Last edited: 11/10/2018 at 23:44 by AlexRail575
Reason: other bug

Log in to reply
Chaining with Exeter 12/10/2018 at 08:58 #112592
headshot119
Avatar
2794 posts
Online
AlexRail575 in post 112588 said:
As the title says, I've tried to chain the two sims together (on the same computer). However, in doing so, I find myself unable to set the route from Westbury signal 160 (that last signal controlled by the box, on the Down Athelney line) to signal E12 (which, in addition to being the last signal actually displayed (grey, along with the repeater E12R) at Westbury, is also the first signal controlled from Exeter).

Attempting to set a route in the opposite direction from Exeter to Westbury (Up Athelney, signals E93 to W41) works completely normally.

With Westbury alone, the route can be set normally.


Another, unrelated bug is that the only trigger for the slot for the Melksham line seems to be the occupancy of the track circuit right before signal 70 - this even for trains which have just left the Melksham line or trains which are not using it (i.e. going straight through, of which there are a few examples in the default WTT)
What version of Exeter and Westbury are you using? And while you're at it what version of the loader?

You'll need to expand on what you mean with the slot, I can't quite understand what you mean.

"Platform 1 your Maesteg service. Platform 1A your Aberdare. Platform 2 your London!"
Log in to reply
Chaining with Exeter 12/10/2018 at 12:45 #112595
AlexRail575
Avatar
16 posts
The loader is V 4.8.2 (the latest), Exeter is 5.1 and Westbury is 4.3.

The Melksham line is just west of Westbury station, and the slot is requested by the Swindon signaller (i.e. the computer when run in singleplayer without chaining).

I mean that in some cases where the slot obviously would not need to be requested, such as a train going straight through or a train which has just left the Melksham line (and is now heading towards Swindon), the simulation still requests the slot (because the only trigger for the slot seems to be the occupancy of the track circuit before signal 74 (correction, not 70) - which is indicated as "70 slot requested" in the sim )

Last edited: 12/10/2018 at 12:46 by AlexRail575
Reason: typo

Log in to reply
Chaining with Exeter 12/10/2018 at 13:01 #112596
headshot119
Avatar
2794 posts
Online
You don't have the latest version of Exeter which is 5.1 build 1. That chains fine with Westbury 4.3
"Platform 1 your Maesteg service. Platform 1A your Aberdare. Platform 2 your London!"
Log in to reply
Chaining with Exeter 12/10/2018 at 22:16 #112599
AlexRail575
Avatar
16 posts
Oh, forgot to specify - it is build 1.

Nevertheless, I checked for updates again, found none, and tried chaining again - now it kind of works, but, unusually, the path for the signal is reserved in two parts, starting with the track circuit that is furthest away from the signal - which it does not do in single player...
[attachment=9858]Signal 160.png[/attachment]

Post has attachments. Log in to view them.
Last edited: 12/10/2018 at 22:17 by AlexRail575
Reason: checked for myself

Log in to reply
Chaining with Exeter 13/10/2018 at 08:44 #112603
Stephen Fulcher
Avatar
1415 posts
Have you tried connecting them the other way around?

Ie of you have connected Westbury into Exeter, then instead try connecting Exeter into Westbury, or vice versa

Log in to reply
Chaining with Exeter 13/10/2018 at 09:17 #112605
Peter Bennet
Avatar
4413 posts
AlexRail575 in post 112599 said:
Oh, forgot to specify - it is build 1.

Nevertheless, I checked for updates again, found none, and tried chaining again - now it kind of works, but, unusually, the path for the signal is reserved in two parts, starting with the track circuit that is furthest away from the signal - which it does not do in single player...
[attachment=9858]Signal 160.png[/attachment]
Not something I recall noticing before. I presume this is something to do with the chaining; it'd be interesting to see what happens with other sim pairs.

Peter

There is no such thing as public opinion. There is only published opinion. Winston Churchill
Log in to reply
Chaining with Exeter 13/10/2018 at 09:48 #112607
headshot119
Avatar
2794 posts
Online
It's perfectly normal for cross boundary routes during chaining.
"Platform 1 your Maesteg service. Platform 1A your Aberdare. Platform 2 your London!"
Log in to reply
Chaining with Exeter 13/10/2018 at 18:25 #112609
AlexRail575
Avatar
16 posts
Oh, and another minor issue, which is just noticed - the station of Chapelton (at the Barnstaple end of the Crediton branch) is named in the sim (both in the main view and as a timetable location) as 'Chapleton'.
Last edited: 13/10/2018 at 18:26 by AlexRail575
Reason: exact

Log in to reply