bridgitte Posted March 1, 2022 Share Posted March 1, 2022 Since this latest update I am experiencing continual crashes during game and even sometimes when I log out correctly or save a game, when I try to load in on that save and sometimes several I find that the saves are corrupted and won't load but just crash during loading - once or twice a message popped up to say that the save files were corrupt and twice it was the last 5 saves of a game - this has been happening ever since this last update - and after spending so long in Fallout 4 to go and get kicked out repeatedly and have saves corrupted after spending hours building up a settlement of doing quests that I now have to redo - please fix or give us back the older version of Vortex Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted March 1, 2022 Share Posted March 1, 2022 those issues you describe are nothing to do with vortex. it doesn't touch save games at all.i'd also ignore the seriously bad advice on downloading back level versions of vortex unless you really want a bad day. Link to comment Share on other sites More sharing options...
Tannin42 Posted March 2, 2022 Share Posted March 2, 2022 Correlation does not imply Causation, just because your problems started occurring around the time of the Vortex update does not mean the update caused the issue. All Vortex does is copy (or more precisely: link) mods into your game directory. Vortex itself does not affect your game runtime at all, it can't cause corrupted saves.If something corrupted your save games, it's one of the mods - either because the mod is bugged or because it's been installed incorrectly (e.g. incompatible combination with other mods).In the latter case Vortex would be involved insofar as it installed the mod but even then Vortex installs the mods you asked it to. Link to comment Share on other sites More sharing options...
rmm200 Posted March 2, 2022 Share Posted March 2, 2022 "Bad day" is a serious understatement.Positive note: It enabled me to turn up a new obscure bug in 1.5.5, which will now be fixed. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.