I tried updating this mod, I've tried renaming it, then even deleting it. I've then tried deleting ALL my mods but nothing will resolve the "LOOKUP FAILED!" bug for my weapons. Is there something I'm missing or am I screwed and have to start a new game altogether?
Oops! I figured it out. >.< I had deleted the wrong file. I deleted the one I put in the main data directory and NOT the one in the My games Directory. I fixed it!
Note: For some reason, with this mod installed, the new hunger and thirst system show the Look Up Failure now in its info screen. Had to delete this mod till it's fixed.
I had exactly same issue, not only at weapons inside inventory, but also at weapons workbench. Disabled all my mods one by one, and the culprit was indeed "What's that Quest". I hope Quaraxkad will update it sooner or later.
I had the same issue, definitely caused by this mod. So, I followed Quaraxkad instructions from their article about using xTranslator, loading first the Starfield esm, then loading the mod translation and then finalizing it - and with the so generated Starfield_en.strings the issue is gone.
Since this is unexpected, I did a binary comparison of the generated files and found significant differences. So, I compared the overwrite completeness of both generated files by resetting the translation of the esm file before importing the strings file. While my file has a 100% coverage, the mod authors file is missing 689 entries, which I suspect is the root cause. I wonder if the deluxe editions (which I have) has a different strings_en file than the regular Starfield edition.
I have no idea why but this mod now causes a "Look Up Failure" error since the new Bethesda patch was released. It worked fine before that but now at least in my game something is causing a conflict. I have had this mod for awhile and it worked fine. I haven,t downloaded any other mods in awhile so it was working fine with all my other mods.
The error is only in the weapons inventory. Why it would effect weapons only again I have no idea. Maybe it is something else in my game that it is conflicting with I don t know but it was a real pain tracking this one down because it didn't appear that this mod would have anything to do with weapons.
As Murphys law would have it, I have 51 mods and this was the very last one I checked because it was one of the mods I least expected to be a problem.
Yeah I just renamed the strings file as back up for now. I've had this problem (Look up failure)before in Skyrim so just searched for string files in Starfield using good old windows explorer, for anyone needs to quickly bugfix in future. I'd never have guessed it was this one, even though I now remember the author explicitly warning us of the method he used, which should have had my Skyrim modder brain working... Sad, hope he updates.
Author hasn't been seen on Nexus for almost three weeks. Dang! I reluctantly am going to have to disable this mod due to it breaking the game after Starfield's latest patch :(
I am (was) in the same position. Just like the other person, I didn't think this one was it but... And damn, I really hope the author comes back to this, because it's such a useful mod! edit: Does anyone know of an alternative that does (nearly) the same thing?
This subject is also being discussed in the StarUI Inventory mod, as this "Lookup Failed" message started to appear in place of the name of many weapons, when we access the inventory through that mod.
The problem is that this mod is based on or alters original game files that exist in the Strings folder, a subfolder (invisible in the vanilla game, as it is compressed in one of the *.ba2 files), but one of the latest Starfield updates (update 1.10 .31 or 1.10.32) changed these original files and now this mod and other mods that use the contents of that Strings subfolder no longer work.
The solution is to disable these mods and wait for them to update. Likewise, if your game shows the contents of the Strings subfolder, confirm that the files there are from a date prior to these last two Starfield updates and delete that content, as it was almost certainly placed there by one of these outdated mods.
Ehm... Also, I have all starui mods (all five of them) installed and enabled and I'm using it without any problems? Or at least, I did so yesterday? I'm about to boot it up, so I'll update this if there's a problem. (and even if there's not.)
You ARE referring to the starUI, starUI hud, starUI inventory, starUI outpost, starUI ship builder and starUI workbench mods, right?
And if you are using the game purchased on Steam, you cannot go back to the previous version of the game. Previous versions of the game are not available on Steam in the case of Starfield, which is a shame.
I deleted this mod but my weapons STILL have the LOOKUP FAILED! bug. I've tried everything I can but I can't seem to get it resolved. I think my game is forever corrupt. :`(
111 comments
I've then tried deleting ALL my mods but nothing will resolve the "LOOKUP FAILED!" bug for my weapons.
Is there something I'm missing or am I screwed and have to start a new game altogether?
Oops! I figured it out. >.<
I had deleted the wrong file. I deleted the one I put in the main data directory and NOT the one in the My games Directory. I fixed it!
Since this is unexpected, I did a binary comparison of the generated files and found significant differences. So, I compared the overwrite completeness of both generated files by resetting the translation of the esm file before importing the strings file. While my file has a 100% coverage, the mod authors file is missing 689 entries, which I suspect is the root cause.
I wonder if the deluxe editions (which I have) has a different strings_en file than the regular Starfield edition.
The error is only in the weapons inventory. Why it would effect weapons only again I have no idea. Maybe it is something else in my game that it is conflicting with I don t know but it was a real pain tracking this one down because it didn't appear that this mod would have anything to do with weapons.
As Murphys law would have it, I have 51 mods and this was the very last one I checked because it was one of the mods I least expected to be a problem.
If this mod is disabled, problem goes away.
edit:
Does anyone know of an alternative that does (nearly) the same thing?
The problem is that this mod is based on or alters original game files that exist in the Strings folder, a subfolder (invisible in the vanilla game, as it is compressed in one of the *.ba2 files), but one of the latest Starfield updates (update 1.10 .31 or 1.10.32) changed these original files and now this mod and other mods that use the contents of that Strings subfolder no longer work.
The solution is to disable these mods and wait for them to update. Likewise, if your game shows the contents of the Strings subfolder, confirm that the files there are from a date prior to these last two Starfield updates and delete that content, as it was almost certainly placed there by one of these outdated mods.
You ARE referring to the starUI, starUI hud, starUI inventory, starUI outpost, starUI ship builder and starUI workbench mods, right?
Yes, I was referring to StarUI mods.
And if you are using the game purchased on Steam, you cannot go back to the previous version of the game. Previous versions of the game are not available on Steam in the case of Starfield, which is a shame.
Breaks the Status Effects to LOOKUP FAILED strings.
Version. 1.11.36