PSanteusanio Posted May 9 Share Posted May 9 (edited) Having the same issue. Clean install of latest version of Fallout 4 Next Gen v.1.10.980 with no patches installed from previous FO4 versions. Installed Unofficial Fallout Patch v.2.1.6c and received same Check Fail message as in previous posts. For information, when I originally installed FO4, I also installed LOOT v.2.23 in the Tools menu. When opening and using LOOT to check load order I notice a discrepancy between the Unofficial Fallout Patch version in Vortex (v.2.1.6c) and the version number in LOOT. Loot was not reading the correct updated version but the old version number of the Unofficial Fallout Patch. Hope that helps. I also tried using the Beta version of Vortex 1.11.2 and still got the Check Fail Message. Edited May 9 by PSanteusanio just to clarify Link to comment Share on other sites More sharing options...
kanguru Posted May 10 Author Share Posted May 10 My original report was based on FO4 updated by Steam to 1.10.980 (no downgrade). Vortex upgraded itself after I told it to switch to the Beta channel. When I start Vortex it tells me it's up to date. Version banner says 1.11.2-BETA. (I initially sought a method for a clean install with the beta version, but I couldn't find out how to do that). UFO4P upgraded by Vortex to version 2.1.6c and the following spoiler shows md5 hashes Spoiler Hashes of UFO4P's ba2 files C:\Users\sean\Apps\xEdit_4.1.5f λ md5sum.exe "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Unofficial Fallout 4 Patch - Main.ba2" \0fca55b40556141683802c10c10306cf *C:\\Program Files (x86)\\Steam\\steamapps\\common\\Fallout 4\\Data\\Unofficial Fallout 4 Patch - Main.ba2 C:\Users\sean\Apps\xEdit_4.1.5f λ md5sum.exe "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Unofficial Fallout 4 Patch - Textures.ba2" \94807394d51b85fad1c73bd318857881 *C:\\Program Files (x86)\\Steam\\steamapps\\common\\Fallout 4\\Data\\Unofficial Fallout 4 Patch - Textures.ba2 As expected, BSArch64 v0.9c shows UFO4P and PPR ba2 archives all are Fallout 4 version 0x08 format exactly as the error message suggests. Version info in the following spoiler Spoiler BSArch64.exe ba2 file version information C:\Users\kanguru\Apps\xEdit_4.1.5f λ BSArch64.exe "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Unofficial Fallout 4 Patch - Main.ba2" BSArch v0.9c x64 by zilav, ElminsterAU, Sheson Packer and unpacker for Bethesda Game Studios archive files The Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/. The Source Code Form is available at https://github.com/TES5Edit/TES5Edit Archive Name: C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Unofficial Fallout 4 Patch - Main.ba2 Format: Fallout 4 Version: 0x08 Files: 1584 C:\Users\kanguru\Apps\xEdit_4.1.5f λ BSArch64.exe "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Unofficial Fallout 4 Patch - Textures.ba2" BSArch v0.9c x64 by zilav, ElminsterAU, Sheson Packer and unpacker for Bethesda Game Studios archive files The Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/. The Source Code Form is available at https://github.com/TES5Edit/TES5Edit Archive Name: C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Unofficial Fallout 4 Patch - Textures.ba2 Format: Fallout 4 DDS Version: 0x08 Files: 1 C:\Users\kanguru\Apps\xEdit_4.1.5f λ BSArch64.exe "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\PPF - Main.ba2" BSArch v0.9c x64 by zilav, ElminsterAU, Sheson Packer and unpacker for Bethesda Game Studios archive files The Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/. The Source Code Form is available at https://github.com/TES5Edit/TES5Edit Archive Name: C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\PPF - Main.ba2 Format: Fallout 4 Version: 0x08 Files: 217 C:\Users\kanguru\Apps\xEdit_4.1.5f λ BSArch64.exe "C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\PPF - Textures.ba2" BSArch v0.9c x64 by zilav, ElminsterAU, Sheson Packer and unpacker for Bethesda Game Studios archive files The Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/. The Source Code Form is available at https://github.com/TES5Edit/TES5Edit Archive Name: C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\PPF - Textures.ba2 Format: Fallout 4 DDS Version: 0x08 Files: 4 The only further issue I can see is that I have around 255 plugins, Vortex doesn't always error on the PPF ba2 files and now I have reduced the non-light plugin count significantly, I am not getting the error messages. Perhaps I'm seeing an issue related to that 256 plugin limit? Kind Regards. Link to comment Share on other sites More sharing options...
kanguru Posted May 10 Author Share Posted May 10 18 hours ago, Pickysaurus said: Beta version 1.11.2 should no longer show these warnings. If you're still seeing them you simply can't be on the latest beta. 1.11.1 did have an issue where the fix wasn't actually included. In that case, there would have to be an issue in the Vortex installer where it changes enough of the installation to have the banner changed to report 1.11.2-BETA but other parts of the previous install remain. I initially looked for a 1.11.2-BETA installer online, but couldn't find one; the only mechanism I'm aware of is the self-update after changing the Update setting to the Beta channel, which is what I've used. If you can point me to an installer for the beta, I'll do an uninstall and then a clean install. Link to comment Share on other sites More sharing options...
showler Posted May 10 Share Posted May 10 (edited) Check the Vortex GitHub? Edit: https://github.com/Nexus-Mods/Vortex/releases/tag/v1.11.2-beta Edited May 10 by showler 2 Link to comment Share on other sites More sharing options...
kanguru Posted May 10 Author Share Posted May 10 1 hour ago, showler said: Check the Vortex GitHub? Edit: https://github.com/Nexus-Mods/Vortex/releases/tag/v1.11.2-beta Wow. Github, eh? The search I ran on Duckduckgo after reading the UFO4P note that said "fixed in the beta" didn't show Github; I should have searched with Bing! NOTE: The screen clip I posted of the extended error message was an old version taken with Vortex 1.10.8 (the last sentence says "Archives for this game must be BA2 files (v1)." whereas the 1.11.2-BETA version says "Archives for this game must be BA2 files (v2/1)." The errors I am seeing use the newer code which specifies versions for Fallout 4 must be [2, 1]. Dates on the files of the current install all seem to be 3 days old... I'll now see how a cleanly installed version behaves. ... A clean install behaves in the same way, incorrectly flagging UFO4P and PPF in the same way as previously. Link to comment Share on other sites More sharing options...
PSanteusanio Posted May 12 Share Posted May 12 On 5/10/2024 at 5:25 AM, kanguru said: Wow. Github, eh? The search I ran on Duckduckgo after reading the UFO4P note that said "fixed in the beta" didn't show Github; I should have searched with Bing! NOTE: The screen clip I posted of the extended error message was an old version taken with Vortex 1.10.8 (the last sentence says "Archives for this game must be BA2 files (v1)." whereas the 1.11.2-BETA version says "Archives for this game must be BA2 files (v2/1)." The errors I am seeing use the newer code which specifies versions for Fallout 4 must be [2, 1]. Dates on the files of the current install all seem to be 3 days old... I'll now see how a cleanly installed version behaves. ... A clean install behaves in the same way, incorrectly flagging UFO4P and PPF in the same way as previously. I will assume, from your last sentence in your post, that this issue is still unresolved. The question now is, despite this problem between Vortex/LOOT and UNFO4 patch, with the Unofficial FO4 patch plugin enabled in Votex, is it working as intended in game? Link to comment Share on other sites More sharing options...
Solution Pickysaurus Posted May 13 Solution Share Posted May 13 Looks like the fix didn't make it into 1.11.2 either, 1.11.3 will be hitting the stable branch today which will finally put this issue to bed! Sorry for the confusion. 1 Link to comment Share on other sites More sharing options...
kanguru Posted May 13 Author Share Posted May 13 19 hours ago, PSanteusanio said: I will assume, from your last sentence in your post, that this issue is still unresolved. The question now is, despite this problem between Vortex/LOOT and UNFO4 patch, with the Unofficial FO4 patch plugin enabled in Votex, is it working as intended in game? I haven't seen any in-game issues. I've just been reporting an error message displayed when there is no error while the release notes reported it had been a known issue that had been fixed. Link to comment Share on other sites More sharing options...
kanguru Posted May 13 Author Share Posted May 13 7 hours ago, Pickysaurus said: Looks like the fix didn't make it into 1.11.2 either, 1.11.3 will be hitting the stable branch today which will finally put this issue to bed! Sorry for the confusion. Fixed for me, I can now confirm. V8s are way cooler than V2s, so I suppose Bethesda's change makes some kind of sense. Thank you. Link to comment Share on other sites More sharing options...
PSanteusanio Posted May 13 Share Posted May 13 1 hour ago, kanguru said: Fixed for me, I can now confirm. V8s are way cooler than V2s, so I suppose Bethesda's change makes some kind of sense. Thank you. Thank-you all for your feedback and info. I just updated to Vortex v 1.11.3 and ran the plugin sorter and everything worked as it should. Yea! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now