Edinburgh v5 issues.

Hap in post 130154 said:

That's not gonna work. Track layout changes and line speed changes won't give you a decent representation of the current real life line. Also QST platforms aren't as they are now for 380/385s in multiple formations.
Some of these changes are the uplifting of the DGL at Greenhill upper, and a new slip from the main line to the Down Branch/Down Perth. line speed raised.
Larbert Down side lifted and made into a DPL. Up side a CE siding. Colour light signalling on all areas of DBL except the Up home and Down Section.

Since the EMUs have been fully integrated onto the lines they now work, all the timings have been made to take into account 1. DMUs running and 2. HST running.

The platform lengths on CScot match those given in the current sectional appendix. The lower speed limit for the Branch line at Greenhill (40 on sim vice 70 in real life) isn't brilliant but can be lived with. Everything else you've listed is more cosmetic- while not fully accurate, it shouldn't functionally affect the running of a modern TT, unless there's a real show-stopper that I've missed?

Agreed that a modern Edinburgh TT isn't remotely possible.

Sorry to break another Sim!

Calvin

Found an odd one, possibly stopping-position related. I routed 1E07 from E482 (line W) through P11 to its booked P10. However rather than stopping in P10, it called to complain it was waiting at E432. I cleared E432 (thinking perhaps it had stopped in 11 and been dispatched from the mid-platform) to E426 on the North line only for it to draw forward and then start its station duties, blocking the south end of the station.

I've noticed what appears to be an incorrect train description:

When 0S25 left Craigentinny shortly after 03:20 bound for Waverley it was a Class 67 x 2 (40m long). When it arrived at SLxW it divided with the rear portion forming 0Yll , obviously a Class 67 (20m long) which would mean that 0S25 would also be a Class 67 (20m long).
0S25 then proceeded to Mound Tunnel (Rev) prior to reversing and joining 1S25 in platform 11. However, I then noticed, as can be seen from the second screenshot (and in the Train List), that this train is described as a Class 67 x 2 (40m long) which it can't be.

Doesn't really matter, but thought that I'd mention it.

I've noticed what appears to be an incorrect train description:

When 0S25 left Craigentinny shortly after 03:20 bound for Waverley it was a Class 67 x 2 (40m long). When it arrived at SLxW it divided with the rear portion forming 0Yll , obviously a Class 67 (20m long) which would mean that 0S25 would also be a Class 67 (20m long).
0S25 then proceeded to Mound Tunnel (Rev) prior to reversing and joining 1S25 in platform 11. However, I then noticed, as can be seen from the second screenshot (and in the Train List), that this train is described as a Class 67 x 2 (40m long) which it can't be.

Doesn't really matter, but thought that I'd mention it.

bugsy in post 130192 said:

I've noticed what appears to be an incorrect train description:

When 0S25 left Craigentinny shortly after 03:20 bound for Waverley it was a Class 67 x 2 (40m long). When it arrived at SLxW it divided with the rear portion forming 0Yll , obviously a Class 67 (20m long) which would mean that 0S25 would also be a Class 67 (20m long).
0S25 then proceeded to Mound Tunnel (Rev) prior to reversing and joining 1S25 in platform 11. However, I then noticed, as can be seen from the second screenshot (and in the Train List), that this train is described as a Class 67 x 2 (40m long) which it can't be.

Doesn't really matter, but thought that I'd mention it.

Train descriptions do not get updated partway through a schedule. The only way to update a description is to have a new working for the portion of 0S25 that has remained, which would give you the option to update the description. This is the same with the characteristics, you'll notice that the Length after the divide remains at 40m in the TT window where as it will be 20m in length.

In this case its a throw up between having a slightly incorrect description for 7 sim minutes, or splitting the schedule and not being able to know where the second portion of 0S25 is going until after the divide has happened

I'm glad I read about the 5A41 issue here before I encountered it in the sim, otherwise I would've been really confused.

I was wondering, could the issue be resolved by splitting the schedule at the first Edinburgh stop?

Can't make sense of your post. Are you working things in the following sequence:

1) Highland Sleeper arrives and will ultimately form three sections (Inverness 1S25, Aberdeen 1A25 and Fort William 1Y11)
2) 0S25 Diesel loco from Millerhill joins at the West end.
3) Train detaches Inverness portion at West end for 04:15 departure.
4) Incoming Electric Loco detaches from East end and goes off to Craigentinny. If you are working to TT and not running early you then have the Inverness train at the West end of P10/11 and an unpowered consist behind it.
5) Departure of 1S25 followed by 0A25 running through to Mound Tunnel and reversing onto unpowered consist to attach.
6) After attachment of 0A25, 1A25 powered Aberdeen portion splits at West end leaving unpowered Fort William portion in P10.
7) 1A25 departs in due course.
8) 5Y11 runs out from Motorail Bay and attaches Fort William day coaches to East end of sleeper (P10).
9) 0Y11 Light diesel for Fort William portion detaches from East end after attaching Day Coaches, runs round and attaches at West End of consist in P10.
10) 1Y11 Fort William portion departs in due course.

Running to that schedule everything in your save works as expected.

Just as a thought, you're not trying to put 0A25 into P11 before 1S25 (Inverness portion) has departed, are you?

Got to admit it does take a bit of head scratching to work it all out, particularly when locos appear early.

Got to admit it does take a bit of head scratching to work it all out, particularly when locos appear early.

Dick in post 130233 said:

Got to admit it does take a bit of head scratching to work it all out, particularly when locos appear early.

That's why the more complex sims are fun to play.

Dick in post 130233 said:

Got to admit it does take a bit of head scratching to work it all out, particularly when locos appear early.

That's why the more complex sims are fun to play.

I have just downloaded the Loader version of Edinburgh and started it off to have a look.

I immediately got the same error as I have been getting on Manchester Piccadilly.

The error occurred after 1B16 had been seeded (which is the first train to be seeded) and reads:

1B16 Internal error(1B16 in Enter: EInvalidOp:Invalid Floating Point Operation

After Pressing OK another error message box appears:

External Exception C000001D

No more trains are seeded.

The error does not occur when ARS is disabled during load, just like Manchester Piccadilly, and has only occurred on my PC and 1 other for Manchester Piccadilly. My Laptop in running Windows 10.

I believe Geoff has a fix for the Manchester Piccadilly error.

Sorry to break another Sim!

Calvin

The other cautionary note is that ACI is never going to keep up with this amount of splitting and joining, and may well result in misleading TD's showing.

bill_gensheet in post 130237 said:

The other cautionary note is that ACI is never going to keep up with this amount of splitting and joining, and may well result in misleading TD's showing.

Of course, you have to bear in mind, in real life the ARS does not handle anywhere near as much ACI as SimSig's does. The sleeper is pretty much handled manually (in terms of signalling) in real life. Sometimes people's expectations are a little high of ARS...

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.