But then again the Questions come, why isn't everyone facing these bugs why is some Xbox and ps3 players playing the game without any problems and other xbox and ps3 players facing problems unless there are different version of the games or something.. Why is it that a certain players gets bugs after bugs and i don't have any problems at all.. Was the copy of the game he got different from mine in any way ?

I still believe most of the problems faced by PC New vegas owners can be fixed..

Well hopefully they'll figure out the answers to the questions (considering it's their job) and then all of these questions will stop.

The games are all the same. The Xbox360s are basically the same closed system. The problem is the complexity of the game.

I don't think there is a thing that goes like: Do X and the game crashes.

It's rather like: Do X, Y, Q & G in this order to make the game crash. Or other million possible combinations etc. The game is huge, and there are endless possible combinations that scripting or other things could cause an error in system.

The bottom line here is: The game on XBox 360 was not tested enough.

Just to chime in:

Bought the game on Xbox. Been having bugs that force me to restart every time I play. Haven't been whining, but did post on it once when somebody mentioned the media reaction to the bugginess in another thread.

It's cool that there are so many people having a bug-free experience. But no, the outcry is not just from whiners. There are some serious problems affecting a substantial portion of players, from what I can tell by reading around various sources.

No, I'm on the 360 and have experienced a high number of hangs. I would normally expect my 360 to hang once or twice a year! It hardly ever happens. But with Vegas it started out with once or twice every three hours or so, then suddenly it started doing it half a dozen times an hour. That's when I patched it.

Other than that I've had the Pipboy not fill the entire screen when I opened it, the Pipboy be extremely bright so I couldn't see the screen, and creatures getting stuck in the ground and getting all stretched out and distorted but that one is very minor and happend in F3 also.

So it definitely is the most unstable game I've ever played on the 360, and I don't want to complain about it, I love the game. But I must be honest.

There is no question that this is one of the buggiest releases on this gen of consoles

should i slap you in the face now or later? what a horrible thread... you really think people would be on the form complaining about bugs and not playing the game... god if this is the future of our youth i am scared by their incompetence...

The single most egregious bug, though not experienced by all users, has also been reported on the Xbox360 and not just the PC. I'm referring to corrupted save games.

i barely see any... the ones i can say right now are if you upgrade the weathered 10mm pistol a huge exclamation point goes over your char. and if you look at rivers you see a huge gorge looking thing. i think the radio is bugged too, not too sure.

lol...ever try this one thing called reading? yea lets you know pretty much everything thats happening.

If you haven't experienced bugs... you're lucky, other people are not liars.

It's a simple fast and hard fast of modern game development that bugs will exist. In my playthrough #1 I had a number of bugs some serious (auto-save not saving, FONV still crashes randomly some times) some less serious (graphics bugs holes in wold geometry) and some annoying and gameplay-changing but not actually critical (ED-E My Love quest being hopelessly bugged and not able to be completed).

It happens, some people get over it and enjoy the rest of the game, some come to the forums to [censored] until they're blue in the face.

Sadly the corrupt save file bug seriously hampers this option- as replaying the same segment over and losing hours of gameplay puts a not-insignificant damper on your ability to enjoy things. The lack of a meaningful official response to this issue is also a little disheartening. The sole thing they have said on it has been "Reload an earlier save."

They fixed this for PC within 48 hours. I learned early on in my FONV experience to save early and often using the menu and it's a habit that's stuck with me (playthrough #2 and I've used 150/1000 saves!) but for PC now it is fixed and it only ever affected you if you closed the game or it crashed. I get crashes too so it was double frustrating but once they disabled steam could support it seems it works. I can't really blame a company for having unexpected issues with third-party software (Steam Client) and I consider the Steam pre-order bonuses worth two days of learning to dilligently save.

I can't think of a logical reason for anyone to just makeup bugs. It seems game reviewers are in on this elaborate hoax as well as they are now making up bugs too. To think that its all make believe is just asinine. Since the patch finally came out for PS3, my game is playable so I'm pretty content with it. However, every single time I've have played the game, it has frozen up atleast once. Literally every single time. Tonight it froze as soon as I started. It loaded, then I exited a building and freeze. That was a few hours ago, I am typing this while waiting on my system to come back on as it just froze on me again.

No. It is not fixed. It is still happening. This issue is seperate from the steam cloud issue .

I've used about 120 save slots so far. The problem is that you will not know that your saves have been corrupted until you later try to load them AND that any saves you create during a session where the state data has become corrupted will be corrupted as well. Say, for example, that your game state becomes corrupted during the "Come Fly with Me" quest but the program does not actually crash. You have no way of knowing that your saves are corrupt at this point as whatever exactly is causing the saves to be unloadable does not necessarily cause a crash until you attempt to load one. Since it's your day off you continue playing for another... 5 hours and create manual saves every 10 minutes. Only then do you go back to reload a previous save for whatever reason- this is when you discover that ALL of the saves from when that malformed data was introduced into the game state onward are useless.

Part of the problem is this- that the glitch that causes saves to be corrupt and the presentation of an error due to this glitch can be separated by hours of game-play. This has nothing to do with, as you condescendingly put it, "learning to dilligently (sp) save."

See the following posts as examples of this:

http://www.gamesas.com/index.php?/topic/1131288-52-hrs-of-playtime-and-cant-load-any-saved-game/
http://www.gamesas.com/index.php?/topic/1131288-52-hrs-of-playtime-and-cant-load-any-saved-game/page__view__findpost__p__16583383
http://www.gamesas.com/index.php?/topic/1132242-cant-load-saved-files-ouch/
http://www.gamesas.com/index.php?/topic/1132234-wow-lost-everything/page__gopid__16583721&#entry16583721

I haven't had that issue, thank Beth, but I'm suddenly hesitant to start my new guns-based legion playthrough until it's resolved. Is there any way to know when a save might be corrupt? is this issue affecting PC?

The two areas noted so far by multiple people as having the potential to cause this problem (we know which ones they are because these people saved often enough to narrow things down) are Vault 3 and REPCON test facility. Since you will only discover these problems when trying to load a save- I would suggest periodically saving and immediately loading when you've reached these places and after you've left them- basically test your saves when you're around there.

If you combine this with just generally saving manually in seperate saves and doing so often you should not lose much gameplay even if you do encounter this issue. If you do, and the problem repeats when you re-attempt whatever area you found them in- try doing things a slightly differently or in a slightly different order. If that solves it- please post it. That will help bethesda narrow down the exact cause. It will also allow PC users to simply use the GECK to fix the problem themselves if it is a simple scripting problem or bad item ID.

I understand being hesitant to replay the game until the errors are fixed. Because of the nature of the issue and the fact that the corruption of state data and the resulting crash to desktop are not automatically concurrent means that we can't really be sure there aren't other quests and areas in the game that cause this glitch. So even keeping those two areas in mind, you might think yourself safe and discover that after a marathon session of playing, none of your saves over the last 5 hours work.

Okay, let's all just be straight with eachother:

1) Fallout 3 and Fallout: New Vegas (even Oblivion) are huge games that have a LOT of data stored into one game. It's a HUGE game, right? So much information going on at once, it's bound to freeze every once in awhile.
2) I'm sure many of the complaints come from M$ users, mainly because A) the Xbox's GPU already had a hard time handling such a huge games as Fallout and 2) PCs get bugs and viruses and even more technical issues a LOT more than consoles do. You can't exactly REFORMAT an Xbox, at least not in the same way as a PC.
3) The PS3 usually requires games to be installed on the hard-drive, don't they? Wouldn't that alleviate the freezing/locking up?


This is just speculation, and I play on Xbox 360.

My habit is to save after every objective and new world location I find. Find a vault, save, accomplish an objective? save. Beath a tough encounter? save. Have to stop playing to go pee? Save. My saving habits have become almost compulsive since I had an auto-crash when entering strip north gate that cost me an hour of playtime. I haven;'t seen corruption yet, but be sure, if I do I'll post it to the wiki, since I realized the sad, sad state of their FONV articles I've been a compulsive contributor.

I've got bugs, and I bought the game off the shelf. I'm also a beta tester with a major games distributor, contributor on five other gaming forums, and have played games since the days they were on a board with hexagons, or used paper and pencil. I think you owe me, and others like me an apology.

I think you are a short sighted, rude, and ignorant commentator.

Will the moderators please ban this person thanks, we don't need this sort of person on the forums.

Despite your cocky demeanor, I do agree that it is completely pointless and somewhat rude of the OP to sit there and complain...about others complaining. Doesn't that sort of create a sense of hypocrisy?

BUT, I don't think you should be demanding bans weighed on the fact that he's just expressing his opinion, albeit moot and somewhat foolish.

Dude, OP, if you haven't had any problems with your game, then please, post something useful or more insightful. Feel lucky that you haven't had any problems. And for all those posts and complaints about issues that you HAVE read about? Well, out of the millions of people playing Fallout, these are the minority when it comes to glitches. =T

There are definately bugs. I personally had the corrupted save files twice. I was lucky the first time this happened since I did a manual save about 3 hours before the corruption happened where I couldn't load from the saves (it was the first manual save I did, all I used before that were quick saves and auto saves).

It happened again a few days later but I was manually saving my game constantly at that point so I only lose an hour or so.

There were other bugs as well but nothing as game breaking as the save corruption bug.

Uh, I think that the people who claim to have no bugs whatsoever are full of it! (two cents)

@ OP are you [censored] kidding me? why would anyone make up bug?

Fallout New Vegas is my Favorite game but is BUGGY as hell.

I'm not demanding a ban weighed on the grounds you suggest...I'm doing so because he is villifiying contributors, and has started an intentionally inflamatory thread, both of which are legitimate grounds for a ban, under the forum rules.