New Vegas not working after new patch....... : Fallout: New Vegas

» Tue Dec 06, 2011 8:40 pm

I don't honestly understand why this happens everytime a new DLC is released.

So, I DL the new patch. Go to fire up the game. Game crashes on start up. Ok, I think to myself, probably an NVSE issue. I go to the NVSE website, DL the latest patch, or what I think is the latest patch (V2Beta9). I install it. I open FOMM. Click "Launch NVSE". CRASH!

I open the package manager, it still shows Beta7 as being installed but I do not see a Beta9. I look in the NV folder and everything looks the same as the original NVSE that was released when NV was still new.

So, what gives?

Honestly, I don't know if its because I cut my head open today at work or the fact that I'm going through a Chapter 13 so I can keep my home but this really pisses me off. All I want to do is chase around some Legion scum and put a bullet in their heads but I can't. So, any help would be great.

Also, would it kill anyone over at the NVSE camp to change the file names to reflect the newest version? This way when you are looking at them in your folder they don't look like they are old files. Seriously, its kind of annoying going through the files looking for one that says beta9 but they all say, "nvse1_1.dll". Why is it so hard to change it to, "nvse1_9.dll" so that when you are looking through your folders trying to make sure its installed properly you go, "hrmm...this one says 1 and this one says 9.....theres my conflict."

» Tue Dec 06, 2011 4:19 pm

So, I DL the new patch. Go to fire up the game. Game crashes on start up. Ok, I think to myself, probably an NVSE issue.

If it's crashing before you've updated NVSE but after you've updated the runtime, you have a load order or mod conflict problem. NVSE will stop loading if it detects a newer version of the runtime. One easy way to check this is to remove the NVSE DLLs and launcher EXE, then try running the game.

Also, would it kill anyone over at the NVSE camp to change the file names to reflect the newest version? This way when you are looking at them in your folder they don't look like they are old files. Seriously, its kind of annoying going through the files looking for one that says beta9 but they all say, "nvse1_1.dll". Why is it so hard to change it to, "nvse1_9.dll" so that when you are looking through your folders trying to make sure its installed properly you go, "hrmm...this one says 1 and this one says 9.....theres my conflict."

The original intent was to make the name match the version number of the runtime it was targeting, but since patch release time has always been extremely hectic I haven't thought of it since the initial update. If you want to find out what version it is, right-click the DLL, go to Properties, "file version" will show the version you have installed.