• stringere@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    20 days ago

    At least when you’re wrong about something you’re willing to keep doubling down and not see how!

    • SchmidtGenetics@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      3
      ·
      edit-2
      20 days ago

      The good news is that Griffiths managed to save the player’s, uh, save. In a further update, he posts a video of the game running flicker-free in the same area on the same save. Per Griffiths, the problem was a “general engine bug/limit being reached,” which means that his fix will “probably help other large bases that had this issue on Xbox.”

      So where is the save being sent back for an engine issue….? This specific fix had nothing to do with fixing a specific save issue, they got sent a save that HAD the issue, and used that to fix a generic issue. Why is everyone going on about this being a save fix?