PC 12/5 Patch

Discussion in 'TSW General Discussion' started by Sharon E, Dec 6, 2022.

  1. Sharon E

    Sharon E Well-Known Member

    Joined:
    Dec 9, 2016
    Messages:
    2,080
    Likes Received:
    2,056
    My Steam is not showing any dl yesterday? Did anyone else not get this one? I have been checking Steam since it was announced yesterday and have seen no dl.
     
    Last edited: Dec 6, 2022
  2. rennekton#1349

    rennekton#1349 Well-Known Member

    Joined:
    Jun 5, 2022
    Messages:
    7,618
    Likes Received:
    4,920
    I got the update yesterday. Have you tried restarting steam? You'll know the update went through if you no longer get crashes when exiting tsw.
     
  3. Sharon E

    Sharon E Well-Known Member

    Joined:
    Dec 9, 2016
    Messages:
    2,080
    Likes Received:
    2,056
    If that is what you saw, then I ran something yesterday afternoon late EST and got the UE crash screen on exit. I did get a second dl this am, but it has the Steam logo on it not TSW3. I will be running the new DB route later today so will see.
     
  4. Sharon E

    Sharon E Well-Known Member

    Joined:
    Dec 9, 2016
    Messages:
    2,080
    Likes Received:
    2,056
    OK, no UE crash on exit after a brief run on the new route.
     
  5. rennekton#1349

    rennekton#1349 Well-Known Member

    Joined:
    Jun 5, 2022
    Messages:
    7,618
    Likes Received:
    4,920
    I have also tested it on other routes and no crashes on exit anymore
     
  6. FredElliott

    FredElliott Well-Known Member

    Joined:
    Feb 12, 2022
    Messages:
    1,568
    Likes Received:
    3,001
    Haven't there been a substantial amount of updates since 12th May
     
  7. rennekton#1349

    rennekton#1349 Well-Known Member

    Joined:
    Jun 5, 2022
    Messages:
    7,618
    Likes Received:
    4,920
    There have. The specific issue OP was talking about has been present ever since tsw3 released. It was said to have been fixed in a previous patch which didn't fix it. So they fixed it again in the December 5 update which actually fixed the issue now
     

Share This Page