FOMM/FOMOD help please

[kevkiev]

Whenever I try to install a FOMOD using FOMM's Package Manager (ie via the "Add FOMod" button) I get this error message:

 

http://i253.photobucket.com/albums/hh70/diggermats/fomod.jpg

 

FOMM will then immediately close but, when I run it again, the FOMod is sitting nicely inside the package manager. I'm able to activate it and go on my merry way.

 

I never really worried about it before because the FOMods always seem to install/ work in the end. But I just reinstalled NV and am in the process of loading up a bunch of mods and figured I'd get to the bottom of this in case it's any cause for concern.

 

This what the associated crashdump.txt looks like:

 

http://i253.photobucket.com/albums/hh70/diggermats/FOMODsomethingbad.jpg

 

Can someone tell me what's going on? Is it okay just to continue ignoring it when it happens? (I read a FOMM/FOMOD for dummies tutorial on the web but, alas, I still couldn't figure it out.)

 

I'm wondering if I should maybe have all my mods in a particular directory or something?

 

Thanks

[Execon]

I am Like you mate, this is causing me a lot of crashes cause the mods are not installing properly, or conflicts with others, manual installations doesnt work either cause FOMM doesnt recognize it...

 

If anyone has a clue... please let us know...

[kevkiev]

That sucks man. 3picdc described a similar problem here. I'm feelin' pretty lucky because, although my FOMM crashes at the "add FOMOD" stage, when I restart it the FOMOD is actually sitting in the package manager, and I'm able to activate it, like nothin' happened. Can't figure it out, but it indeed works in the end for me.

 

Hope y'all figure out how to get it going. Thanks to our ever-helpful fellow nexusite (?) Sunnie, I was finally able to figure out how to turn regular mods into FOMOD files and install via FOMM's package manager. Makes later uninstall nice and easy for mods with lots of texture/mesh/ sound files etc. I saved the steps she laid out so hopefully once you solve your FOMM snag it'll help you too:

 

Creating a FOMod:

1. Create an empty folder, name doesn't matter.

2. Drag all of the mod files and folders (all folders/esp/esm/bsa) from the mods archive and drop them into the empty folder you just created.

3. Open FOMM, click on "Package manager" button.

4. In the Package Manager UI, click on the little arrow on the top most button on the right and select "Create FOMod'.

5. Click the button you just selected and the Create a FOMod ui will open.

6. Enter the file name you want to create in the box under "FOMod File Name (without extension):"

7. Add your files to the Source Files section by clicking the Add Files and Add Folders buttons, browsing to the folder you made and selecting the mods files/folders and clicking OK.

8. Once you have all the mods folders and files in the Source Files section, drag each file and folder over to the FOMod Files section on the right.

9. Click on the "FOMod Info" button on the left and add any info that identifies the mod you are packaging. (Note, leave the Required FOMM Version as 0.0.0.0 to avoid possible tool error messages that will stop you from progressing).

10. Click on the "Save Locations" button on the left and check the option for "Create FOMod".

11. Click OK. The creator will most likely pop up a warning message that some info is missing, which is ok. Click OK and the package will be built and stored in the FOMod folder set when FOMM was first installed.

12. Once the package is built the Create UI will close and you will see the mod now listed in the Mod List of the Package Manager. click on the FOMod you just made and select the "Activate" button on the right and the package manager will do all the actual file/folder installations. To uninstall the mod, simply select the FOMod and select the "Deactivate" button.

13. Repeat the above process for each mod you want to be packaged.

14. Now close the Package Manager and make sure any esp/esm files are checked and are in a proper load order.

[NorthWolf]

Exact same behavior for me. It's not damaging but it is very annoying. :confused:

[PowderdToastMan]

From the looks of it, youve just re-installed the game?

 

I had the same problem last time i installed because i forgot to start up the game at least once before trying to use fomm. have u done that?

[kevkiev]

From the looks of it, youve just re-installed the game?

 

I had the same problem last time i installed because i forgot to start up the game at least once before trying to use fomm. have u done that?

 

 

Interesting. T'was so long ago I can't recall. Thx, I'll try that on my next reinstall. (And it seems there's always a "next reinstall" somewhere out in the future, sigh...)

[mauve96]

PowderdToastMan

 

Yup, you were right. New start on a clean game and ONLY THEN using fomm did help, thanks.

Edited July 29, 2012 by imanayev tim

[Gribbleshnibit8]

If you're adding a bunch of them, you can also just drop them in the directory where FOMM saves them to. Saves a lot of time in having FOMM load each one.

 

For easier finding and management of my own mods, I save them all (for every game) in a centralized MODS folder near the root of my drive. You can change where FOMM looks for mods in the Settings (and also find out where they're saving if you don't know).

[Fortevn]

Can't seem to find the reason. I have the same problem and the crash starts at login popup. If I click cancel I'll go the package management and crash after each add.

Every mod sit there when I launch FOMM again (also check on mod folder, they're there with proper size) so I didn't miss anything. However, the adding process is insanely fast, about 10-100 times faster than NMM so I wonder if everything is ok ingame...