Edinburgh v5 issues.

Woodhead Signalman in post 130203 said:

Hi, I just had a phone call from a 'shunter' which asked me if i wanted to let 6S01 run 15 minutes earlier than booked from the Berwick-on-Tweed direction. Shouldn't I have the got the call from the signaller at Berwick-on-Tweed signal box, not a 'shunter'? Looks like possibly a glitch in the code somewhere. Thanks for attention in this matter. Alan.

Ta, Mantis 31261 raised.

This isn't an issue, more a question. Can anyone explain the purpose of 5Z01?

swiftaw in post 130326 said:

This isn't an issue, more a question. Can anyone explain the purpose of 5Z01?

Suburban line route refreshers. SR only have/had limited ECS runs around the sub, this allowed us to keep the route as a diversionary for pax services if Haymarket went down. We'd route out to the East and back onto the Midclader, E&G, Fife or shed, though services were prioritised due to the long block sections others would be caped (cancelled) or terminated short.

To date, the last time a full route refresher happened on the Sub was when the Borders line was being tested, both Edinburgh/Tweedbank drivers and guards were refreshed on it. Now only Edinburgh/Tweedbank Drivers sign it completely, all other depots would require a route conductor.

About 15 minutes later a train stopped at the signal as I had not received a call saying the crossing was clear. I waited another 5 minutes and thought perhaps there was a bug where you dont get the clear call

swiftaw in post 130448 said:

About 15 minutes later a train stopped at the signal as I had not received a call saying the crossing was clear. I waited another 5 minutes and thought perhaps there was a bug where you dont get the clear call

That would be too realistic! Signallers hate it when crossing users don't call back to confirm they're clear. I believe the next train has to be stopped and cautioned if the signaller suspects this is the case, causing delay.

Bit off-topic, but a feature I'd very much like. In real life one of the questions you would ask is how long the user needs to cross. Now their estimate might be off, but in SimSig you get no indication of how long the request will last (unlike with train delays for example), which makes it difficult to decide whether to grant permission to cross. We do not delay trains for user-worked crossing requests, that's lesson 2 :P

At 13:23:23 hrs, the signaller answered a call from the car driver at Dock Lane UWC-T, who requested “Three rhino to go across – 72 seconds”.

TUT in post 130451 said:

Bit off-topic, but a feature I'd very much like. In real life one of the questions you would ask is how long the user needs to cross. Now their estimate might be off, but in SimSig you get no indication of how long the request will last (unlike with train delays for example), which makes it difficult to decide whether to grant permission to cross. We do not delay trains for user-worked crossing requests, that's lesson 2 :P

Quote:

At 13:23:23 hrs, the signaller answered a call from the car driver at Dock Lane UWC-T, who requested “Three rhino to go across – 72 seconds”.

- (R082017_170503_Dock_Lane, para. 25)

When real life imitates SimSig, almost...

Not an issue (so sorry for going off-topic a bit), but it's good to see Edinburgh in the loader, AND with a loader version of the 1993 timetable. I always loved playing this one on the EXE version, but would inevitably get to a point where I just couldn't keep up with everything going on. ARS will hopefully solve some of that, so Ive just started a new game to see how I get on.

Thanks for bringing it up to date :)

I think I jinxed the sim slightly by making a post that said "not an issue but .."

It's 01.06 in the 1993 Loader TT, and I've only just had a message saying "Today is Wednesday". That's the longest I've ever had to wait for a sim to tell me which day it is! I've got a save I took immediately afterwards, should it be required.

lazzer in post 130468 said:

I think I jinxed the sim slightly by making a post that said "not an issue but .."

It's 01.06 in the 1993 Loader TT, and I've only just had a message saying "Today is Wednesday". That's the longest I've ever had to wait for a sim to tell me which day it is! I've got a save I took immediately afterwards, should it be required.

The choice of day is only published once the decision has been called. For a lot of TTs one of the seed trains will be dated so the decision is called on loading. In this case presumably the first time that the sim needed to make a decision about the day is for a train entering at or about 01:06.

Would the train that determines the day have anything specific in its TT (apart from its description saying it's the train that determines the day)?

lazzer in post 130472 said:

Would the train that determines the day have anything specific in its TT (apart from its description saying it's the train that determines the day)?

In the top right of the front tab of the TT there are two boxes for Decision and Choice. They will carry data if the train is governed by a decision. Not sure how far in advance a decision is called but you may find a train shortly after 01:06 which has the day-of-the-week decision. A lot of TT writers use DoTW for the decision name (or you can see a list of the decisions embedded in the TT on the Decisions tab of the main TT).

6Z6700 (enters 01:55) - [any] TUE | THU (which I assume means a random choice out of three days?)

The DOTW decision would of been called about a min or so before 7S34 was due to enter as that is the first train that requires a decision and as the choice is random the train that caused the decision to be called may not end up entering.

In the TT editor you have a Tab Called Decisions and this lists all the decisions that are in the timetable and under each decision is a number of choices, so when a train that is due to enter (about a min or 2 before it does) has a decision the loader goes to this list and look for the decision and selects one of the choices it then goes back to the train and looks to see if the choice selected matches any on the train if the choice does the train will enter, if the choice does not match it gets marked as having entered and the train will not enter.

for further trains that require the same decision the loader will look at the decision list see that a choice has been selected and then see if that choice matches, and then take the appropiate measure for entering or not.

Wiki entry here for more info on decisions

MarkC in post 130483 said:

In the TT editor you have a Tab Called Decisions and this lists all the decisions that are in the timetable and under each decision is a number of choices, so when a train that is due to enter (about a min or 2 before it does)

Cheers - I see how it works now - much more complex than before the update to Loader v4.5, but I think it's a better system. So are you saying that the core code now makes a random decision on which day of the week it is, and then each train with a DotW entry interrogates this decision to see whether it can enter or not?

[quote=MarkC;post=130483]Cheers - I see how it works now - much more complex than before the update to Loader v4.5, but I think it's a better system. So are you saying that the core code now makes a random decision on which day of the week it is, and then each train with a DotW entry interrogates this decision to see whether it can enter or not?

I'm currently playing the 1993 timetable and I've observed something that I don't understand when setting a specific route at Edinburgh itself.

This being when you have a train in Platform 17 that is behind E483 and you manually set a onward route either from E483 to E485 to E497 or if you set the route from E485 to E497 first then set the route from E483 to E485, E483 will only show a shunt aspect with E485 showing a full aspect.

However, let ARS set the above route and E483 doesn't show a shunt aspect but rather a full aspect so why is this?

So far from a 00:00 start, I'm now at 17:04 and it happens all the time.

Also when you have services leave Thornton Yard and the loco has to run around it's train if you route the train onto the Down Cowenbeath to ET777 either manually or ARS when the route needs to be set from ET953 (Reverse) to ET777, the signal doesn't clear at all so you have to talk the loco past the signal at danger yet if if you route said train onto the loop and run the loco around it's train then when you set the route from ET953 (Reverse) to ET779 you get a shunt signal aspect.

Why is this?

ajax103 in post 130675 said:

I'm currently playing the 1993 timetable and I've observed something that I don't understand when setting a specific route at Edinburgh itself.

This being when you have a train in Platform 17 that is behind E483 and you manually set a onward route either from E483 to E485 to E497 or if you set the route from E485 to E497 first then set the route from E483 to E485, E483 will only show a shunt aspect with E485 showing a full aspect.

However, let ARS set the above route and E483 doesn't show a shunt aspect but rather a full aspect so why is this?

So far from a 00:00 start, I'm now at 17:04 and it happens all the time.

Also when you have services leave Thornton Yard and the loco has to run around it's train if you route the train onto the Down Cowenbeath to ET777 either manually or ARS when the route needs to be set from ET953 (Reverse) to ET777, the signal doesn't clear at all so you have to talk the loco past the signal at danger yet if if you route said train onto the loop and run the loco around it's train then when you set the route from ET953 (Reverse) to ET779 you get a shunt signal aspect.

Why is this?

Platform 17 is an odd on and I am not sure why it does it, but if you click on E483 to signal E495 or E497 or E499 (missing out Signal E485) you then get Proceed aspectcs on the main signal not the shunt.