Exeter v5.0

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

" said:

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

E160/E260 also clear to Yellow when routed up the bank to E213/E313 without a route set and clear to E215/E315. this has never been the case previously, although it could be correct for the rebuild.

" said:

" said:

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

E160/E260 also clear to Yellow when routed up the bank to E213/E313 without a route set and clear to E215/E315. this has never been the case previously, although it could be correct for the rebuild.

This is correct now - it's coming down the bank that there is a requirement for the exit signal to be off

I haven't updated yet, but thanks for the update Peter.

The manual suggests that pre-1986 mode only differs in respect of Tiverton Junction, which would mean that it is strictly a small window of one year from May 1985 to May 1986, as May 1985 was when the Exeter St Davids remodelling took place (and that would be a bit more complicated to replicate).

From memory the biggest differences were a down through line (between p1 & p3), and the connections to Central were from P3 & P4 (I don't think P1 had one at all, certainly it was the main platform for services towards Dawlish). That provided a few more potential conflicts at that end of the station!

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

E3/203 to the South Devon should clear with a Green aspect (and stencil indication "DV", but SimSig doesn't have them) not a Yellow

See: http://photos.signalling.org/picture?/16771/category/1620-2015_october
(Not my pic)

Just started playing on this, looks good.

One thing I have noticed which doesn't seem to have been mentioned is that the crossings near Norton Fitzwarren (Bradford on Tone, Victory) don't seem to work, the indicators stay on R as a train passes, certainly in the Up direction.

Here's something interesting, with the default V5 timetable, 1c99 arrived into p1 EXD slightly early, and as it's timetabled to sit for 4 mins anyway I decided to "call on" 5L20 as I worked out both would fit. That worked fine, and 1c99 could leave on time at 04:08 - I didn't notice until I got a penalty that red-cow barriers did not raise even though auto was ticked, maybe because the route was a call on not a full route. (from E688).

2 more possible bugs:

1. Route Set E604-E606-E608-P6 @ Taunton, when headcode steps into P6, blank headcode also inserted into P5. Doesn't do it if E606-E608 is cancelled before setting E608-P6

2. Train timetabled to exit at Meldon Quarry, instead loses timetable, says terminated and doesn't fall off

I’ve done a little research into the problem with the Totnes loco sidings (spurred on by the fact that I decided to introduce a friend to Project X). Timetable validation fails routing from Totnes platform 2 into Totnes loco sidings, when it clearly should succeed (in fact that’s the only route by which trains can enter the sidings). If one contrives to get a train into the sim running on such a timetable (not too difficult, either by editing the timetable of a running train or by having the train enter as a different ID and then take the timetable in question as a new working), it seems like it will usually work properly.

I am pretty sure that one time the train decided to turn around and point up in Totnes 2, despite arriving in the down direction and despite the down direction being the right direction to access the sidings, but I can’t reproduce that now.

Exiting the loco sidings, on the other hand, appears to work flawlessly and validate without any trouble.

Great work!

Just one things to report, don't think its been mentioned elsewhere. At Dawlish Warren E223 on the Down Loop is a fixed red, not a limit of shunt.

There seems to have been a topic merge here of Exeter v5.0 thread and Derby station Via Buttons thread. :unsure:

" said:

I’ve done a little research into the problem with the Totnes loco sidings (spurred on by the fact that I decided to introduce a friend to Project X). Timetable validation fails routing from Totnes platform 2 into Totnes loco sidings, when it clearly should succeed (in fact that’s the only route by which trains can enter the sidings). If one contrives to get a train into the sim running on such a timetable (not too difficult, either by editing the timetable of a running train or by having the train enter as a different ID and then take the timetable in question as a new working), it seems like it will usually work properly.

I am pretty sure that one time the train decided to turn around and point up in Totnes 2, despite arriving in the down direction and despite the down direction being the right direction to access the sidings, but I can’t reproduce that now.

Exiting the loco sidings, on the other hand, appears to work flawlessly and validate without any trouble.

Can't find any problem with Totness loco - timetabled a train from Buckfastleigh to loco and back which worked fine.

Please see attachment. I have checked for updates and there are none.

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

Perhaps I'm being dense. I only see V4.0 available, is V5 limited release?

" said:

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

Should these shunt routes be permissive and clear if the line is occupied?


Peter

" said:

" said:

Another bug (I assume):- Unable to call call-on routes from E260 or E160 towards Exeter Central. Clicking on the white triangle for either E213 or E313 kills the flasher (Entry call) on E160/260 as the case my be) as starts a new flasher on E213 or E313 (whichever you clicked on).

Should these shunt routes be permissive and clear if the line is occupied?


Peter

I think its a terminology Mix up. in previous versions E160/260 would only clear if E213/313 were showing a proceed aspect so you could set a shunt rout up the bank on the white triangles to let a loco run round for instances, without needing the full route.

in the current version this is null and void as E160/260 will clear with E213/313 at danger, however the white triangles are still en situ and if you try to use them, the route fails to set and the sim thinks you've selected E213/313 as an entrance signal.

I suspect the shunt routes have been removed but the triangles have been left.