Fallout New Vegas crashes regularly for me on two different machines. I am far from the only one experiencing this problem and all of my other games run flawlessly including Fallout 3 and Oblivion.

This is totally unacceptable. These problems should have been addressed before the game was even released. These bugs render the game unplayable. Why wasn't this addressed before release? When is a patch going to be released?

Join the "CLUB", I have expressed my complaints on this very forum even posting my dxdiag and to this moment I have had no answers to my complaints. I have asked that STEAM and Bethesda simply provide us with a patch to "FIX" all of the problems being experienced by most of us. But as of this moment it has not come to fruition. I hope you will have better luck than I have thus far.

From the Please Red before Posting sticky thread: Please note that these forums are not used for official technical support. Rather, we plan to use it to provide updated information and allow dialog between gamers to solve common problems, such as the most common problem of video or sound card drivers (or a lack of updated ones).

For technical and customer support, please call 410-568-3685, 9:00 am to 5:00 pm EST Monday through Friday, excluding holidays, visit support.gamesas.com or email support@gamesas.com.

This section is for posts and topics related to issues running the game.

The contact info would be great if they would be available 24/7 and then actually respond. If you work then the hours are useless, especially if you are PST.

I have been with Bethesda since Daggerfall as a closed beta. This is awful and not ever my experience with them.

Weird how many people experience problems with NV. I run it on a machine well below minimum spec and it runs just fine. Well I sure am happy I don't got win7 or vista as it seems to be incompatible with almost everything ever done before today in the field of computer science. Sometimes I wonder if the trouble don't come from there? Anyone?

naw I've had no problems with a proper win7 machine with 99% of apps includijng games and I support several 100 from DBs to autocad.

This game has some issues. Its just really amazing they are so random. So many people not having problems, but the ones who are doing so on machiens that run everything else fine for the most part.

Yeah it's kind of strange. The fixes tend to be somewhat random too. I mean yes if there are bad codecs or other identifiable problems are generally things that have consistent solutions, but the CTDs can be very random. Some people with nearly identicle setups have to roll-back drivers to a slightly older than current version while others with that slightly-older version only have their crashes fixed under the newest ones. I've seen threads where people with the same nvidia graphics card, same version of windows, same motherboard, same bios, and same CPU and one had to use 260.99 or else the game was unplayable and another had to roll back to the version just prior to that. And the d3d9.dll fix... still seems to be the only solution for some and the bane of others independent of what hardware they have. I'm sure it's not actually random but whatever underlying consistencies there are to why the solution for one person is often as much the source of troubles for the next person seems to defy logic at times.

I'm starting to worry that Gamebryo has developed some form intelligence and that on some systems it just seems to also be a little psychotic.

Is there a point to this thread besides ranting? If you have issues then you need to post information regarding the error(s) and your system specifications and other relevant data. Whining about the game isn't helping anyone. Bethesda Software developers rarely use this forum to bugfix.

Well... I have the opposite experience. For me Bethesda games have always crashed frequently, but NV has only once so far: which I put down to using the latest version of the engine?

Yes this game does have more bugs with quest logic, but thats only because it actually HAS quest logic and things to go wrong unlike fallout 3.

I'ts Gamebryo 2.3 isn't it? I think that was the latest version available when they finalized the engine version during early development- the most recent version is only 2.6 and that's what a game currently in development might be using. I'm not sure what engine version Fallout 3 used though.

Nope, it's Gamebryo 2.0 same as FO3 and Oblivion. They haven't updated the core Gamebryo 3D engine since Oblivion - note the 2006 copyright in the title card for NV. 2.3 (or maybe it was 2.2) changed the physics component from Havok to Physx and I think later versions use the open source bullet. Gamebryo/Emergent is owned by creditors now who are trying to sell it off, it's pretty much dead as they've let most of their employees go and closed their main engineering headquarters. And before somebody says "well the explains everything if they haven't updated it" no it only explains why it looks a little dated, is only DX9, hasn't changed at all from FO3, etc. There is a darn good reason they didn't utilize newer versions for sure

Ah ok so it's both relatively current and almost the same as the oblivion engine at the same time because it hasn't seen major updates from Emergent since they laid off most of the staff responsible for updating it.

I had forgotten that even though Emergent selling off the engine rights was a relatively recent development that they had laid off most of their Gamebryo development staff years ago. I should have remembered though since it was in the local news and that was how one of my friends lost his internship.

The next Fallout might use IDs Rage Engine... This would be very cool!

Yes it would. Id's Rage engine can be used for open world games unlike many other game engines/middlewares out there (like Unreal 3, Source, etc. although that doesn't stop devs from trying to use them like Unreal 3 was used for a MMORPG once I think). Could even be one of the many reasons for Zenimax to be interested in the first place (although Id was sick of Activisions crapping all over them throughout the years). Either way, we've definitely seen the last of Gamebryo being used as the core 3D engine for Bethesda games. Morrowind ran off of a Gamebryo predecessor called NetImmerse which was DX8 based and lacked a physics engine. It was probably due to the developer's familiarity with the engine that they decided to go with Gamebryo for Oblivion (which was quite a popular engine/middleware at the time), and also because they could easily port it across platforms due to it being a middleware. Then after Oblivion wrapped up they started FO3 but by then they'd already invested so much time/money that even if they hated the engine they pretty much might as well have used it. Morrowind CTDs even now on Windows 7, I'm sure the devs are just as tired of it as everybody else but FO3 and FO:NV are still wonderful games if you can look past all the issues.

Agreed, Fallout 3 is one of the best games I've played in the past years :fallout: And it ran smooth as silk on my computer. So frustrating that F:NV is like a ticking timebomb, never sure when it'll crash... Because I know it's an awesome game but right now I really can't "look past all the issues".