I think your missing 2 zeros after that 3.
I honestly feel bad for Bethesda and Obsidian over the save bug. It is clearly a problem with the interaction between New Vegas and Steam, something they did not spend those thousands of hours testing before hand like the actual game was. There are Some bugs yes, but only the Save bug and a few others appear to be universal across all platforms and most will be fixed in a number of days. What irks me is the Huge hit they are taking over the Save Game bug when its not even the fault of the game or its developers. Next time I suspect they will do more testing on the Delivery mechanism (whatever that is next time) to prevent this kind of tragic situation. I for one having played and modded Fallout3 for over 2,000 hours can Definitely see that there are far fewer bugs in this puppy than I expected to see, I've had only 1 game crash so far and that I find significant for the platform.
Not much consolation to those getting thrashed by the bugs, but I do know that between Bethesda and Obsidian there were Hundreds of people testing this game.
Actually, no the save game bug doesn't have to do with steam. People have tried disabling Steam Cloud, running it in offline mode and not getting achievements, etc. no luck. You have to go into fallout's files and fix it.
Even if it was steam, there are plenty of huge bugs that are not steam. For example, the framerate dropped to abysmal levels in big fights because it always dropped when NPCs came on screen. So with lots of NPCs you can have a top of the line PC, be running it in low graphics, and have a framerate of like 3 fps (if you're lucky) because the game didn't know how to use direct X. People (read: the community) made a fix that links FO:NV to direct X like it's supposed to be.
Those are the ones I've encountered personally. Here are some I've heard about but not personally encountered yet (I've played the game about five hours so far):
"Your companion may not initiate a conversation with her elder, forcing you to reload a saved game or ignore the quest. A mutant for hire will respond to your request to continue the quest with the same dialogue that he delivers if you tell him you need more time. Scripting errors abound in which things that are supposed to happen never do, while in many other cases, inexplicable events occur that will boggle your mind. Locals will freak out and run around as if someone is brandishing a weapon and then stop and walk back to their assigned positions. A vendor might attack you unprovoked, even if you have a golden reputation in that town and are dressed in neutral clothing. Sometimes, it's unclear if you're unaware of a contributing factor or if the game is simply going bonkers. Not to mention frequent crashes on both consoles and corrupted game saves, which might cause you to lose progress. In addition, the longer you play, the slower the frame rate gets (on the Xbox 360), or the more noticeable the screen tearing and frequent pauses become (on the PlayStation 3)"
These bugs are courtesy of http://www.gamespot.com/ps3/rpg/falloutnewvegas/review.html?tag=topslot%3Bimg%3B1&page=2.
I think Obsidian made a great game, but the QA was nowhere to be found. Which seems to becoming a pattern for them if Alpha Protocol is any indication. I really hope they'll make up for it and start with the patching. (Which, they have, to an extent. I believe they fixed the framerate issue yesterday). I hope they'll continue fixing it with patches so in the not so distant future we'll have a game that's acceptably buggy, instead of what it is now.