Lumaan Posted September 16, 2019 Share Posted September 16, 2019 FO4 I have been unable to update the normal version with a update.https://www.nexusmods.com/fallout4/mods/23391 - Immersive Settlers. Version 1.3 download all the files then I update it to version 1.31 with only 1 file, and it only delete v1.3 and install v1.31 and all the files (v1.3) is replaced with the 1 file in v1.31.It should only replace 1 file and keep the rest still installed.I need to at the moment manual repack the files... :( Link to comment Share on other sites More sharing options...
rmm200 Posted September 16, 2019 Share Posted September 16, 2019 Somehow you replaced 1.3 with 1.31.Normally, you would install both as separate mods and Vortex conflict resolution would let you pick the file from the 1.31 mod.If you disable that mod, the 1.3 version would be used.Bottom line: Don't replace mods with patches. Keep them as separate mods. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted September 16, 2019 Share Posted September 16, 2019 Are you trying to install this mod with Vortex? Using Vortex, I installed version 1.3 and then installed the updated version 1.31. The update was successful. No files were missing. The only thing required to complete the update was to set a rule that the updated .pex file (v1.31) load after the older .pex file (v1.3). The updating process was quite straightforward, and so I'm perplexed how you wound up with only one file. rmm200 is right - you somehow replaced v1.3 with v1.31 instead of simply updating v1.3. Link to comment Share on other sites More sharing options...
Lumaan Posted September 16, 2019 Author Share Posted September 16, 2019 Had them download and they came out as same file (one shown but 2 in version numbers). No mater what mod manager I have every used (Last 15+ years) they always come at one line for v1.3 and 1.31, 2 files.And your say update it, but been doing that, v1.3 is the main file and then v1.31 is a update, downloading them but one line and replacing it. grrr. (Need to look into it, where that button is for this) And another file problem I had yesterday was FlaconOil's https://www.nexusmods.com/fallout4/mods/3747 - 3 parts and it was 3 part but somehow Vortex handle as part of files (one) where it's 3 part of 3 installation. But that one I'm okay with, modder had wrong version number. (I chance the version to 1 on all 3 part) Edit: There shoulder be one when you click version and there is 2 or more files get a popup with replaced or merged, instead of ... only button is "Check for updates" (how it work? still need to find a file to test it) Link to comment Share on other sites More sharing options...
Pickysaurus Posted September 16, 2019 Share Posted September 16, 2019 I see the problem, both files have exactly the same name. So Vortex believes that 1.31 is a new version of 1.30. This means it completely replaces it. You can rename the archive for 1.31 to something like "Immersive Settlers update" to rectify this. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted September 16, 2019 Share Posted September 16, 2019 I see the problem, both files have exactly the same name. So Vortex believes that 1.31 is a new version of 1.30. This means it completely replaces it. You can rename the archive for 1.31 to something like "Immersive Settlers update" to rectify this. Actually, having the same name is not the problem. When I installed both mods, I did so with the names unchanged. Vortex did not mistake v1.31 as a new version of 1.3. Instead, Vortex treated v1.31 as an update to v1.3 by signalling a file conflict between the two mods involving the file "marmo1233_renamescript.pex." I created a rule that the v1.31 file load after the v1.3 file. Once that was done, I checked the game data folder, and all five of the required files were there (1 esp and 4 pex files). Given my experience, I'm still very perplexed as to how the v1.31 update completely erased and replaced v1.3 in the OP's game setup. However, whatever the source of the OP's problem, your suggestion to change the mod names should solve the problem for him. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 16, 2019 Share Posted September 16, 2019 The other thing you can do when an update has the same name, is when you're installing, a confirmation box should pop up asking you whether you want to install it as a VARIATION. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted September 16, 2019 Share Posted September 16, 2019 The other thing you can do when an update has the same name, is when you're installing, a confirmation box should pop up asking you whether you want to install it as a VARIATION. In my case the box did not appear. Would that be because v1.31 contained only one updated pex file whereas v1.3 contains five files (1 esp, 4 pex)? Anyway, Vortex apparently interpreted correctly that v1.31 was a single file update and not a complete mod renovation and replacer. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 16, 2019 Share Posted September 16, 2019 The other thing you can do when an update has the same name, is when you're installing, a confirmation box should pop up asking you whether you want to install it as a VARIATION. In my case the box did not appear. Would that be because v1.31 contained only one updated pex file whereas v1.3 contains five files (1 esp, 4 pex)? Anyway, Vortex apparently interpreted correctly that v1.31 was a single file update and not a complete mod renovation and replacer. Hmmm, I bet it only pops up if its an ESP or ESM being replaced Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.