There are threads about a pair of locomotives blocking the passage - I know. I can move them, start from the timetable a few minutes earlier - I know. But ... has anyone managed to get this service in Journeys? After two tries - I have completed all the tasks, I am going back to the menu, but it is not finished.. It's the last one for me niah
This may or may not work 1 - Set the junctions so you can drive forwards and couple to the offending locos. 2 - Push the locos forward, just enough to trigger the way point. 3 - stop, uncouple the offending locos and reverse your train back past the junction $ - switch the junction back and the the offending locos should then move down the adjacent track out of your way.
I will try, if the current not-the-first attempt* fails * 1 -> 2 -> then I took "the offending locos" to the most left track. Will see... THX for Yours effort o7
As reported in another ticket, I coupled to those two alien locos and drove away with them toward the Shaw mine. Well before arriving there, I was stopped by a red signal. The dispatcher informed me that I "seem[ed] to be off the path". That red is as far as I got, but after checking the line ahead for other trains and finding none on my track I backed slowly away and came here to file my report. Earlier, in a session similar to this one, I stopped just short of that pair of unwanted locos, left my engine, and entered the lead cab of the other pair. When I pressed "E" to sit in the already occupied driver's seat, I was asked whether I wanted to take control of a different session, which I later discovered is one of the many that involve returning helper locos to Cumberland. Whoever created these sessions should, in my opinion, be handed a broom and dustpan, as should anyone in charge of TSW2 quality control. No one could possibly have test driven these sessions without noticing these egregious errors.
Had the similar idea today, and actually it worked well for me. I was able to complete this service within the journey mode. Jep, tried the same and had the same experience. So I'm glad the workaround proposed by Jannerdunk worked for me.
