Now WTF still CTD

[ClayboTGW]

I too was havening a lot of CTDs but between fixing a few steam setttings, and configuring my ini. file to work best with my machine and using a codec resetting mod I'm getting higher framerates and a lot less CTDs I have a lot of mods running as well. all you can do is a lot of trail and error to get the game to run smooth on your system. If you change your ini file be sure to always back up the defualt one that the game created upon install.

 

Try Looking here for ini tweaks thou it says FO3 its the same game engine and ini file. http://www.tweakguides.com/Fallout3_8.html

 

also this mod is very good at reducing crashes http://www.newvegasnexus.com/downloads/file.php?id=35868

 

 

Bethseda games like Oblivion. FO3 and FONV have always been prone to CTDs after extended gameplay.

[secksegai]

The crashes to desktop have become utterly intolerable with this game. It is becoming more frequent. The game is fundamentally unplayable. I will be going back to FO3 which has no problems in this regard. Its not the video cards its the game/Steam interface. I believe there was a minor update recently, since then I've had problems. Especially with the AI of Powdergangers. Can't go anywhere near them without the game crashing. This has happened since the last patch. The game was mostly stable before that patch and I was running a large number of mods with no problems. I've cut than number to a quarter with no luck at all. I've run it with almost no mods and it still crashes every 10 minutes. Pathetic programming and using Steam as a client is a very bad idea. Its crap. This game is a total waste of time and money.

 

The fact that you're running a large number of mods should be your primary suspect. I'm guessing you've done little to know modding of your own as if you did, you'd be aware of how patches themselves can cause issues to arise by effectively becoming incompatible with certain mods (at least until said mods are updated).

 

While I will complain about the implementation of steam, it's the game itself that really deserves the bad rap. Steam just adds additional complications to an already problematic game (no real manual patching).

 

Considering I'm able to go hours without crashing now on less than a decent system (on the latest patch) - its more than likely certain mods you've been using have resulted in your severe instability. Half the mods I use I write myself, and the other half generally involve textures and meshes, something I don't plan on ever learning and will generally have a minor impact on performance and stability (when installed correctly).

 

I honestly wouldn't be surprised if your archive list is the problem, as you can't just have archive invalidated at the beginning of the list if that applies to you. The fact that powdergangers are causing a crash screams mod incompatibility, but if you'd rather just blame the game.....

[HeavyHandz]

Yo, you said at the top you were running your game clean with no mods. Now you say you running with almost no mods? Don't just give up on the game, make a clean install and don't use any mods that edit worldspace. I still don't know which screwball mod I installed that decided to rip a chunk of the area near the Boomer base completely out causing violent CTDs if I so much as sent a teammate that way. I did a clean install and I realize the mod took out a whole bridge, some exposed sewer and a lot of other stuff which I had not seen with those mods installed. Also make sure, if you don't already, that using FNVedit to make your own overriding patches is required if you want to reduce CTD and game breaking changes. And I agree with you, I hate Steam and anything that even looks Steam.

[GreatestDay]

No I guess I don't know how much time you spend here helping out, because I only started playing the game after the megapatch and just started looking for fixes n other stuff. So around here I don't know whos who. Yes the thought always counts, but if the poster has a track record of giving incorrect advice (generally speaking, not referring to you at all), then more often than not the thought gets lost. Know what I mean?

 

Yes I do have FFDShow, I disabled it, made no difference, took the settings down to Medium, no difference. Latest drivers, check. No mods, check. And my other games run just fine, smooth as glass. And no offense but you're starting to sound like a crash mazochist lol. I'd say 3 crashes in 30 mins IS pretty bad. Just started playing a game I really enjoy, only to have my e-rection put under a e-cold shower every 10 mins. Yeah it's pretty darn bad in my book.

 

And f*ck Blizzard, until Diablo 3 comes out that is. After spending a year playing FPS games I can never go back to the isometric birds-eye view again, feels so hollow. D3 is an exception because it looks extremely hot. But SC2, D2 and other s*** look like complete crap now. And if you say WoW, I'll slap the taste out of your mouth!

 

Have you done any ini editing to enable multi-core threading?

 

Do you have FFDSHOW installed?

 

I don't like it when people just spit out alleged fixes that they themselves haven't tested. Thanks for trying and everything but don't post like 10 different random "fixes" if you don't know whether they do anything. Honestly this is the most ridiculous game I've ever played. 30 minutes of gameplay and 3 random crashes, it's so frustrating. If Bethesda can't fix it, what makes you think those other alleged fixes will?

 

It's not people's settings or rigs that cause the problem, it's the game files themselves because stupida$ Bethesda won't bother testing their product before releasing it. It's absolutely SHOCKING that they would deem this kind of state as "release-ready".

 

Personally I have disabled FFDShow for FNV, everything up to date, windowed mode and turning down game settings, list goes on and on, nothing works. The only thing that HAS worked is the mouse acceleration off-trick, I'm very glad for that.

 

You obviously don't realize how much time I spend offering help in this forum. I run the game with a less than adequate setup and get more stable performance on an aging (ancient in computer terms) machine compared to some of these folks with nice rigs. I don't waste my time offering advice on something I haven't tested myself - unless I'm just speculating and then I mention that it just be a guess.

 

FFDshow will cause instability, something I know firsthand after experiencing it firsthand - in the least it will bog you down probably wasting cycles. You also assume too much in general - just because the Official Company can't get something working properly, doesn't mean the fan base won't as some of said fans have extensive technical knowledge. Replacing the d3d9.dll isn't new, as I've had to do it before for certain games when they had issues with the latest drivers - but usually its a matter of new drivers no longer compatible with an older game, as opposed to a brand new game not running optimal code for the operating system as I believe has been the issue for FONV. I'm not all that familiar with dynamic link libraries or programming, but it doesn't mean I can't utilize someone's fix, especially when the description of said problem and fix provided makes sense to me.

 

I've crashed far more than 3 times in half an hour, though usually that's because something crashed my original game and I'm trying to recreate the situation so I know what variable is causing it (so I can avoid it or fix it in the Geck).

 

If 3 crashes in half an hour has you up in arms, what are you doing playing a Bethesda game? Stick to Blizzard =P

Edited December 29, 2010 by GreatestDay

[Deleted1744345User]

The game engine royally sucks, and that is probably the source of many of your crashes. I'm grateful that I experience fewer crashes than you, but Bethesda definitely should have fixed it up much more before releasing it. That company is starting to slide into the trend like other companies of churning out quick games for quick bucks. Call of Duty is no exception. Hopefully the game engine is scrapped in the next Fallout and moddability still retained. Let's keep our fingers crossed.

[hangman_86]

I can play the game fine, just ctds on those particular missions.. So I think its something in the game itself that conflicts when missions are done in a particular ordder.. Video card is not the issue for two reasons.. the computer i listed is brand new My other computer is an amd nvidia build and it crashes on the exact same spots. Another issue that i have noticed on both systems was with the pipboy menu cursor lagging when moving to select items n weapons, though i worked around that by moving cursor to left of selection screen then sweeping it right when at correct height.. Also running game with 0 mods so they are not the issue either. I got past those crashes by starting a new game and doing missions in a different order than i had previously, also found that i have significantly less ctds when i dont have a companion running around with me.. Still will crash on a few other missions like it had previously on gi blues, so i just skip them now.. thanks for the help

[secksegai]

Honestly I don't normally put up with games this buggy, FO3 & FONV are a special case since I played FO1 and FO2 and developed a fondness for the universe. The worst I'm normally able to put up with is BioWare level bugginess, and I don't recall ever having one of their games CTD short of unstable memory as their bugs are more along the lines of the minor ones you'd find in these FO3/FONV games. While it may seem odd to actually try to crash the game, my reasoning for it is most people would say Q&A did a lousy job and the customers have inadvertently become beta testers it would seem. Might as well know what breaks the game so as to know to avoid it or find a solution to fix it.

 

It's probably not video related, but being brand new doesn't guarantee an issue free experience. Software and drivers don't necessarily get along all the time, and there are times when using older drivers will actually be more stable and/or have higher performance. For any game that would have the issue, you can luckily just override the direct 3d dll instead of loading old drivers just to run one game.

 

Honestly, as far as troubleshooting crashes, it may not even be worth the time, considering the engine itself is the main problem. Certain commands and actions will crash the engine, and they can occur without any modding whatsoever. I've never had a problem with companions themselves crashing my system, but when you consider the scripting they all have, and the fact that not all of them are even bug free in the vanilla game, it's not hard to believe that the system would feel more stable without them.

 

But, if you have to skip content, there's probably something more to it. While I admit I tend to do quests in a particular order, a lot of that is just avoiding known bugs, like Raul and Ranger Andy. I'd strongly suggest takin a look at the Fallout Wiki to see if any of your problem situations are listed in the quests notes as you may find you're simply experiencing an actual bug and there may be workarounds listed.