Has anyone tried just starting fresh? It's irritating when you have to start over on some games but maybe the fix doesn't work until then? (saves aren't always salvaged by patches, sometimes you have to start clean). Yeah, clearly they don't want it effecting their game's first sales discount on Steam.
Bit premature? Maybe listen to what the players HERE say before announcing it's fixed. Originally posted by Jonofwrath:Lol at "fixed". Some of us like to relax in GOD mode and don't care for multiplayer or co-op. Would have been nice for y'all to have labeled the file as something like "Developer Save" or something instead of "Corrupted" and no warning anywhere. The previous behavior can be returned entirely by providing `+devMode_enable 1` on the command line. This means that save games that were previously marked as Dev Mode saves, now display as “corrupted” to prevent the user from accidentally re-enabling Dev Mode by accessing them. To help users avoid accidental Dev Mode activation, all Dev Mode functionality has been disabled by default. We wanted to provide some clarity on this.Īs part of Update 1, the behavior of “Dev Mode” was changed because some user behavior or save game problems would be mistaken as developing/tinkering and feedback from users revealed that once Dev Mode was enabled, it wasn’t always clear how to disable it, and save games were being effected that the user never intended to use tinker with in Dev Mode. Originally posted by jleaveyBethesda:Hey all. This will avoid Steam replacing the unwanted save file with a backup. When doing so, you should temporarily turn off your Cloud saves in Steam, too. We recommend moving your existing save game file to a different folder and then restarting the game. If you make use of the command console, you will need to delete any Campaign save file that has made progress with a console command active and then relaunch the game in order to continue playing without Developer Mode. This includes any new Campaign save games created, or any old Campaign save games progressed, even if no console commands were active during the play of that save. Save games are held under each individual Windows profile, and sharing the profile between multiple players can cause issues.Activating a console command will put the entire game into Developer Mode, causing any further save progress to be flagged as developer-only. We recommend using individual Windows profiles instead. Having multiple users on the same Windows profile to play DOOM, even if it is with different Steam IDs, can cause this issue. If you find your game in a Developer Mode state, there are two possible reasons and respective fixes: Thank you for your patience while we worked to resolve the issue. Update 6/30: This has been fixed with Update 1.
0 kommentar(er)
