Fallout 4 Crash Crafting Tab

[BraveLittlePiggy]

Okay, so I have a few mods installed and one of them seems to keep crashing my game whenever I open the crafting tab in the settlements. It happens everywhere and it's really starting to annoy me. http://imgur.com/a/fpx96 I hope this image helps.

[Preacher403]

Well, remove them one by one until it stops crashing, then don't reload that one.

[BraveLittlePiggy]

I believe that the mod that is causing it to crash is Armorsmith extended and was wondering if anyone knew if there was a fix. Sorry for not being very descriptive.

[Rez Elwin]

Try reinstalling AWKCR, and let it overwrite anything is asks to then try again.

[BraveLittlePiggy]

Alright, Ill try that.

[BraveLittlePiggy]

Hmmm... That didn't work. I also tried reinstalling Armorsmith exteded, but that didn't do anything either.

[Rez Elwin]

I copied this from the FAQ on Armorsmith Extended


[quote=A: Crashing when hovering over the crafting category or the workbenches being invisible is caused by your game not being able to locate the custom models needed to render the workbenches. There are three possible reasons and solutions for this:

1) You do not have ArchiveInvalidation properly set up in your Fallout4.ini. This is required for the game to use custom assets.

2) NMM failed/was prevented to properly extract the asset files when installing the mod. Check that there are files in Data\Meshes\AWKCR. If not, extract them manually from the .zip and put them there.

3.You have your NMM virtual install on a different hard drive than your Fallout 4 install.

Those are the 3 main causes, there have been people that haven't been helped by those 3 fixes because the problem wasn't caused by their installation of this mod. Here's a couple solutions to their situations.

Here is what was a solution for Yopoman
"I FOUND THE CULPRIT! Turns out there was a folder in my DATA directory called "INTERFACE", I went ahead and deleted that folder after doing some reading of various forum posts, apparently the .SWF files in there can get messed up. I was uninstalling all my mods systematically, and couldn't fix the CTD but after deleted the "INTERFACE" directory and deleting the "Interface.ba2" file in the FO4 DATA folder I went and verified my game integrity through Steam and VOILA! No more CTD when using crafting stations. "

Here is what was a solution for BenScott777
"I have figured it out. So I am running windows 10 and I just found out that my computer has not only placed a Fallout 4 folder in my disk drive C, but also made a copy in the cloud service from microsoft called OneDrive. The changes to the ini i made in My Games/Fallout 4 didn't matter because the game was reading the inis that were in the OneDrive/My games/Fallout 4 instead of the ones actually stored on my computer. So it seems a lot of people are having the same issue I have been so it may be worth adding to the FAQ the idea to check if OneDrive is storing a copy of Fallout 4 and prioritizing that instead. "

If none of these solutions fix this problem for you then I don't know what you did wrong. [/quote]

[BraveLittlePiggy]

Im not sure what I am doing wrong. I have resulted in deleting the mod and playing without it. Thanks for trying to help. Really appreciated

[Pinnes]

Originally posted by Rez Elwin:

I copied this from the FAQ on Armorsmith Extended


[quote=A: Crashing when hovering over the crafting category or the workbenches being invisible is caused by your game not being able to locate the custom models needed to render the workbenches. There are three possible reasons and solutions for this:

1) You do not have ArchiveInvalidation properly set up in your Fallout4.ini. This is required for the game to use custom assets.

2) NMM failed/was prevented to properly extract the asset files when installing the mod. Check that there are files in Data\Meshes\AWKCR. If not, extract them manually from the .zip and put them there.

3.You have your NMM virtual install on a different hard drive than your Fallout 4 install.

Those are the 3 main causes, there have been people that haven't been helped by those 3 fixes because the problem wasn't caused by their installation of this mod. Here's a couple solutions to their situations.

Here is what was a solution for Yopoman
"I FOUND THE CULPRIT! Turns out there was a folder in my DATA directory called "INTERFACE", I went ahead and deleted that folder after doing some reading of various forum posts, apparently the .SWF files in there can get messed up. I was uninstalling all my mods systematically, and couldn't fix the CTD but after deleted the "INTERFACE" directory and deleting the "Interface.ba2" file in the FO4 DATA folder I went and verified my game integrity through Steam and VOILA! No more CTD when using crafting stations. "

Here is what was a solution for BenScott777
"I have figured it out. So I am running windows 10 and I just found out that my computer has not only placed a Fallout 4 folder in my disk drive C, but also made a copy in the cloud service from microsoft called OneDrive. The changes to the ini i made in My Games/Fallout 4 didn't matter because the game was reading the inis that were in the OneDrive/My games/Fallout 4 instead of the ones actually stored on my computer. So it seems a lot of people are having the same issue I have been so it may be worth adding to the FAQ the idea to check if OneDrive is storing a copy of Fallout 4 and prioritizing that instead. "

If none of these solutions fix this problem for you then I don't know what you did wrong.

[/quote]

I tried everything here and more, but in the end I fixed this problem by installing the optional files of AWCKR:
Armor and Weapon Keywords Community Resource Bench Meshes loose files ZIP
AWKCR - Color Swap Mod Slot Hider ZIP
Not sure if both are needed, but I installed both and it started woriking.

They are found here:

http://www.nexusmods.com/fallout4/mods/6091/?tab=2&navtag=http%3A%2F%2Fwww.nexusmods.com%2Ffallout4%2Fajax%2Fmodfiles%2F%3Fid%3D6091&pUp=1

I installed them simply with nexus mod manager, and it started working, oh man, over an hour of trying this and that to fix this =D the euphoria was quite something

(Note that I tried everything in the message I'm quoting before I fixed the problem with the optional files.)