Give Feedback
0 of 0
About this mod
If everything else fails then this patch is for you! CTD fix for AWKCR and Armorsmith Extended.
- Requirements
- Permissions and credits
- Donations
What this patch addresses ?
Are you getting invisible items in workshop mode at the crafting section followed by a CTD? Then this is for you!
When to use this patch?
When you have already tried everything else and nothing worked. Things to try before using this patch.
"Quotes from Gambit77 at the official mod page"
1) Check your plugins tab to verify you have the current version of AWKCR installed. What you're describing is what happens when you have overwritten ArmorKeywords.esm with an old version and are therefore missing used keywords, which causes a CTD when the game looks for them. Old versions of ArmorKeywords.esm are packed with both Concealed Armors and Crafting Workbenches, say no when asked if you want to overwrite Armorkeywords.esm when installing them.
2) You do not have ArchiveInvalidation properly set up in your Fallout4.ini. This is required for the game to use custom assets.
3) NMM failed/was prevented to properly extract the asset files when installing the mod. Check that you have the file ArmorKeywords - Main.ba2 in your Data folder. If not, extract it manually from the .zip and put them there. If you have that and you're crashing try installing the loose files for the benches in the optional section of the file downloads.
4) 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. "
So if all that fails then this is for you.
Important Note!
This patch will make the custom workbench meshes from AWKCR - AE to be replaced with vanilla benches, the functionality is the same ofcurse. That's how this patch works.
Are you getting invisible items in workshop mode at the crafting section followed by a CTD? Then this is for you!
When to use this patch?
When you have already tried everything else and nothing worked. Things to try before using this patch.
"Quotes from Gambit77 at the official mod page"
1) Check your plugins tab to verify you have the current version of AWKCR installed. What you're describing is what happens when you have overwritten ArmorKeywords.esm with an old version and are therefore missing used keywords, which causes a CTD when the game looks for them. Old versions of ArmorKeywords.esm are packed with both Concealed Armors and Crafting Workbenches, say no when asked if you want to overwrite Armorkeywords.esm when installing them.
2) You do not have ArchiveInvalidation properly set up in your Fallout4.ini. This is required for the game to use custom assets.
3) NMM failed/was prevented to properly extract the asset files when installing the mod. Check that you have the file ArmorKeywords - Main.ba2 in your Data folder. If not, extract it manually from the .zip and put them there. If you have that and you're crashing try installing the loose files for the benches in the optional section of the file downloads.
4) 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. "
So if all that fails then this is for you.
Important Note!
This patch will make the custom workbench meshes from AWKCR - AE to be replaced with vanilla benches, the functionality is the same ofcurse. That's how this patch works.