I would like to see some kind on acknowledgment from Obsidian/Bethesda about these issues. So far I only hear crickets.

I CAN guarantee that regular saves work. I'm a regular save kind of guy - I do that a lot along with quick saves. My quick saves keep on disappearing; the first time it did that I was horrified. However, all my regular save games have remained untouched through multiple crashes/losses. I'm just glad I made sure to use regular saves, even though it's still a pain in the ass losing progress.

Same issue here, quick and autosaves are NOT working right at all.

Thank you for the feedback. :thumbsup:

I have opened a ticket on Steam asking if they are aware and already working on the issue, and also asked them to estimate when the fix would be apllied.

Hope they answer soon. I'll let you guys know as soon as I have the answer.

So far, manual saves are working for me. To speed up the process of saving, hit the ~ key, and then type save "savename1" and then hit enter. To save again, hit the the ~ again and then the up arrow key. This will bring up the previously typed command. Rename it (or not), hit enter, and there is another save.

That will come in handy, I'll do that.

Thanks again.

Confirmed, auto/quick saves are lost when you exit the game and return. Regular saves work fine. Quality assurance, missing the obvious problems since 1981...

Thank god regular saves work, that's still going to be a bit of a pain though as if the game crashed anywhere near as much as FO3 did, autosaves and being able to spam the F5 button were near-essential.

Cinder, you mentioned that running it in offline mode should fix the problem; has anyone been able to confirm this?

Obsidian/Beth/Steam/whomever better be aware of this and fix it, I'm going to be even more pissed than I already am because of download issues if I finally get the game and can't even autosave or quicksave...

Auto/Quicksaves do have a history of being broken with past Bethesda games so make hard MANUAL saves only and lots of them to avoid potential file corruption...this happened too in the past.

So Obsidian is protecting their rep of great games with super buggy releases. Nice.

Try launching from the desktop shortcut and let all the intro screens play through then click Continue to succesfully reload your last Quicksave. Seems to work for me while other methods result in a bugged out load screen.

Do not press ESC... there is no ESC... Do not click the mouse... the mouse is fragile.

http://forums.steampowered.com/forums/showthread.php?t=1522475

Heads up, this thread has more details, two workarounds (one already discussed here), and an acknowledgment of the issue by a Valve employee.

Probably related to the save game issues is with the configuration. I made changes to the controls when I first launched the game then I made changes later. The later changes are lost to the first changes after quitting and restarting the game. I think it is coping back an old copy of the falloutprefs.ini from the steam userdata directory. As in it isn't updating the old copy with the new copy when you quit.

Manually copying the falloutprefs.ini from the my games folder after quiting FNV to the steam userdata folder will fix the config reseting. But you will probably have to do it every time you make changes.

I have noticed weirdness with the save files, I turned off the Autosave features, as my usual practice, and the weirdness reduced.

Has anyone who has this issue tried turning off the Autosave features? Also, try deleting the Autosave file manually. Search for it in the Steam Directory. That may stop the game from shuffling these around.

If this works, avoid using Autosaves until the issue is fixed by Steam.

Let me know if this works.

It's not the game, it's an issue with the Steam Cloud. See http://forums.steampowered.com/forums/showthread.php?p=17831496#post17831496 on the Steam forums.

Same thing happens to me, but ONLY with quicksaves and auto saves. manual saves still work. POS steam cloud.

Hi,

*EDIT* I honestly don't think this has anything to do with steam cloud.


I had the same problem, and it was consistent quicksave nor autosave worked. So i decided to do a few experiments:

FIX (worked for me and a few others in irc)


1. Your saves most likely still exist:

Your fallout save files are located in:

Open up:
[Win7-64]
C:\Users\\Documents\My Games\FalloutNV\Saves

[Other]
Open up "My Documents" folder, then open up My Games\FalloutNV\Saves

You now will see a list of all your save files

Look for any files ending in .bak(you might need to enable show file extension to show file extensions e.g if you see something like: autosave and another one called autosave.fos, the autosave.fos has a file extension of .bak) you can check this by right clicking and choosing properties.

Rename the one not ending in .bak into something like backup_save.fos, then remove the .bak file extension

E.g. I had:
autosave.fos
autosave.fos.bak


i renamed autosave.fos to autosave_old.fos, then i renamed autosave.fos.bak to autosave.fos, Loaded the game and loaded the autosave and boom all my progress was back.

2. WAHHHH I don't see anything, and i can't save or anything.

- Open up fallout.ini, it will be in your FalloutNV folder in my games.
- Search for this: SLocalSavePath
? Where does it point?, if it looks like:

SLocalSavePath=Saves\

If you see that, make sure you actually have a saves folder in the falloutnv folder.

3. Preventing it from happening again

right click fallout.ini and choose properties, untick read-only
Open your fallout.ini file in notepad or whatever and change:

iSaveGameBackupCount=1 to iSaveGameBackupCount=0

This will prevent the game from making any "backup" saves (i have 0 idea what this is even for)

Save your changes and go back and reenable read-only

4. NOTHING WORKS STILL OHGOD

Open fallout 3
make a characther or whatever, get to a point where you can save your game:

Hit ~ and type:

save "aname"

Hit Enter.

Where aname can be anything you want, i don't suggest spaces or anything, just something simple like "puppy1" i don't know what problems with long file names.

Open the console again, and type load "thenameyougaveit", if nothing happens then there is something seriously wrong.


Why?

Also how many of you made a new character, at some point today and after making the new char these issues started happening? Furthermore how many of you named this new character the same name as your old one?

!!!EASY FIX!!!!

If you do a save through the console (its the same as saving via menu) and for whatever reason my save game folder is not writeable/accessable or the save file has bad parameters there doesn't appear to be any sort of error notification.

Also when you make a second character, The old autosave file isn't the one that gets "backed" instead its the new one you just made that gets backed up. As to why you can quickload/etc while you are in the game as your characther it is probably because internally the autosave is not loaded by the filename instead it is loaded by the unique file descriptor object. However when you reload fallout it sees autosave.fos and consideres that the newest version.

somehow my quicksaves and autosaves are working again, the only thing different I did was turn off PhysX to see if the game run smoother next to NPCs, but I doubt it have something to do with it...
or the problem has been Fixed and I didn't know? xD

It does have to do with the Steam Cloud. I can't post a screen shot here, but saves seem to be getting shuffled back and forth from Steam, even if you have the Steam Cloud feature disabled. Problem is, when you use Autosaves, this shuffling around messes things up as the files have the same names. When people are choosing to continue, the game is picking the latest file, even if it is the one that was just downloaded from Steam a few minutes ago, that was uploaded to Steam as a back up several local saves ago. With them all being named Autosave, it is impossible to keep track of.

Only when I went to manually only saving the game did I see what was happening. I ended up with two Save 7 at completly different points in the game, same with most of the other numbers. Each one of the saves that have the same sequence number are from different points in the game as I was rotating through the slots.

Hopefully this issue will be addressed soon as Steam is aware of it and are investigating. In the meantime, turn off the autosave features, and use new manual save slots until this is fixed. Keep your saves in order by looking at the elapsed play time in the screenshot of the save as you choose it from Load. This way if you decide to go back, you are actually going back to the save you want.

Until this is fixed, I will just create a new slot each time I save. I can always delete them later.

Official Steam rep on the forums said that Steam Cloud for FONV has been disabled until they can find a fix; can anyone confirm or deny if this has helped?

i would like to know this aswell.

if steamcloud is off then the game should no longer overwrite, or even be able to overwrite, the autosave and quicksaves.
so they should now work as a result.

It hasn't helped.

I made this bat file, however. Place in your fallout new vegas folder and please edit it to fit your file structure where I have "EDIT ME IN BRACKETS."

cd ..cd ..cd ..cd userdatacd [EDITME]cd 22380cd remotedel *.fosdel *.inicd ..cd ..cd ..cd ..cd steamappscd commoncd fallout new vegasfalloutnv.exe

This will do all the work for you, and work each time. I'll repost it at the steam forums. edit: I'm not registered for the forum yet. Somebody else pass along my solution, please.

edit: oh, and if you don't know how to make .bat files. Open notepad, paste the text in from above (after correctly filling in the steam\userdata\[paste this where it says [EDITME]]), save as "whateveryouwant.bat" (not .txt!) and place it in your fallout new vegas main directory, where falloutnv.exe is located. Just double click it to automatically clean out the remote saves and run the game.

edit3: This should, also, fix any issues with archive invalidation invalidated provided that you make your .ini changes after cleaning out the remote folder at least once.

I don't even have the option to enable or disable the Steam Cloud on FNV. I've played a few hours and quit several times and it has not deleted or overwritten my autosave or quicksave files.

So has this been fixed on the steam side yet?