New armor mods (from my mod) crashing game

[mm137]

I have been working on a pretty elaborate new set of armor mods for quite a while now, but I put it aside because every time I tried to select one of them in the menu, the game CTDs. I had hoped that the GECK would have provided some enlightenment as to what I'm doing wrong, but so far I can't figure anything out.

 

Following the pattern of vanilla armor mods (leather specifically), I have constructable objects, misc items for the loose mods, material swaps, and OMODs, plus additions to the OMOD lists for the new entries. Am I missing something? :wallbash:

 

At first I thought it was the material swaps, but even when I tried using vanilla swaps and no swaps, still CTD. :wallbash:

 

Does anybody have any experience with this, or is there a mod that adds armor mods that I can look at?

[VIitS]

When is it crashing? If it is just when you try to spawn/craft the armor/OMODs, it is something with the meshes (did you make a ground object for it?). If it is crashing on load, there is something wrong with your esp (while it will return a bunch of false positives, usually in the form of unknowns, "Check for Errors" in FO4Edit should find any such issues. They would be reported as unresolved/ "unable to resolve" errors (at least, those are the only kind of errors I have seen in a plugin that could cause a CTD on load).

 

Do you have any masters on it? If so, check to make sure the game is actually loading the master, a lot of people have had problems with getting it to load plugins properly. I have found using NMM to import your load order to work fine (at least, I haven't had any of the issues getting a plugin to load that I have seen others mention).

[mm137]

There's no new meshes involved- just material swaps. I've been using generic ground objects for the new mods, but I am wondering if that's the issue. The crashes occur in the armor workbench menu - the vanilla mods work fine, but as soon as I select one of my new ones - crash!

 

No errors in xEdit or CK, and no additional masters beyond the FO4.esm.

 

Thanks for the advice. I will post again if I make any progress.

[VIitS]

Did you include a model reference (MODL in xEdit) in your new OMODs (specifically, the nif you are applying the material swap to)? That's the only thing I can think of that would cause that.

 

Even if there was something wrong with the MSWP (which would happen if you created a new MSWP record with xEdit instead of copying an existing one and changing it/making one in the CK), all that would happen is the original texture would remain (i'm basing this on the issue "Art Gallery" had where new MSWP records linked to statics resulted in blank canvases, so it might be possible for a bad path or something in an MSWP to cause a CTD).

[mm137]

!!!

 

That might be it! Man, if that's all it is, I will be stoked. Thanks again, I really appreciate the help.

[mm137]

Looking through the vanilla files, its seems most of the vanilla armor mods don't have a Model entry. I'm going to try this anyway and see if it works, though.

Edited April 30, 2016 by mm137

[VIitS]

Huh. I knew the OMODs that didn't have visible changes didn't need a model, but I thought the ones that applied a cosmetic change, like the power armor paints, did. Looks like I was wrong.

 

It's definitely something weird going on with the mesh, or something really weird going on with the MSWP, because the spot it is crashing at means it is trying to render something and there is a problem with what it is trying to render.