pretzdothack

Since I saw this post I disabled my ad blocker on this site. However, since then, every time I come here I now have to report multiple ads. Either autoplay video, or ads that cause massive site lag until I report/disable them. This is most disappointing. I hope Nexus is able to find a stable, trustworthy ad provider soon.

I didn't have to do any editing of ini's with FOMM, or downloading archiveinvalidated either. I just downloaded my mods and installed them using the Package Manager, and life is good. Seeing as I installed the FOMM's after I already did archiveinvalidated I don't know for sure if FOMM will work without modifying the .ini files.

I assume since you're on here you've used some mods before, lol. Also, I don't know how long "a while" is so this might not work but If you've used texture mods or modified your .ini file in any way then it won't load until you follow the link in my signature and re-arrange some things. Then it should work! Good luck~

Is this the chauncey crash?

Odd. I can't really think of anything helpful. Was this something that just happened, or has this happened since you first started?

How "Not matching"? As in you have a caucasian character with african-american face/skin tones? Or just a different shade of the same race?

What kind of crashes? Like, you have to do a complete reboot? Or does it give you an error or say (Not Responding) in the corner? Also, what are your computer specs?

Not quite sure how you got it in this path. Hazmatradman420, if you don't see it there look in C:\Program Files\Steam\SteamApps\common\fallout new vegas Most likely a torrented copy.

@MythWisper- Intriguing. Thanks for the information! @Fumofumo- I've only had two real artifactings while playing. To which my computer replied with a BSOD, lol. Otherwise there hasn't been any color changes or pilxelation on the normal crashes I'm speaking of. Next time it happens I'll try to get a screen shot if it'll let me. Usually I just check GPU-z before the game starts and sometimes in the middle of it. Mostly though it's after the crash and as soon as it boots up I'll check it. I've even run in windowed mode a few times and positioned GPU-z where I could see the temperature. I'll look into MSI Afterburner and check that out. As for the after-market cooling devices I already have an extra fan that plugs into the PCI port underneath it and cools the card down even more. I've never seen the temperature read higher than maybe 70c.

I noticed a small issue that cropped up because I had manually set up ArchiveInvalidationInvalidated!.bsa prior to installing FOMM. When I checked the FOMM ArchiveInvalidation tool it overwrites the Fallout_default.ini in the *:\Program Files\Steam\SteamApps\common\fallout new vegas folder & the Fallout.ini in the C:\Documents and Settings\MeTheAdmin\My Documents\My Games\FalloutNV folder making a reference to Fallout - AI!.bsa ~ which FOMM inserts into the D:\Program Files\Steam\SteamApps\common\fallout new vegas\Data folder (or it renames the old ArchiveInvalidationInvalidated!.bsa to AI!.bsa) In either case it does NOT remove any manually inserted reference to the old (or deleted) ArchiveInvalidationInvalidated!.bsa file in any of the above mentioned ini files. I am presuming that this is what's been causing my game to CDT every so often... well, OK it is just one more step in trying to resolve my intermittent game crashing. If this cures the issue completely I'll post something about it. Meanwhile I think the above information regarding the changes that FOMM makes to the various ini files is worth being aware of since it does make the Fallout_default.ini changes. Strange. I don't get any intermittent CTD with manual archiveinvalidation or FOMM invalidation. I don't think you would get any from that, but I suppose its possible.

No problem. Hope you got it solved.

I didn't have to use any console commands. I just restarted an earlier save. It seems that what glitches it is if you talk to conteras after you get into the communication area for the first time and tell him that someones breaking in. Instead just get in there, look around and check the computer. Then wait outside till about 12:30 then follow him in.

Yeah. So I've been dealing with this for a while, and I can't seem to figure it out. Occasionally (at least once when playing) the game will crash. It seems to happen when I'm loading or exiting a menu of some sort. I'm noticing that the menu it happens most often with is a loot menu of some sort. The crash is odd. Upon exiting/loading the menu the screen gets these little dots that are green (I'm using the green HUD. Color is probably not related) and they cover the screen relatively evenly spaced. The sound begins to loop rapidly and after a few seconds my monitor resets to black. Then the sound fixes itself for a minute, and then loops again. This just repeats. I'm forced to do a hard reset of my system. No ctrl+alt+del, no alt+tab. Nothing. Occasionally I can get a mouse icon of some sort to appear, but it doesn't move. Then it just fades when the monitor flashes again. I had asked once before but nothing really came out of it. Someone suggested I change video drivers; So I did. I had been using Catalyst 10.7. Then went to 10.4 as per the suggestion. It happened less it seems, but still happened. Steam then suggested the "latest" ATI drivers. 10.9. So I once again did a clean wipe of the drivers and installed that. Still crashing. It does seem to be a driver failure, or at least appear to be one, but when I've had them in the past windows let me know that it was trying to recover. Someone said it could be my video card "dying". Yet i've only had it for just a year this month. I used GPUZ to check the temperature and all other stats and everything appears to be normal. I don't believe this is mod related because it happened in FO3 as well. (I only started FO3 for my pc for modding two days before NV came out so I didn't experiment with the problem in that aspect). I run the game on High settings, and when running the game in low-mid settings still crashed. I would really like a solution or some advice or at least somewhere to begin looking. Thanks for any and all info!

My [ARCHIVE] section reads as such: And I have no problems with them anymore. My .ini's aren't read-only either. Make sure you're doing the Fallout_default.ini file! If you do the other ones and not this one you will notice NOTHING changing. I used the manual archive invalidated file. I think the new FOMM and even the old FOMM can do it for you. @crisisninja- What exactly is still happening? Explain the crashing. Is it a crash to desktop with an error or a "Not Responding" text? Or do you just click "Launch" or "Play" and nothing happens? As for the people who this little guide is still helping: You're welcome and I'm glad this has helped you! Enjoy playing!

It's generally, from what I've noticed, a script glitch. Related to a quest normally I believe. I don't think a mod would affect it. I had the same problem with the NCR Monorail quest because it was glitched. After restarting the quest right it fixed itself.

Crashing how? As in it gives you an error and says "not responding" on the task bar? Or do you click "Play" and nothing happens? If it doesn't start and you're using mods it could be because of the modified .ini files. Follow my guide to see if that helps. http://www.thenexusforums.com/index.php?/topic/261613-patch-broke-your-texturesmods/ If it's actually CTD'ing and giving you actual errors, as opposed to not running, try getting the .dll fixes and finding some drivers that work good. Nvidia cards are having problems right now.

Okay, just so you know , if you do the verify integrity of your files it will remove a modified .ini file. Such as the ones people have to modify to use texture mods and some other miscellaneous mods. The crashing you were experiencing could be any number of things. Such as the "81 mods" not clashing well together with them since the new patch.

Seems most people have gotten this taken care off and are off to more complicated bugs/crashes! Joy joy. xD

Removing the patch would involve a complete uninstall of the game, then reinstall with updates turned off. You then run the risk of not having any of the save-game glitches fixed though. And your glitches sound hilarious and I've yet to hear of these. xD

It's odd that it would just start messing up if it's been fine this whole time. Then again it could of just installed the updates late. Anyways, verifying the integrity will just remove your modified .ini files. So, the reason it keeps finding one and fixing it is because you keep editing it. Try running a vanilla version and see what happens. Try re-arranging the load order in your ini files according to my guide and see what happens. http://www.thenexusforums.com/index.php?/topic/261613-patch-broke-your-texturesmods/ By crashing do you mean actually CTD or just you hit play and nothing happens? If this all fails do a complete re-install with no mods. You said you reinstalled but you didn't say if it was vanilla or not.

Try using a mod manager to select them. http://newvegasnexus.com/downloads/file.php?id=36901

Oh, you mean the data files in the launcher? You cant select them?

I suppose the easiest way to start looking at it would be to disable all mods and see if it works then. Then turn on each one until you find the culprit. And from what I'm to understand corrupt save files won't load at all. So I don't think it's that.

Choosable traits? Am I missing something? I assume you mean the bonus packs, and that you had one of each?

That's honestly a lot more information than we need, lol. Okay, anyways, I assume you had the game working before the patches, right? Are you using mods and a mod manager? If so try disabling them all and running a vanilla version of the game to see what happens.