kanguru

Version 1.12.0-BETA.3 no longer alerts that deployment is necessary

Thanks, @Citadel535 I get what you're saying about the painful process of tracking down a mod responsible for crashes. I have already been through the "disable recently changed mods" dance without finding a culprit. I've done binary search-like disabling before (never as simple as it sounds) and will probably be doing it again. In this case, it does not feel like a mod problem: the same collection of mods both works and does not work to load my most recent saves. That said, it doesn't feel like a Vortex problem, either, given that while it arrived with 1.12.0-BETA.2, it stuck around after downgrading to 1.11.7 and then disappeared temporarily after reinstalling 1.12.0-BETA.2 before returning after the system was rebooted (nice to have a workaround, but it sure is fiddly). Thanks for the "delete pipeline cache" suggestion. I'll test that and see if it helps.

In theory, I'm sure that's right; Vortex itself shouldn't cause a game crash. In practice, however, it's all software, which has been known to do things it's not supposed to; all software has bugs, apparently. I appreciate that it's unlikely Vortex is responsible, but I thought I'd ask and see if anyone else had seen this behaviour. I wonder how I could debug further? Vortex.log and file tree checksums from the deployments where the game works compared to where it doesn't? I'll see if that shows anything. Any other debugging advice is welcome.

I don't know that this crash is due to the BETA.2 update of Vortex 1.12.0, just that it has been happening regularly since then. I see the crash regularly when loading recent saves for Starfield (exit saves, auto saves and regular saves). If I downgrade to 1.11.7 I get the same crashes. New games work fine. Seems like there's a problem with my saves, doesn't it? HOWEVER When I upgrade to 1.12.0-BETA.2 again, I can load saves that were crashing only a few minutes ago without problems! I've followed this path three times so far and I see the same crashes each time, then things just start working again. Anyone seen anything as weird as this before? Do I win an award?

Since installing 1.12.0-BETA.2, each time I start Vortex I see the message "Deployment necessary" for Starfield. I think this is new behaviour. To confirm: I just updated a mod which caused a new deployment, then I quit Vortex. On restart, I get the "Deployment necessary" message again. Running a deployment manually by clicking the "Deploy Mods" button, I note it runs much faster than I'm used to, yet on restarting Vortex I'm again told "Deployment necessary". I have been running Starfield Vortex Extension 0.7.1 since 13 June 2024.

Same here. The Vortex error message also says of allegedly missing files, "these plugins will be commented out of your plugins file," but this does not appear to be happening; there are no commented out plugin files in plugins.txt.

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.

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.

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.

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.

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 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 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.

Attached screen clip shows I'm running the beta version and still getting error message "Incompatible mod archive(s)".

Thanks, @showler, that was exactly the point of my post: I AM running the beta, yet I still see the error. I thought it might be useful for Vortex developers to know that the beta hasn't fixed it, at least in my case. Further, the error is occasionally triggered for other mods, see attached screen clip. (If anyone can point out where the language I use makes that point harder to see, please let me know so I can improve future reports.)

I downloaded the beta because the release notes suggested that the "Incompatible mod archive(s)" but had been fixed, but I must have misread them because I'm still seeing the warning for the Unofficial Fallout 4 Patch (see attached). Perhaps I'm doing something wrong, though? Does anyone have any advice for me?

Oh, fantastic! Just what I needed. Thank you.