Fallout: New Vegas senior producer Jason Bergman stopped by the official forums to announce the release of a second patch over Steam to address save game issues that players were encountering. He also goes on to outline console patching plans and to point out that faction-related issues aren't always bugs:
As you may have seen, we released a patch over Steam for PC users last night. While we didn't release a full changelist, the patch contains quest and scripting fixes. It's not a minor hotfix, it contains over 200 fixes in all. We are in the final stages of testing this update on both 360 and PS3 and we hope to have them out to users very soon. I just logged into the Xbox 360 version (only because I had it days before the PC version and didn't want to start over...) and it looks like there's a patch available for it, too. One would assume it incorporates many of the same things the PC patches do.
We are also pleased to say that we have just released a second fix for PC users to address the autosave and quicksave issues that some people were encountering. That particular issue was never seen prior to release and it was extremely difficult to reproduce reliably, even after the game had launched. In order to fix this problem we have had to disable Steam Cloud functionality. It has been turned off, and we won't turn it back on until we're absolutely sure it will not cause any more problems. Please restart your Steam client to make sure you get the update.
We are also working directly with hardware manufacturers to improve performance for certain video cards. This is a driver issue, and not directly related to the game.
On consoles, we are aware that a small group of 360 users are seeing a DLC warning which is preventing you from loading save games. We are absolutely looking into this bug now, along with other reports of save game corruption. It is our highest priority right now that we find out what is causing it. In the meantime, we recommend you save often, and revert to an older save if this occurs.
As far as general memory and instability, you should see an improvement once the patch goes live, but we are continuing to work on this based on user feedback.
We want everyone to know that we are monitoring the forums and cataloging every single issue we see reported. We're reading forum posts, we're checking Twitter, and we're reading Facebook comments. We aren't able to reply to most threads, but we're listening. If we see an issue, we have people here trying to reproduce it so we can fix it.
While there are definitely legitimate issues out there, we wanted to take a moment to address a couple of things that have been reported as (bugs.)
The now infamous Doc Mitchell video, while very funny (and horrifying) was not a bug. Unfortunately during our launch day, there was a brief window where Steam was pushing out corrupt or incorrect files. In the event that a user wound up with a corrupt meshes.bsa file, they would get that error. It was easily (and instantly) corrected by simply re-validating your files with Steam. At most, a handful of people ever saw that issue, and even then, only for a moment before fixing it.
We have seen forum posts where people are claiming they are not getting all of their perks. Again, this is not a bug. In Fallout: New Vegas, you receive perks every other level, not every level as you do in Fallout 3.
And finally, a quick tip: Be aware of your faction status before assuming the game is broken. Factions will react very strongly to you based on your current armor. If you're wearing Powder Ganger or Caesar's Legion armor, you will be shot on sight by the NCR (and vice versa). Also note that there are groups of renegade Powder Gangers (known simply as (Escaped Convicts)) who will shoot you regardless of your faction status.
Please post any issues you are having to our forums and we'll do our best to fix them as quickly as possible.
The Fallout: New Vegas Teams at Obsidian and Bethesda