I wanted to try out the public test branch for the upcoming patch to get my hands on the refreshed UI. (Good job there btw!)
Therefore I did a backup of my save states after syncing them to my hard drive from the steam cloud. Then I installed the beta patch and could play. After testing out the new stuff and not encountering any particular errors I wanted to downgrad back to the stable branch.
Now my game keeps crashing whenever I’m entering the character selection. I can see the background of the character screen just fine. Also my characters are listed completely in the bottom right panel. However the model of the selected character isn’t shown and after 1 or 2 seconds the game crashes. I attached the crash report; without the dump file though, since I don’t know whether it contains personal information which I may don’t want to share publicly here. If it is necessary to solve the issue, I’ll gladly provide it (of course).
I uninstalled and reinstalled Grim Dawn, but it doesn’t fix anything. I also tried to remove the whole Grim Dawn directory in …\Documents\My Games without any success. Even with the directory removed it somehow resynced my saves from the Steam Cloud although I turned cloud save states off via Steam (because I knew they could be problematic since I migrated my save states to the beta branch before).
If there is any additional information I can provide (i.e. the dump file) please tell me. I really want to get my game up and running again - and also use my old saves for that.
If your saves are in the new save format, the game will crash.
If steam now holds your save files in the new format, clearly cloud save wasn’t disabled properly.
Unless you have an extra local backup and disable steam cloud in steam and ingame, wipe your save folders and restore the clean backup, you’ll have to stay on the playtest branch until it turns to stable.
if you have cloud on ingame the crashes are being caused by game using your steam save folder with the 1.3 saves, those need to be replaced, including stash (hope you backed up the whole save folder not just individual chars)
if you were playing with client online, and it synced after entering 1.3, it might overwrite your backups with 1.3 saves from the cloud, reject the sync if it gives you the option
if you turn cloud off ingame you can plop the backup saves in the my games documents folder
if you then still wish to utilize cloud for save backups do the reverse steps in part 2 of Pow’s post medea linked, since game wont read saves in steam save folder unless they got imported sometimes (in your case shouldnt’ really matter as much as you’re just replacing/overwriting existing named files with the same)
Thank you. That worked. I only disabled cloud savings through steam so it synced the updated saves and tried to use them instead of the back up I made and put back in place on my drive.
I only disabled it via steam; not ingame. It works now. However when I turn it on again ingame it starts to crash again. I guess I won’t be able to sync my working backup in the steam cloud. Guess will have to wait till the patch its to activate it again.
turning cloud on/off ingame options “physically” switches save location on your computer, thus technically using different saves
cloud on in GD ingame options = steam save folder C:\Program Files (x86)\Steam\userdata\"your numbers"\219990\remote *start path might differ if you have custom steam install like d drive etc
cloud off in GD ingame options = the docs/mygames/grim dawn path
Steam syncs only from the steam folder/remote, so if those are the 1.3 saves either direct or steam downloaded after playing/trying to paste in backups, is then why you’re crashing turning cloud back on. You’d need to replace those saves with the backups to not crashw with cloud on (and if then turnign steam sync on reject the down sync, otherwise replaces your saves with 1.3 again)
Alternatively you just stay with local saves/cloud off in game having saves in doc folder for now
That worked. Moved my save directory there after deleting the old faulty save directory in the userdata path. Thank you so much. Thank god I made a full copy from the whole saves, settings, etc. directory in before the whole branch switching etc.
Now I can wait patiently for the patch to drop officially … on stable.
you have no idea been a couple unfortunate ones that only backed up individual char files, resulting in them losing their entire stash from being v1.3 “corrupted”
Thank god I made a full copy from the whole saves, settings, etc. directory in before the whole branch switching etc.
been a couple unfortunate ones that only backed up individual char files, resulting in them losing their entire stash from being v1.3 “corrupted” 