Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 "What we've got here is a failure to communicate"

About Leyodemus

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Guys/gals/..., I know it's not a FIX whatsoever, but the following approach seems to work for me: Load your savegame (--> if all your current savegames fail to load, I'm afraid this approach won't well help either... and I'm truly sorry for your loss, I know it sucks donkey d*ck) Continue playing NEVER use the autosave functionality Save your game, but ALWAYS choose "Save as" and give it a "unique" name without spaces --> I like to use stuff that is currently going on in-game as part of the file name next to my club's name, so "LiverpoolCupGameNext" or "LiverpoolT
  2. OK @Ben Allingham... So in other words: every 200MB-file that I see in my Google Takeout-zip is just 1 part of a particular savegame. Well, I checked and that seems to be the case indeed, since there are 2 separate files with the exact same name for each of my savegames. That is probably also the reason why my Steam-version of FM can't load these files "separately". The splitting/merging-code was probably only included in the Stadia-version of FM? If there is a way to load these splitted savegames in the Steam-version, please let me know. From a software developer standpoint I totally get
  3. In my case these saves are still OK, but if I load them and continue playing, FM refuses to save the game again... To be honest, I think that all the 200MB-savegames are in fact corrupted in some shape or form, because it is near-to-impossible that ANY savegame is exactly 200MB in size. I'm not sure where the corruption is situated, since these savegames can still be loaded at this point, but I think it's fair to say that the 200MB-limit is the root of all evil and has to be removed :-) If Google says: nope, 200MB per savegame is all you get, that's their choice of course, but then w
  4. Yep, and I'll raise you: it's not even "around the 200MB mark", ALL of those savegames are EXACTLY 200.000.000 bytes in size, which is a virtually impossible coincidence :-) So that has to be the limit that was set on Stadia for FM-savegames. If this was a conscious decision, FM should have never been released there because that's just ridiculous. @Ben Allingham, please tell me I'm wrong...
  5. SO...I did an export of my FM20-savegames via Google Takeout, and I think I have spotted the exact issue. Every savegame that is NOT corrupt, has the same file size of exactly 200MB: As a software developer, I find it extremely hard to believe that ANY file is EXACTLY 200 MB in size, let alone multiple files, which makes the problem super-obvious to me: the max size for a FM-savegame on Stadia is 200 MB. Please fix this problem (can't be that hard to be honest, and I can't image this being such a surprise, since EVERY FM-savegame goes well over 200MB in time) AND tell us
  6. And it would also be nice to know if our current saves will be "fixed", or that the update will only make sure that new savegames don't have the same issue again. Fingers crossed either way...
  7. Same issue here, and I'm only in April of 2022, but with a LOT of leagues loaded... I started noticing this problem earlier on when I saved games. But when I tried to save it again, it would always work so I didn't pay that much attention to it. BUT, at this point, 95% of attempts to save the game fail and if a game does get saved, it probably won't load back up afterwards. Also, I notice when the game fails to save and I continue to play, stuff just "isn't right", database-wise. What I mean by that is: if I for example click on the score of a recently played game, to see the game/match
  • Create New...