I have just attempted running a south east bound Sursee to Luzern and managed to get passed Rothenburg and the service is stopped at A12 and it will not change to clear despite nothing ahead and having been sat here for 20 minutes. It seems Luzern bound services are unplayable because of this at A12 and on outbound towards Sursee encountering a variety of problems with the units not moving off on systems issues. I have accumulated 144km on this route but because of this problem not one service is shown as completed. Why is this happening with this route?
I´ve done several services in both directions without any trouble. What exact service are you running? I´ll try to reproduce this.
The problem persists approaching from Sursee A12 where the line joins from where another AI service is sat but does not move, so the signal is red and will not change 21116 is one of the affected schedules. I have got a train come in to Luzern on AI to start at Luzern, I get on it and the brakes will not release. I have restarted it and it is the same every single time, I have brake of power off and done brake full reset multiple times but it is not releasing the brakes. I have read the manual through twice and same instructions followed but yet it will not release.
I´ve done this service twice. Without any problem or waiting. But then again: In TSW2 on PS4, not PC. So, there might be different AI traffic schedules. Sorry I couldn´t be of more help here. As for your brake issue, just guessing: You ran inadvertedly into emergency braking with the e-brakes. In order to get running again, you must push the train brake lever fully to emergency and back to release. That should release the brakes for good.
I have tried the full brake reset multiple times but it hasn't worked, there is just nothing building up air at the no 2 end.
I can confirm on TSW3 - Playstation 5 - Service 21116 gets stuck at Red at Signal A12. I can't even see why. Signals down the line are various different colours without any trains in sight. Also tried 21122 same result. I've finished that one in the past so looks like this is newly broken in TSW3. I just tried the same services in TSW2 and they are working fine. So looks like the 'fixes' in the TSW3 version have broken a fair chunk of the timetable but at least the TSW2 version works until that gets 'fixed' as well..
Oh joys, one of the most important aspects of a train simulator and the developer still can't get it right...
Oh Dear, why would I not be surprised. Automatic updates switched off already because of DTG´s "patches".
I‘ve backed up all my TSW2 DLC on PC in case the same bug is introduced in TSW2. So hopefully I can just copy it back if the worst happens. This is my most local route so I play it often. I‘ve reported the bug on Rivet‘s forum. Hopefully Jasper_Rivet will pick it up from here as well.
Cheers guys, we could reproduce that issue. I'll forward the bug to our devs to have a look at and update you once I know anything new.
It doesn't look like a case of "the developer getting it wrong" but a bug! It was working in TSW2 it seems but not TSW3.
To be fair, I was a) in a bit of a grump about the sim in general when I posted this, having got a crash one night followed by a red signal bug in a DTG route the next, which resulted in another two completely wasted sessions, b) I didn't realise this was a Rivet route/bug. DTG seem to have endless signalling bugs in their routes, and creating the same red signal bugs repeatedly would be a case of still not getting it right in my book. But if this is a Rivet-specific issue and not typical for them, fair enough.
Jasper_Rivet do you know if there is any update on this? Still getting stuck at the red light. Thanks
Was there anything mentioned about the missing drivers in rivets dlcs? Seems since luzern sursee in their addons the drivers of the a.i are invisible. Same in iow2022 & edinburgh glasgow. Nothing gamebraking, but a bit immersion braking since its kept quiet by devs.
