• ipkpjersi@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    I mean, Ghost Recon Wildlands which came out in 2017 for example has save dates written as a 32-bit date so it’s prone to the 2038 bug, I set the date to 2040 and tested a bunch of software and while you can save the date overflows and shows as 1969. I bet there are still people using 32-bit dates even if unintentionally.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      I mean, technically you could use unsigned 32bit if you don’t need to handle dates before 1970. But yes, the best course of action now is to use 64bits. The cost is pretty much nothing on modern systems.

      I’m just cautious of people judging software from a time with different constraints and expectations, with the current yardstick.

      I also wonder what the problem will be. People playing ghost recon in 2038 are going to be “retro” gaming it. There should be an expectation of such problems. Would it prevent you loading or saving the file is the question?

      • ipkpjersi@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Nope, saving and loading works on that game (and pretty much every other game I tested), it’s just you lose the date display in-game so you don’t know when you really last saved.

        • r00ty@kbin.life
          link
          fedilink
          arrow-up
          3
          ·
          10 months ago

          Yeah, that’s my point. It’ll be a retro game by 2038 and anyone playing it will know it’s “one of those quirks”

          The bigger problem is software where the date really matters.