No not sure if they are AI though i havent done the route properly yet they arent on my timetable anyway
No there aren't. Already been mentioned by the dev, Voyagers didn't exist when the timetable was made (it's been sitting with DTG for like 8 months!)
I've not had a chance to look at it yet since I'm at work but from what I've read I don't understand why it's taken so long to be released, given basic things like the positioning of the trains at Leven is still not fixed.
Playing on PS5 driving the 158 and there are no onboard announcements, it's slightly confusing does the update refer to the TSW 6 core feature announcements or what Rivet implemented when Fife circle first released?
Playing a night time service in the new timetable and Edinburgh Waverley seems to have no night time lighting at the station? Is anyone else experiencing this?
I’m on PC and also noticed that the on-board announcements aren’t working on the 158. The only announcement that happens is right at the beginning. It says “Welcome to the ScotRail service to” and then nothing, and then “The next station is” and then nothing. I haven’t tried it with the 170, so I’m not sure if it’s just the 158 or if it’s the timetable as a whole.
Looks like quite a bit of work has gone into the route the scenery looks better the new timetable is great
I just tried loading into a few services to see if I could get announcements to work on any services. It seems like the announcements work on services using the 170, but most if not all services using the 158 don’t have working announcements, they only play the beginning spiel with no stations noted. I also noticed that some 5 car services don’t play any announcements at all, not even the broken beginning spiel.
Still a pain they don’t include the freight services from England that go on the Fife circle line and then all the way down to Aberdeen ( I mean yeah it’s not a daily service but still should have been added, like two to 5 every few days, some on a request basis)
I have genuine empathy with Skyhook on this... The Sprinter timetable couldn't have been released at a worst time. You have the ongoing core issues, along with overall low player morale because of the core issues effecting other DLC and showing no sign of improvement. Overall these issues 'spill' into Skyhooks 158 timetable and any small niggles it may have will feel exaggerated more then what they actually are. I think we as a community should cut them some slack and be considerate. I've noticed a few small issues but nothing I'd class as extravagant. The two issues I've noticed are the following: Class 158 running sounds at low speed seem to be more quiet since the update (I could be wrong, but maybe the 170 has caused this in some weird way?). The running sounds could be louder to give the sensation of moving at low speed. And the lighting at Edinburgh Waverley seems to be temperamental. I loaded in one service and they were off. And loaded in another and it was working perfectly okay. Outside of that I'd like to congratulate them on bringing this route to life. It will be nice one the Inter7City sets are released along with the XC 220 at some point. It's a lovely and a lot busier route now. Was worth the wait to bring this route to life! So credit where credit is due.
Well the scotrail class 43 is basically confirmed at this point but I would also love to have the class 220 and it better include the one per day run from Aberdeen during the morning and then the night trip
I have the same There is an initial announcement when loading in Welcome to this Scotrail Service to [silence], calling at [silence]. Then no announcements at all when approach or at stations.
Pretty sure they don’t go through the Fife Circle - they go through Stirling then across to Dundee iirc.
6A65 0600 Oxwellmains Lafarge Colas toCraiginches Aberdeen C.Ra (Normally these services, not sure if Oxwellmains is actually England or not )
Not sure yet but probably separate since one is GWR and the other is scotrail and well scotrail sure as hell can’t replace the hst at the moment
As far as I can see that one goes via Stirling and Perth so not on Fife Circle, but the evening return journey DOES go on the Circle. Not sure if it runs light or not. Oxwellmains is still Scotland incidentally, it’s to the east of Edinburgh.
OK, here's one: the 158's engine sounds just cut out for no reason. I'm driving a magic train powered by pixie dust now (also, the wiper bug is still not fixed. It seems on every Sprinter in the game the wipers make two or three cycles and freeze.)
How many services do you get with the express freight layer? and second do you need the 66 pack + the scotrail express route or just the pack?
The layer selector says that I have all the required DLC and that it’s enabled (The layer isn’t greyed out), but the only Class 66 services I have available are the RHTT services, so I think the layer might just be AI. I believe that the layer only requires the 66 pack, it doesn’t seem to require anything from the Edinburgh-Glasgow route itself.
158 announcements don't work on Edinburgh-Glasgow either. Also, I'm a bit miffed that this is a separate timetable, and not an augmentation of the very sparse default TT.
Give 'em time and I'm sure they will include the 220 on FCL at some point. I'd also like for Skyhook to fit the 220 and 170 onto the MML too to spice it up a little bit!
Well well well. The 3, 66 services are LOVE, the track monitor doesnt show the freight speed limits only service train limits, so constantly overspeeding. No Cowdenbeath services, and 158 in the timetable shows, 2 doubled up trains, a scotrail 158 and a leven branch livery train. Twice, but same services. Why? A bit of a mess after waiting so ling for the new timetable. Tut tut
MML needs AI-only 158s that run from Nottingham/Derby to off the map locations such as Mansfield, Worksop, Grantham, Liverpool, Norwich or Crewe that just don't exist
Reading the notes of todays patch, and it seems to suggest the ScotRail Class 170 has been updated to the BCC 170 standard? Could someone read it and make sure I'm not going mad... Would definitely bring me back to the route frequently knowing the 170 has been updated properly and with Skyhooks timetable.
Having had a chance to play it now I've noticed the timetable is pretty sparse at night. The last 170 service on the timetable is at 20:43 which isnt right. On the positive side I can see they've done a bit of work on the scenery and I do like that they've put in services that don't stop at every station which is a good thing. I still overall feel a bit underwhelmed given the wait for it.
I kinda get why, by it does seem a bit funny that there a layers for a train that doesn't exist (Scotrail HST), but not for one that does exist in game (voyager). Hopefully it's added sooner than waiting another 16 months
These are not driveable with the 158 in Leven livery, only the one with SR livery. Headcode 2G... I believe.
The Skyhook post on their Discord page spoke volumes to me. Very easy to agree and understand their frustrations.
I think all third parties are going to get the shaft one way or another by DTG at the moment. The structure of development for TSW is just a shambles, the way DTG communicates is now a shambles, the core game is in shambles. On one hand it’s a shame, on the other though I hope all these issues & frustrations put enough pressure onto DTG to actually do something. Im not saying that the third parties themselves aren’t making mistakes, but AAS got shafted big time by DTG’s complete lack of testing, Skyhook are now going to get why is X not there, despite DTG holding the timetable hostage for what, a year?
According to them they didn’t have enough capacity to do full testing so it was handed to DTG to do so. I don’t think it’s great from AAS (and have left AAS feedback on that accordingly) but if DTG agreed to it & then passed what we got through QA, they really dropped the ball.
On the other hand, as a developer getting paid for the end result you could argue that it was AAB’s responsibility to have sufficient testing capacity in place when they first set up the project. And they should never have agreed or handed off the route for publication with that issue still outstanding. They should never have needed to rely on DTG.
As far as I'm concerned, they both deserve a bit of flak for the botched release. Both parties should have seen that it wasn't quite ready and held off release until it is/was.
