Triple Trouble On "double Trouble"

Discussion in 'TSW Troubleshooting & Issues Discussion' started by Pipe, Jan 6, 2023.

  1. Pipe

    Pipe Well-Known Member

    Joined:
    Jan 11, 2022
    Messages:
    2,103
    Likes Received:
    4,433
    • Issue Summary: Drive the consist to Lewis where it gets uncoupled and split. The AI *should* drive the first train to Eastbourne, while you´re in charge of driving the second half from Lewis to Seaford. On the junction from the mainline to Seaford you´ll find ........ surprise, surprise ...... the first half of your train stopped on the junction which points to the branchline to Seaford. The AI signaller even clears you to proceed passing the red signal. But then you get blocked by the first train. See video.
    • Platform: PS4 TSW2
    • Game Mode: Journey
    • Route Name: ECW
    • Loco Name: Class 313
    • Service/Scenario Name + Start Time: Double Trouble
    • Step-by-Step Instructions: Follow the video. I even played the smartass by just releasing the brakes and started pushing the first train half to Seaford. But it gets you only a little further. There you get a RED and won´t be able to proceed because your train "seems off path". I think somebody posted this bug already on the forum, but without video
    • This scenario can´t be finished

     
  2. aeronautic237

    aeronautic237 Well-Known Member

    Joined:
    Sep 1, 2022
    Messages:
    3,376
    Likes Received:
    3,271
    When this happened last time, it was because AWS was activated in the AI train, which caused an emergency brake application, although it doesn't seem like this is the case in your run. I will run it on my machine to see if I have this issue and get back to you.

    EDIT: I did it successfully and am waiting for the video to upload (in which I do accidentally mess up the uncoupling because I wasn't focusing), but I just noticed you are playing TSW2. Hopefully this won't affect anything, but it did work in TSW2.

    It finished uploading:
     
    Last edited: Jan 7, 2023
    • Like Like x 1
  3. Pipe

    Pipe Well-Known Member

    Joined:
    Jan 11, 2022
    Messages:
    2,103
    Likes Received:
    4,433
    Hi aeronautic237 ,

    thanks for trying to reproduce this. Very appreciated! :)
    I´ll give it another trial as well and dismiss AWS (although I´m not sure it was on).
    I like the 313 and its journeys. Would be a pity to have this one always unfinished.
     
    • Like Like x 1
  4. Pipe

    Pipe Well-Known Member

    Joined:
    Jan 11, 2022
    Messages:
    2,103
    Likes Received:
    4,433
    Hi aeronautic237

    I´ve managed to finish this scenario. By delaying the uncoupling procedure for around 5 min. Only the TSW Gods might know what turned out differently after that. AWS wasn´t switched on anyway.
     
  5. aeronautic237

    aeronautic237 Well-Known Member

    Joined:
    Sep 1, 2022
    Messages:
    3,376
    Likes Received:
    3,271
    Hmm, that's strange. Well I'm glad it worked!
     
    • Like Like x 1
  6. Hiro Protagonist

    Hiro Protagonist Well-Known Member

    Joined:
    Apr 18, 2021
    Messages:
    485
    Likes Received:
    478
  7. Pipe

    Pipe Well-Known Member

    Joined:
    Jan 11, 2022
    Messages:
    2,103
    Likes Received:
    4,433
    aeronautic237
    Hiro Protagonist

    Thanks for your inputs. I did a search before in the forums and found some threads about this. But in my case I didn´t drive with safety systems on, so I couldn´t turn them off.
    Another workaround for this bug then is what described above: Delay the uncoupling by around 5 minutes. I arrived 8 minutes late at Seaford and got only a silver medal (if one cares!) but at least I could finish and tick this scenario.
     
    Last edited: Jan 9, 2023
    • Like Like x 1

Share This Page