It doesn't matter what version your game files are. You can use this on a backed up copy. You can use this with downgraders. You can use this on a brand new copy with CC content.
There's one requirement: A downgraded 1.10.163 version of Fallout4.exe and steam_api64.dll. GOG editions additionally need Galaxy64.dll.
If you're using Buffout 4 and encounter CTDs: Disable Buffout's archive limit option. I'll have to investigate it later.
Straight-up, this thing doesn't work, and I never even upgraded to 'next-gen' version.
I've manually deleted the Whole Interface directory that comes with this mod (not that I needed as MO2 didn't report any conflicts whatsoever), yet I still crash after about 10 seconds of game loading (I'm running the game through F4SE in MO2).
The only fix I've found is to disable this mod and use BA2 Archive Version Patcher instead. It's a tool that downgrades all the archives so they can be opened by other tools (such as BAE or Cathedral). I personally use it if mod author didn't provide loose files and only provided the new (incompatible) archive.
When it comes to new/updated mod archives (made with/for next-gen version), I tend do the following:
Prefer loose files, if they are available. If not, download and patch the archive with the tool mentioned above.
Open the newly patched BA2 in Cathedral or BAE.
Extract the archive so I can have loose files.
Using Cathedral, I pack (archive) the freshly extracted files to a new archive with the same name as the old one. This allows me to have the latest stuff on old, unsupported version, and so far everything works properly - I didn't notice any issues. Granted, I only 'patched' 2 or 3 mods with this technique. Note: Technically, once you have the loose files you don't need to deal with Cathedral to pack them again to new archive for old format, but I'm a sucker for performance and on my system the difference is visible - loose files perform less and my machine has to work harder than with BA2 archive.
Play the game and think how Bethesda shouldn't be in business because time has proven they do more harm than good. I've been playing Fallout series for ages and it's no doubt it's my favorite and most played game on Steam. But I mean, come on - this is not the first time this has happened, yet they did it again.
What a shitshow of an update, honestly. Looking forward to the day Bethesda falls, they deserve nothing more. Just my honest opinion.
So I've already downgraded my game by downloading the depots and removing most of the CC content from the directory, by installing this, would it be safe to just reinstall the old CC content or does that require some extra stuff on my part?
yeah. as long as you add both the cc content and the updated esms and archives, you should be fine. it works for me, just make backups before doing this in case you want to revert. i made a new mod package in mo2 and placed all the 1.10.980 updated files in it, so i can turn the update on and off at will if needed, until it's safe to do a full update in the future.
So, could someone please clarify for me: does this only work for downgraded versions of 1.10.163, or can people that haven't upgraded to 1.10.980 yet use this as well?
it's totally redundant to use this mod with any game version above 163. it just doesn't make sense to add a bandage on top of a bandage, there's no wound to be treated.
Not what I meant; what I meant is, if I never upgraded to the next-gen update (i.e. by disabling Steam's auto-update for Fallout 4 like I did), would I still be able to use this? Or would I have to upgrade to next-gen and then downgrade back to 163? Because near everything I've seen talks about using this when downgrading back, but I haven't seen anything about trying to use this without having updated the game at all.
I'm using original 163 and it doesn't work for me. So far my only option has been to patch the newer archives so I can use mods that are packed that way.
I have 1.10.130 version.. Will this allow some mods to work now? Most install and show checked in mod manager. I have a few though that install Fine but show unchecked and grey. Any reason for this? Game runs fine.. No conflicting mods, just some don't show up right in mod manager in settings..
this makes post-nextgen mods playable at the version of the game previous to nextgen update, if you load next gen mods with previous versions your game automatically crashes. This mod makes that posible.
Wondering if someone could help. Edit: found it (it's packed up in this mod BA2, it's a copy of Archive2 from b4 the next gen update)
I want to keep my fallout4 with this useless next gen upgrade, lol. It's just easier for me and i don't mind waiting for mod updates.
Problem is, this update also updated Archive2, and now I can't pack ba2 files for Fallout 76 (FO76 simply doesn't recognize ba2s packed with current Archive2). Anyone know how I can get the old Archive2, or downgrade just this one program?
I've looked through this, so I'm hoping I'm not reposting a question. In Mod Organizer v2.5.0, this mod does not appear in "Plugins", rather it solely appears in the mod-list. The game launches properly with the simple downgrader, and the new content from the next-generation patch is listed as "BackportedBA2". All things considered, it looks like it's working. Should I worry irregardless?
194 comments
There's one requirement: A downgraded 1.10.163 version of Fallout4.exe and steam_api64.dll. GOG editions additionally need Galaxy64.dll.
If you're using Buffout 4 and encounter CTDs: Disable Buffout's archive limit option. I'll have to investigate it later.
https://pastebin.com/38umXMCr
I've manually deleted the Whole Interface directory that comes with this mod (not that I needed as MO2 didn't report any conflicts whatsoever), yet I still crash after about 10 seconds of game loading (I'm running the game through F4SE in MO2).
The only fix I've found is to disable this mod and use BA2 Archive Version Patcher instead. It's a tool that downgrades all the archives so they can be opened by other tools (such as BAE or Cathedral). I personally use it if mod author didn't provide loose files and only provided the new (incompatible) archive.
When it comes to new/updated mod archives (made with/for next-gen version), I tend do the following:
What a shitshow of an update, honestly. Looking forward to the day Bethesda falls, they deserve nothing more. Just my honest opinion.
Hope this info is useful! Take care!
Since the nxg update I need something like this to get the DLC files to work with the VR version, sadly
i also use vr and would like to know
this trick is only if you sadly upgraded 1.10.980 or 1.10.984
Any word on this?
Wondering if someone could help.
Edit: found it (it's packed up in this mod BA2, it's a copy of Archive2 from b4 the next gen update)I want to keep my fallout4 with this useless next gen upgrade, lol. It's just easier for me and i don't mind waiting for mod updates.
Problem is, this update also updated Archive2, and now I can't pack ba2 files for Fallout 76 (FO76 simply doesn't recognize ba2s packed with current Archive2). Anyone know how I can get the old Archive2, or downgrade just this one program?