You'll need to unsubscribe in Steam and go into your /data directory to make sure its files are actually deleted)ĥ) Repeat until you have everything you want/that works re-subscribed and you can still initiate a new campaign.Įnabling small batches of mods per test is time-consuming, but it makes it easier to isolate a problem in the event you re-subscribe a "bad" one. (If you activate a mod that kills the campaign, it's probably not enough to simply disable it. For each group of mods you re-subscribe, re-enable them in your launcher (I used the CA launcher for this), start the game and see if you can launch a campaign. I did this to be sure, but I'm not sure it was necessary.)Ĥ) Start adding the mods you'd like to continue using in small batches (this is where having a Steam Collection will really pay off). Here's the solution (sorry, it's a grind):ġ) Unsubscribe all mods from Steam (I'd recommend making a personal Collection first and adding them all in, so that you have them all in one place to re-subscribe)Ģ) Manually delete all non-essential, mod-related leftover files that linger in your /Data folder (and then probably run a Verify Integrity via Steam, just to be safe)ģ) Make sure the game runs and the campaign can be started in this vanilla state (if not, you might benefit from uninstalling and re-installing the game. (It would take me hours to identify the specific culprit, so I'm not going to.) pak file was obviously sabotaging the campaign start. Even when not being flagged "on" in either the CA Launcher or KMM, the presence of it's. 2K A Total War Saga: Thrones of Britanniaįinal comment: Ok, this was indeed some sort of cruft from an un-updated mod that was floating in my /Data directory.
844 A Total War Saga: Fall of the Samurai.
0 kommentar(er)
