• WarmSoda
      link
      fedilink
      English
      arrow-up
      38
      ·
      11 months ago

      I love how the temporary solution is to start a new game lmao

      • Potatos_are_not_friends@lemmy.world
        link
        fedilink
        English
        arrow-up
        19
        ·
        11 months ago

        That was actually a smart hack, because Xbox had limited memory.

        If you wanted to make a comparison, it would the Morrowind bug that if you did specific things in hour 15, it’ll definitely cause your game to crash in hour 120.

      • WarmSoda
        link
        fedilink
        English
        arrow-up
        10
        arrow-down
        1
        ·
        edit-2
        11 months ago

        That was Morrowind. Pretty clever, actually.

      • TheCrispyDud@kbin.social
        link
        fedilink
        arrow-up
        8
        ·
        11 months ago

        No idea but the GOTY edition for Morrowind on the Xbox somehow had an auto saver that kicked in right before a crash.

  • Pratai@lemmy.world
    link
    fedilink
    English
    arrow-up
    22
    ·
    11 months ago

    Bethesda: Quick! Get the free labor modders to fix it before it hurts our sales!”

    • resketreke@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      11 months ago

      That’s the oldest trick in the book: appealing to nostalgia to sell more copies. Bethesda did it again!

  • TonyHawksPoTater@kbin.social
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    11 months ago

    It’d be more news-worthy if Bethesda released a game that DIDN’T start crashing more the longer you played. I remember dealing with this in Fallout 3. Here we are, 15 years later…

  • Mereo@lemmy.ca
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    11 months ago

    Basically, the game is telling players to stop wasting their time.

    • WarmSoda
      link
      fedilink
      English
      arrow-up
      8
      ·
      11 months ago

      This is more like Skyrim, Fallout, and Oblivions issue.

  • Philote@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

    Endgame was brutal. It was a 50/50 chance if you paused to save while moving it would crash.

    • chunkystyles@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      I played for around 150 hours and didn’t have crashing issues. What would you call endgame for Starfield?

      • Philote@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 months ago

        I was at around 55 hrs during endgame, which was finishing the main story line after doing most of the side quests. I think I had 1 main base with 10 - 20 buildings and equipment. I was playing on a series S. I am boggled you didn’t have many crashes, I’ve seen hundreds of reports of similar issues when I was trying to figure out what was going on.

        • chunkystyles@sopuli.xyz
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          I played on PC on the Steam version of the game. I only bothered with bases on my first playthrough. I don’t remember how long my first playthrough lasted.

    • Aganim@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      Takes me back to the days of Morrowind. Saving in Vvardenfell was also better enjoyed while not moving. Must be that NetImmerse legacy. 😋

  • Throwaway
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    3
    ·
    11 months ago

    Thats been in creation since morrowind, its only an issue due to all the clutter