Fallout: New Vegas Patch Coming "As Quickly As Possible"
- Thread starter Andy Chalk
- Start date
Personally I've run into fewer bugs in KotOR 2 than the original, and think the sequel is worlds better in pretty much every department except for The Huge Plot-Twist.Polaris19 said:
But then The Huge Plot-Twist only really works once.
Now, if you'll excuse me, I'm going back to Korriban with my ship full of Padawans.
I love that glitch. Hilarious.
I haven't had anything like that, but it did crash on me when I was moving inventory from a temporary companion and suddenly extra guns started appearing in both our inventories, then blamo! Frozen Xbox.
But otherwise it's been pretty smooth. I expected crashes though. Fallout 3 did the same thing to me on the PS3. I learned to save every 15 and turn on all the extra save functions. For me, it's worth it. But I would say if this kind of thing bothers you, wait a bit. Fallout 3 was so much smoother after a year when I played it again.
I haven't had anything like that, but it did crash on me when I was moving inventory from a temporary companion and suddenly extra guns started appearing in both our inventories, then blamo! Frozen Xbox.
But otherwise it's been pretty smooth. I expected crashes though. Fallout 3 did the same thing to me on the PS3. I learned to save every 15 and turn on all the extra save functions. For me, it's worth it. But I would say if this kind of thing bothers you, wait a bit. Fallout 3 was so much smoother after a year when I played it again.
This is why I'm waiting to by it around Christmas. And on the PC.
By then the devs will have patched the major ones(hopefully), the community will have patched everything else, and there will be a nice selection of mods available.
Plus eventually I'm sure someone is going to make Dr. House into House.
By then the devs will have patched the major ones(hopefully), the community will have patched everything else, and there will be a nice selection of mods available.
Plus eventually I'm sure someone is going to make Dr. House into House.
Unfortunately, there is an age old reason why games are often buggy on release, and it often goes like this:
- Developer gives publisher a timetable, which may slip early on, but publisher monitors progress and often requires proof of progress updates.
- at least 6 months before expected release (if not more), publisher sends out notification so stores can order copies (which gives publisher an idea of how many copies to print) - this is almost always contrived to be 3-4 months before Christmas, no matter where team progress is.
- Developer realizes they can't meet the date with the number of bugs and asks for an extension, which publisher refuses or in some cases, the publisher gives the title to another dev team to polish and fires the existing development team (which is my experience, thank you EA).
- Developer squashes as many critical bugs as possible, but the game still ships on the date.
- Developer scrambles to put together a zero day patch, or at least one soon after release (there is generally about a month between when the developer hands it off and the publisher publishes it), because they care about customer experience and publisher only cares about their investors.
I'm guessing developers like Blizzard and Arena Net are usually in late beta when they send their notice to stores and spends the last few months doing nothing but polishing, but I do know those two will refuse to publish if the game isn't done. The team I was contracting for was in mid-alpha when ship was set and late beta when we were fired (a month before it was due in publisher's hands).
It isn't much different in the corporate world, but instead of a publisher forcing the date, huge customers do. I've worked in both worlds.
- Developer gives publisher a timetable, which may slip early on, but publisher monitors progress and often requires proof of progress updates.
- at least 6 months before expected release (if not more), publisher sends out notification so stores can order copies (which gives publisher an idea of how many copies to print) - this is almost always contrived to be 3-4 months before Christmas, no matter where team progress is.
- Developer realizes they can't meet the date with the number of bugs and asks for an extension, which publisher refuses or in some cases, the publisher gives the title to another dev team to polish and fires the existing development team (which is my experience, thank you EA).
- Developer squashes as many critical bugs as possible, but the game still ships on the date.
- Developer scrambles to put together a zero day patch, or at least one soon after release (there is generally about a month between when the developer hands it off and the publisher publishes it), because they care about customer experience and publisher only cares about their investors.
I'm guessing developers like Blizzard and Arena Net are usually in late beta when they send their notice to stores and spends the last few months doing nothing but polishing, but I do know those two will refuse to publish if the game isn't done. The team I was contracting for was in mid-alpha when ship was set and late beta when we were fired (a month before it was due in publisher's hands).
It isn't much different in the corporate world, but instead of a publisher forcing the date, huge customers do. I've worked in both worlds.
in fallout 3 I was talking to lucky harith (who was swimming at the time)
and his head started spinning, vertically, even!
and his head started spinning, vertically, even!
Hmm, interesting. My game has run perfectly for the first 4 hours. And I never had any bug problems with Oblivion. Fallout 3 on the other hand had this annoying habit where I would phase through the ground and fall for eternity.
And to those who said KOTOR 2 was buggy, it wasn't buggy-it just was never finished in the first place. XD
And to those who said KOTOR 2 was buggy, it wasn't buggy-it just was never finished in the first place. XD
Exactly! I mean, it's not like these are new bugs either.Woodsey said:
They were present in Fallout 3 [http://www.youtube.com/watch?v=lw8nppzDS4Q&feature=player_embedded#!] and it appears that Bethesda and Obsidian were just ignoring them.
This just gives me the impression that they were thinking: "Why fix what people will pay for?"
PS3 version is broken... Meh, don't expect anything: Fallout 3 GOTY for PS3 is broken and isn't fixed, but it's still being sold (!!!). I think that's the only console game this gen which is actually broken and can't be properly completed. And now New Vegas has same damn bugs and more.
I managed to activate that bug on Fallout 3. In an unorthodox way.
I killed people and resurrected them (using the console command "resurrect 1") until there were nothing left but goo. Then I talked to them. This usually caused them to suddenly get a body and a "ghost head" like the one said in the video. They would also sink slowly into the floor until you talked to them again. During the conversation they would sometimes do a headspin or whatever it's called.
I killed people and resurrected them (using the console command "resurrect 1") until there were nothing left but goo. Then I talked to them. This usually caused them to suddenly get a body and a "ghost head" like the one said in the video. They would also sink slowly into the floor until you talked to them again. During the conversation they would sometimes do a headspin or whatever it's called.
