Creation Club "Lookup Failed!" Messages

[UUFrost]

I grabbed the free Horse Power Armor today from creation club, but all the pieces show "LOOKUP FAILED!"

 

I researched this a good hour. Found a lot of good info, but none of it helped.

 

I did ALL of the following:

 

I completed deleted my strings folder in the Fallout 4 Data folder.

I disabled EVERY mod and completely removed the "Full Dialog Interface" mod.

I removed all my fallout ini files in both the steam directory and in my profile.

I verified the integrity of the game files using Steam.

 

NONE of this worked. I'm stumped. If anyone has a suggestion, I'm open.

 

Tomorrow I'll be completely deleting Fallout 4 and EVERY mod and reinstalling everything if I can't find a fix.

 

 

 

[JagMaker]

i don't know how cc mods looks like, but if it .esp file - load it in esp/esm translator and change 'lookup failed' to smth like 'Horse Head'

 

'horse head armor' in fallout.. like a knife to the heart

Edited September 16, 2017 by JagMaker

[ShinKungFuMan]

UUFrost, have you tried taking the pieces to a power armor station and adding a mod to them? That may automatically correct the name for you...however in the event it doesn't, try this:

 

Open it up in the CK, and go to Instance Naming Rules. You'll want to make a duplicate of dn_PowerArmor (something like dn_PowerArmorH). Now go into the armor files themselves (sort by Form ID and you should have them right at the top, all 6 pieces). Open these and you'll see a dropdown tab that says dn_PowerArmor. Just change this to the duplicate Instance Naming Ruleset you made.

 

I've got a fix/rebalance on here too that fixes that as well, but either route should get you covered. In either case you *have* to take the pieces to an armor station and apply a different mod to them so it resets their name properly.

Edited September 16, 2017 by Kung Fu Man

[UUFrost]

Thanks man! I actually found that out by accident.

 

I even uninstalled FO4, F4SE, and EVERY mod.

 

Then I reinstalled JUST Fallout 4 and F4SE and the error was still there. This means it's "baked" into the save file, so I'm really glad the workbench fixed it.