I have both the Classic Fallout Weapons and Weapons of the New Millenia installed. Upon playing with both mods, I found that there were alike guns in both weapon packs. For example, both WNW and CFW have an M14, but the M14 in WNW is superior (no surprise).My goal was to remove the duplicate weapons from CFW so there wouldn't be two different items of the same gun. So I opened up the.esm and.esp for CFW in FNVEdit and began to remove the undesired weapons by accessing the weapons tab, right clicking the mentioned undesired weapons, and removing them. I got through all of the weapons and launched the game. It went through the usual logo screens as expected, but the menu with the start, load and save buttons never loaded.
Jul 10, 2008 This Weapon Pack Is The Most High Detailed Of Them All It Rivals GRIMS Weapons And Others. I Recommend This To Everyone And Especially People Who Love Guns =). Does cooling a substance (e.g. A freezer pack) below its freezing point, take its temperature lower? Or is the freezing temperature the lowest it can go? For example by landing in a swimming pool full of shredded foam rubber, the force would be 5000 Newtons, about 1100 pounds, which you would probably survive.
It didn't crash because the music was still playing, but since the menu never showed up I couldn't really do anything so it's no better than a crash.So I go back to the.esm and.esp. I check through the other tabs for leveled lists and such and find that there are red and underlined entries in these tabs. So I edit those to remove the red, underlined parts (which I assumed to be an error that would cause the mentioned error above). So, with hope of actually getting the game to start, I launched the game and the same error persisted. Why can't the game just load already?!Because I want to play Fallout, I have deleted those changes and just reinstalled the CFW mod.
Now I have to deal with duplicate weapons again.P.S. I have the proper.esm files. I checked in Wyre Flash to find what the problem could possibly be, and CFW showed up as Orange but not red.
It mentioned an issue with my load order. CFW.esm should be just after FalloutNV.esm but before any of the DLC.
This isn't the issue because I actually did that, and the error did not persist despite the different load order prior to my 'noob' editing to the CFW esm and esp. I have other plugins for CFW. That's quite helpful, thank you. It's rare to see such a descriptive reply.I am on New Vegas and not Fallout 3. The tool provided is said to only work with F3.I first converted the.esm to.esp via FOMM, then opened that file in GECK and made the appropriate changes. When I finished up I converted the.esp back to.esm via FOMM again, added it to my mods, loaded the.esm but had two warnings.1. WARNING: This plugin has the file extension.esm, but its file header marks it as an esp!2.
The masters for the newly created.esm file are FalloutNV.esm and CFWNV.esp - the.esp file I edited back in GECK.I attempted to run F:NV despite the missing master, just to see what would really happen. It crashed, no surprise there. So I added the master and it didn't crash, but still had that 'not-loading' error I originally had.
It seems I'm back to square one.Also, I thought it would be worth mentioning. The.esp file previously mentioned had the opposite of the error given by FOMM for the.esm file:WARNING: This plugin has the file extension.esp, but its file header marks it as an esm!I find this all really odd.EDIT:I found an easy way out! By disabling the additional plugins of which CFW.esm is the master of, the error no longer persists! Maybe the reason the error was there was because appropriate changes were not made to those plugins? Bear in mind that the only thing I edited in GECK was the.esm (converted to.esp of course). So, I assume that making the same changes I did WHILE the other two plugins are also loaded will fix this issue? Otherwise I can just.
Not use them. But that would not be ideal.Edited by nkorea, 16 April 2015 - 12:40 AM. Re-read my post, I updated it /edited it.Fomm is the correct tool to use to reconvert in 1 swoop into an esm, the header of the file should also get altered so as to not cause the error as listed here.Fomm 't-snip' utility is used to save the file 'make esm' into a new file. But, it is not the end yet, you still need to convert that result into a real Plugin.
FNVPlugin works with Fallout New Vegas ESM/ESP files. You can display the records and merge two plugins to form a new plugin. You can also create an override plugin containing the merged lists from one or more plugins.That applies the needed coding you will require and Validate the file to 1.34.if you do not do this, any file created by the other program will not be valid.Steam Invalidates erroneous code.you add all programs you intend to use through steam and IT will validate all functions, this includes all 3rd and forth party applications.That includes Fomm.use the steam OS,lock out windows from your software, that's how.1. WARNING: This plugin has the file extension.esm, but its file header marks it as an esp!Make a list of the exact file names your using, I use Mod organizer. How I use it depends on the game used.regardless, you still need to heed what I said.Isolate all data per mod, load only data concerning that mods needs,edit only 1 file per session, the data directory needs to be Virgin as in zero assets from any mods at all, other wise the engine will pick up instructions from files it parses in that data folder on load of any software.If it's in there, it's gonna get loaded.I will continue to watch this thread and see your progress.kitty.