NV Crashing at Start-up Window

[ZeAntiNoob]

Whenever I get the start-up window open where it has the options Play, Options, Data Files, etc. and I hit Play, the game just crashes and I get the little error saying "New Vegas has stopped working" (no s***) and then it just closes. The thing is though, when I launch NV with FOMM it works just fine. Unless I have NVSE downloaded, in which case I get the same menu and the same result when I hit play. Anyone have a solution?

[GrindedStone]

FOMM (NVMM) puts the Main.esm, DLC.esm, or Mods.esm.esp into order based off the modified/created on dates (down to the second) The FNV launcher and under certian conditions the FO3 launcher will both ignore the modified/created on dates, an just look at the actual names of the .esm an .esp in A-Z in these cases any mod or DLC which the first two letters of the name are before Fa as far as A-Z then those mods now try to load before the main.esm itself. FalloutNV.esm Fallout3.esm the first two letters are Fa So ClassicPack.esm for example is Cl which is before FA, so the game tries to load ClassicPack.esm before the FalloutNV.esm to which classic pack requires, thus causing instant crash. Alphabetical crash if you will.

 

I would speculate that because the issue is somewhat present in both games that it would be from the lack of support these default game launchers provide in the actual ordering of .esm an .esp However you could ask some of TES players who have been around this type of set up longer than the fallout 3 players. Most of TES players have a intimate understanding of certian aspects which most of us Fallout players ignore by default because we are kind of spoiled rotten from the more polished later releases.

 

Fallout NV will have this problem randomly after the game has been played for a little while, or after something was changed as far as what is being loaded. Fallout 3 though only has this particuar issue under certian conditions, for example if FOMM is installed incorrectly, or perhaps a registry error, who knows. So logically it suggests that perhaps the issue is caused in Fallout NV from the same thing, maybe, perhaps, blah, eh? Crying.... :( Personally I have seen FNV edit load up a load order an it's in the correct order based off the modified/created dates. But later on the game launcher puts this load order together alphabeticaly which crashes instantly.

 

The only fix that I found was to change the names of all the DLC an mods so that the first two letters start after Fa going toward Zz. This was done by adding Fb_ Fc_ Fd_ and so on to each of the DLC or mods. However some mods require to load other mods as masters which is based of the name of those mods in the header data, so before you change the name of everything you would have to first go into FNV edit an change these required masters names. Also any mod which is using voice sounds Data/Sounds/Voice the folders are named based on the .esm or .esp which controls them a sort of automatic loading an selection for voice type audio files in the dialog creation process. So those folders would have to be renamed as well. So this fix really isn't any good at all, and is only useful if you have spent a few days working on a load order an have no other choice.