Patch Notes (and The Lack Of Them)

Discussion in 'TSW General Discussion' started by CK95, Apr 19, 2023.

  1. CK95

    CK95 Well-Known Member

    Joined:
    Apr 13, 2019
    Messages:
    3,929
    Likes Received:
    11,746
    This one is for the community team - I would like to address the often lacking patch notes.

    Recently there has been an increase in patch notes simply excluding some changes. Often you will post a list of routes & their changes, but then updates will happen to various DLC’s. I presume this will be down to an update applying to the core, and thus across various routes, but even then they don’t match up.

    The latest one posted was this:

    Update 19/04/23

    We've pushed an update to PS5 that should help address some of the issues players have been facing on the platform, please be sure to update your game before playing again.

    Please could you detail what you’ve changed? I am unlikely to buy this DLC, which has many documented issues, when all you can say is “we’ve addressed some issues”.
     
    Last edited: Apr 19, 2023
  2. tallboy7648

    tallboy7648 Well-Known Member

    Joined:
    Apr 9, 2020
    Messages:
    6,567
    Likes Received:
    10,810
    I agree. It seems that some patch notes tend to be vague. That's like if a rail company said that there is a delay on a train line but then they don't say what line is delayed and why it's delayed or a city department of transit saying that they fixed the road but don't say what road was fixed
     
    • Like Like x 1
  3. yardem

    yardem Well-Known Member

    Joined:
    Nov 16, 2022
    Messages:
    1,025
    Likes Received:
    1,109
    When they released the red lights patch, there was a lot of noise made.
    In the March roadmap, JD claimed that the fix has addressed 80 to 85% of the red light issues in the game. There is absolutely no data to base this number on. The feedback thread is still full of red light issues, including some very old ones (BR143 Tutorial on DRA) and very very new ones (Boston Sprinter's Cold as Ice scenario ends with a bunch of trains blocking the Boston South station).
    JD and DTG have been mum on this, and the red light issues are no longer on the roadmap.

    A similar approach has been taken with achievements. There's a long list of achievements that are broken. They fixed one: some BR187 achievement was fixed in December. Nothing since, and nothing in the April roadmap.

    dtg_jan If you're taking over from JD, please can you look into these issues?
    1. is DTG still working on fixing red light issues? (feedback thread is loaded with examples)
    2. why are red light issues no longer on the roadmap?
    3. is anything being done about broken achievements/trophies?
     
    • Like Like x 5
  4. ARuscoe

    ARuscoe Well-Known Member

    Joined:
    Apr 9, 2018
    Messages:
    10,832
    Likes Received:
    10,490
    Except for their ongoing auto testing, beta testing and QA testing... No data at all...
    Not saying you're not still getting red light issues but to say they've got no data simply because you haven't seen it isn't the best way to make a case.
    Matt and JD said on a couple of roadmap streams that the majority of red light issues had been fixed by changes in the core and then opened a post on the forum to ask about continuing red light issues. That doesn't mean DTG are looking into them of course but I'm sure they have a lot of reports of what redllights are happening and whether these are the same as what was happening before. Personally I'm seeing a lot less of them on BML for example

    Unfortunately DTG cannot do the simplest thing with achievements, which is get rid of them. Apparently the console companies insist
     
  5. yardem

    yardem Well-Known Member

    Joined:
    Nov 16, 2022
    Messages:
    1,025
    Likes Received:
    1,109
    Sorry, I was talking about actual testing, not fictional testing! The only testing they seem to have is from players, after release!

    I'm a software developer. When there's a bug, the first thing I do is write a unit test that reproduces the issue. When running the test, it fails. After fixing the problem, the test must pass. From now on, the test remains as part of the suite of tests that validate the code.
    Where's the test for the BR143 Tutorial, which has a known red light issue after Priestewitz?
    What about the other many red light issues posted in that feedback thread?

    Claiming "majority of issues have been fixed" without actual numbers means nothing! How many known red light issues existed before the fix? How many are left after the fix? Give me the numbers and I'll do the math for the "80 to 85 percent"...
     
    • Like Like x 5

Share This Page