FOMM Issue - "Error Loading... Invalid Archive"

[bsmetal]

Today, while using FOMM i've been receiving the same message while opening the Package Manager:

 

"Error loading 'Enclave_Commander_-_Marine_Edition_v1-0-44896-1-0.fomod' Invalid archive: open/read error! Is it encrypted and a wrong password was provided? If your archive is an exotic one, it is possible that SevenZipSharp has no signature for its format and thus decided it is TAR by mistake".

 

This happened when I was creating fomod using the Enclave Commander mod and canceled the building process. Now whenever I try to run New Vegas it crashes almost immediately about 3-10 seconds in-game.

 

Is there a way I can fix this? It doesn't show up in the package manager or the load order.

[wizzydizzy]

The installation instruction only offers the choice of manual installation. It doesn't say anything about the mod being fomod-ready.

So I don't know, why you've used the package manager with this one, unless you have created an installer script.

 

Suggest deleting the .fomod file from your "mods" folder and deleting all files that came with the mod as well. You can try reinstalling it afterwards.

 

 

[bsmetal]

Well, to be more specific I was using the 'Create from folder' tool and canceled it during its building process. But I found it and deleted it so I no longer get that error message anymore which is good, but i'm guessing why my game still crashes after loading must be something else..

[wizzydizzy]

Did check, if your load order is the reason for crashes?

Did you get any error messages?

 

FNVEdit will report errors due to laod order, so you might want to try that.

[bsmetal]

I in matter of fact did check on FNVEdit and there is no load order problems according to it, I have 1 merge patch if that helps.

[wizzydizzy]

Just to get it right, when is FNV crashing exactly?

Before the main menu is displayed or if trying to load a save?

 

To make sure it's not your merged patch, you can do the following:

 

After loading your merged patch into FNVEdit (only select the patch), right-click anywhere in the left-side window and select "apply filter".

Make sure only "conflict inherited by parent" is checked (near the right bottom). Click apply/OK.

When the filtering process is done, right-click on the patch and select "check for errors".

Each error reported indicates mod conflicts that couldn't be resolved.

 

This is when the usual routine has to be started:

Deactivate mods and check, if you still experience CTDs. If you still get CTDs after having deactivated every mod, it's the time for starting a new game (if starting a completely unmodded game solves the problem, you might have a corrupted save) or a clean install.

 

 

[bsmetal]

I think I may have found the source of CTD, FNV seems to crash when I check the 'items' menu in the pip-boy.

 

I was changing stats on the Ahztek's Weapon Overhaul and the AWOP patch for it. And now whenever I go to that submenu in-game the game CTD's. I've checked the GECK for any duplicates and ran it through FNVEdit a few times along with a new merge patch for it, but still seems to crash.

[wizzydizzy]

It depends on what changes you made to the mod.

If you, for some reason, changed the Form IDs of some objects, this can be problematic.

[bsmetal]

I did take notice after making *slight* changes to many things in the AWOP overhaul patch is that there were multiple Form IDs of the same items.

 

I have deleted the items with duplicate IDs (as I still have no idea where it came from) but the game still seems to crash whenever I decide to use the AWOP patch now. As it is the source of the crashing..

[wizzydizzy]

Multiple Form IDs with the same entries should not be a problem, as long as the original Form ID still exists, as it's the one the mod is looking for.

With several items having the same FormID it's completely different. This will produce a crash in almost all cases.

 

Have you tried running the game with the original mod files and patches?