Slashdot Mirror


'Forza Horizon 3' Update Accidentally Published Unencrypted Build of the Game (vice.com)

An employee at Forza Horizon 3 developer Playground Games accidentally green-lighted the wrong update file for PC players, who found themselves downloading a whopping 53GB download that turned out to be an unencrypted future build (.37.2) of the entire game intended for developers. Motherboard reports: Naturally, players who'd managed to download it yesterday had a field day leaking the information within, right down to massive posts on Imgur showing all the new cars and forum threads detailing the Porsches thought to come in an future unannounced pack. Since Forza Horizon 3 requires a constant online connection and works off of a constantly refreshing save file, anyone who played the new patch on PC found themselves slapped with an error saying their Forza profiles were no longer available. Playing it with the new build would thus effectively mean starting a new game from scratch, even if they'd dumped dozens of hours into Forza Horizon 3 since its release last September. But starting over is exactly what players shouldn't have done. The best thing they could do was shut down the game, walk away, and wait for a fix. "PC players who completed the download of .37.2 and then started a new game save will have a corrupted saved game," wrote Brian Ekberg, Forza's community manager, in a forum post. "Avoid creating a new saved game on .37.2, and only play on .35.2 to avoid this issue. As long as you have an existing save and have not created a new one on .37.2, your saved game will work correctly once the update is available."

33 of 70 comments (clear)

  1. Hah! Sure, blame the players .. by kaka.mala.vachva · · Score: 1, Insightful

    "PC players who completed the download of .37.2 and then started a new game save will have a corrupted saved game," wrote Brian Ekberg, Forza's community manager, in a forum post. "Avoid creating a new saved game on .37.2, and only play on .35.2 to avoid this issue. As long as you have an existing save and have not created a new one on .37.2, your saved game will work correctly once the update is available." Riiight - it is completely Forza's responsibility to restore saved games in this case.

    1. Re:Hah! Sure, blame the players .. by Luthair · · Score: 1, Informative

      Yea, it doesn't seem acceptable that a corrupted save from an automatic update won't be fixed.

    2. Re:Hah! Sure, blame the players .. by war4peace · · Score: 3, Funny

      Horrible analogy.
      In case of a bank, you know it's not yours because you shouldn't have received them anyway.
      In case of this game, you already bought it so you own it.

      --
      ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
    3. Re:Hah! Sure, blame the players .. by Luthair · · Score: 5, Insightful

      You say that but Halo Master Chief had a 20gb patch day-1, sadly patches in the gigabytes have become the norm. Plus these are often streamed in the background. Either way I wouldn't be suspicious of a 50gb update, though I'd be pissed and go complain online about having to wait for yet another update.

    4. Re:Hah! Sure, blame the players .. by TroII · · Score: 4, Funny

      In case of this game, you already bought it so you have a limited license to potentially use it under certain conditions as long as the studio sees fit, doesn't decide to shut off their authentication servers, and neither the publisher nor the gaming platform decide you've violated an arbitrary rule.

      FTFY

    5. Re:Hah! Sure, blame the players .. by Opportunist · · Score: 2

      You assume that the player actually noticed that the update happened.

      More and more games come now fall into the habit, at least if they're updated often and require large updates, to start their updater with the computer and keep it running, checking every now and then for updates and downloading and applying them in the background, without the user even noticing that an update occurred unless he just happens to want to play the game while the update is in progress.

      If the game is on Steam, chances are even higher that any update happens without the user even noticing it.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    6. Re:Hah! Sure, blame the players .. by Falos · · Score: 1

      Lemme check if the receipt said Blockbuster on it.

    7. Re:Hah! Sure, blame the players .. by zifn4b · · Score: 1

      You say that but Halo Master Chief had a 20gb patch day-1, sadly patches in the gigabytes have become the norm.

      That's because we have idiots managing software projects with unreasonable expectations. Therefore, we compromise by releasing stuff that isn't done and patch it up until it is actually done because you know being able to say "it was released" is more important than if the software actually works or damages the reputation of the software vendor.

      --
      We'll make great pets
    8. Re: Hah! Sure, blame the players .. by sound+vision · · Score: 1

      I've seen games with 50+ GB updates before. Especially MMOs - isn't that what this game is? Or is the always-on thing only for DRM?

    9. Re:Hah! Sure, blame the players .. by AdamStarks · · Score: 2

      From a technical perspective, it's completely acceptable. This build was never intended to be released to the public, and so there was no expectation of backwards compatibility. It produces a new save, which the old build (by definition not patched to handle saves from the future) will then apparently choke on and mangle. Unless the mangling somehow avoids losing any information, or users' saves are backed up somewhere, I don't see what can be done in this situation.

      The only thing I can think of would be to hold off on pulling the developer build until you've produced another retail build based on the last good one, with functionality patched in downcast saves generated from the developer build. But that kind of thing would probably have a minimum of something like a 1 week turnaround, which would mean leaving the development build live for a whole extra week.

      In other words, the decision to immediately pull the developer build and revert to the previous one probably makes the corruption of saves inevitable. The only hope is that they pull it fast enough that as few users as possible are afflicted.

      As for future-proofing against this kind of mishap (which falls in the general case of "Updates Breaking Saves"), you can use a versioning system that keeps saves from older builds around and writes to differently named saves with each new update. That unfortunately seems not to be what was done here...

    10. Re:Hah! Sure, blame the players .. by thegarbz · · Score: 1

      That's because we have idiots managing software projects with unreasonable expectations.

      Actually a day one patch sounds more like using the publishing window for development. Nothing new there.

    11. Re:Hah! Sure, blame the players .. by zifn4b · · Score: 1

      Actually a day one patch sounds more like using the publishing window for development. Nothing new there.

      Agreed. But just because it's "nothing new" doesn't mean it's any less stupid than it always was.

      --
      We'll make great pets
  2. Accident? by uvajed_ekil · · Score: 1

    "Accidental leak?" That results in free advertising, see above for example.

    --
    This is a hacked account, for which the owner can not be held responsible.
    1. Re:Accident? by Mr+D+from+63 · · Score: 2, Funny

      "Accidental leak?" That results in free advertising, see above for example.

      Blame the Russians and you'll get even more press.

  3. Re:At least they weren't stealing from SCO by mattyj · · Score: 1

    I don't believe that the presence of the code in Linux has ever had anything to do with it, it's the alleged copyright that SCO wrongfully staked a claim on. Then switched to trade secrets. Then licensing fees.

    They originally breached the licensing agreement with Novell and refused to defend themselves, opting instead to continue filing frivolous lawsuits against anyone using or supporting Linux, then claiming the proof was secret and they wouldn't discuss it in open court.

    Their misunderstanding of what they sued AutoZone for is a hilarious story, too.

    And when SCO tried to claim copyright on GPL'ed code.

    And then the consultants that found no evidence of copyright infringement in Linux code.

    Your view of history is severely muddled, and I'm not even sure what this has to do with videogames. SCO (and it's many incarnations) was essentially a licensee of Unix that misunderstood what Unix/Linux was and attempted to be an early incarnation of a patent/copyright troll. That 'little guy' deserved the beating they got.

  4. Data metering and caps by techno-vampire · · Score: 1

    There's a lot of people out there on a metered connection, or who have to pay extra if their downloads exceed a specified cap. I can't imagine a plan like that having enough bandwidth per month to cover a 53 GB download without extra cost. What I'd like to know is, who's getting stuck with the bill? Are the customers going to have to fork out or is Playground Games going to Do The Right Thing and cover the expense?

    --
    Good, inexpensive web hosting
    1. Re: Data metering and caps by bn-7bc · · Score: 1

      Is the meetered interner connection (appart from 3G/LTE) realy s thing outside the USA (I'm not trolling here this is an hones question), as for 3G/LTE gotas, well. Maybe thostechnologies wher never ment to replace xDSL/cable (due to limitations on pe to ce hop rf spectrum), but over eager pr people at wisp/mnos got the idea that" This if faster than xDSL (well higher bit rate at least) so we can sell our service as a replacement" I,ll admit thst in some cases, as when you are located to far from the co, or on a crappy pair of wires, unfortunatly 3G/LTE is your only choice and then those bog updayes raly are a problem, atleast with steam you can set in. Ot to download in the bacgroubd without notifying you first

    2. Re: Data metering and caps by omnichad · · Score: 1

      I think your keyboard is broken.

  5. Re: At least they weren't stealing from SCO by pixel+sorceress · · Score: 1

    Is it retro-trolling week here on Slashdot? Are we going to have a lovely old fashioned flame war about whether the Amiga or the Atari are the best 16 bit micro next?

  6. Meanhile Gog still has unencrypted games by rsilvergun · · Score: 1

    and it's no accident. I wouldn't care if I didn't need to spend an extra $100 on CPU that can handle the decryption to get decent framerates (here's looking at you Batman: Arkham Knight).

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Meanhile Gog still has unencrypted games by Opportunist · · Score: 1

      The sad part is that this often means that the cracked versions of the games play better than the legally bought ones. Talk about adding insult to injury.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    2. Re:Meanhile Gog still has unencrypted games by hairyfeet · · Score: 1

      Citation please? Because from every in depth review I've seen Batman Arkham Knightrider wasn't suffering from encryption issues but from a publisher with a severe case of not giving a fuck. They made sure it ran on the Xbone, only half ass made sure it ran on PS4 and then didn't even bother with that much for PC but let a fourth string dev house do the porting with almost no money and an extreme deadline.

      Not saying buying from GOG is a bad idea, in fact I personally will buy to GOG over anyplace else if they have a game I want, but trying to blame Arkham Knightrider on bad crypto ignores the shitty practices which are frankly par for the course when it comes to Warner Bros.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    3. Re:Meanhile Gog still has unencrypted games by scourfish · · Score: 1

      The decryption of an executable into memory is most likely not the cause of terrible framerates in games.

  7. Re:no effect by dadelbunts · · Score: 2

    You are a big racing game fan and have never heard of the Forza series? Ooooooooooooooooooook.

  8. Re:News for nerds indeed by epyT-R · · Score: 1

    Sometimes, video games are played precisely because they aren't the real thing.

  9. Blissful Ignorance? by s.petry · · Score: 2

    The lawsuit is done, as is SCO. The complaint from SCO boiled down to them LYING! Hence, they lost every single lawsuit and appeal. I'm not sure if you are a shill or just completely ignorant, but in the case of the latter there is a site called Groklaw which covered the cases start to finish. With I'll add, an exceptional paralegal pulling down PACER files, and numerous attorneys adding commentary and explanation to the proceedings.

    As one example, SCO tried to sue for source code they claimed to own that was released by AT&T before AT&T lost their lawsuit trying to recapture source code they gave away so that people would improve the AT&T code for free. The AT&T lawsuit ended up in the branches of BSD and System V(5).

    SCO tried very hard to play the patent troll game and lost. Most of us in the world are happy about it, and better off because of it. Go do your homework, or shill back at the Junior High schools where people may believe the trolls.

    --

    -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

  10. Saved game corruption by Waccoon · · Score: 1

    Gee, maybe they should let people make backups and have real save slots... just like in the old days. It's not like saved game corruption is a problem old as dirt, right?

    I'll skip griping about always-online games. These days there's plenty of indie titles available so I don't have to subject myself to the crippled AAA garbage.

  11. Re:no effect by johannesg · · Score: 1

    I imagine the average PC owner would think "XBox exclusive" if they heard that title, and not pay further attention to it. I certainly had no idea there was a PC version. Then again, if it isn't on Steam or Gog, as far as a great many PC gamers are concerned, it doesn't exist.

  12. And this isn't a.. by poofmeisterp · · Score: 1

    ..sales tactic? These sorts of things have been happening more and more; there is less loss due to pissed off consumers and more interest the "news" feeds the nosy hackers. Lost 100 for lost saves; gain 2000 for hacking interest AND flashy interest generated by viewers of the "news".

    Hell, I would do it, and I'm not a sales-minded person. They're way ahead of me in using tactics for sales, so I state my point.

  13. Re: At least they weren't stealing from SCO by Sloppy · · Score: 1

    Are we going to have a lovely old fashioned flame war about whether the Amiga or the Atari are the best 16 bit micro next?

    My Amiga had a 68060. Quit calling it 16-bit as though it's anything like your sorry Atari.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  14. MS is the worst with patches by HalAtWork · · Score: 1

    I got an Xbone as a gift and 3 games, Master Chief collection, Halo 5, and Forza 3. MCC has me downloading a 62GB patch, Halo 5 has a 50GB patch, and Forza 3 had a 2GB patch. The other day I went back to try and play Forza 3 but it's trying to download yet another 2GB patch and refuses to launch until I update it which means I couldn't play when I wanted, with kids I don't get much choice of when I can play. So far, (like Windows machines) I spend more time waiting for patches to download and install than I do acually using the system. I don't understand why patches are so huge on Xbox, can't they just use diffs or something?

    1. Re:MS is the worst with patches by Kaenneth · · Score: 1

      Download time aside; fuck data caps.

  15. Re:At least they weren't stealing from SCO by omnichad · · Score: 1

    What's there to distinguish? The lawsuit was regarding 'Linux' and not any userspace tools that may have been running on top of it.