Dlcs Port Over Tsw Iterations

Discussion in 'TSW General Discussion' started by pedro#1852, Nov 2, 2025 at 12:10 AM.

  1. pedro#1852

    pedro#1852 Well-Known Member

    Joined:
    Feb 23, 2024
    Messages:
    598
    Likes Received:
    973
    a discussion I want to start is, is it just me or does anyone else notice that when a dlc is ported to a new tsw iteration, new bugs appear out of nowhere? bugs that didn't exist in the previous iteration (in which the dlc was released)

    i.e, a dlc played in the iteration in which it was released has fewer bugs than its ported versions in more recent iterations
    is it just me or does anyone else notice this?

    this invariably leads to the discussion that perhaps this practice of porting dlcs isn't very beneficial, which only happens because dtg has this cursed practice of releasing a "new" tsw iteration every year...
    what do you guys think about this?
     
    • Like Like x 1
  2. UnlimitedMagic

    UnlimitedMagic Well-Known Member

    Joined:
    Nov 28, 2018
    Messages:
    1,196
    Likes Received:
    1,539
    Idk if this issue sprawled in TSW 6 but I had a service in scenario planner to have 2 paths. One being Paddington to Hayes and then the other just going back. On the return for some reason I had to open/close the doors on the opposite side at each stop to proceed? Bit weird. Not sure it’d be worth reporting aswell
     
  3. spikeyorks

    spikeyorks Well-Known Member

    Joined:
    May 31, 2023
    Messages:
    1,512
    Likes Received:
    2,677
    That bug has been happening since DTG 'invented' path chaining. I think the issue here is that the original route wasn't built with chaining in mind so if it works "great" but if it doesn't "tough". Hopefully this will have been address in the new version of GWE coming along shortly.
     

Share This Page