Actions

Fallout 4 Running Multiple Copies: Difference between revisions

From Mike Beane's Blog

mNo edit summary
Line 44: Line 44:
<pre>Copy-Item -Path "Fallout 4 - 1.10.163.0" -Destination "Fallout 4 - Vault 13 Demo" -Recurse</pre>
<pre>Copy-Item -Path "Fallout 4 - 1.10.163.0" -Destination "Fallout 4 - Vault 13 Demo" -Recurse</pre>
* Vault 13 Demo doesn't like cc (Creation Club) files.  Run the following command
* Vault 13 Demo doesn't like cc (Creation Club) files.  Run the following command
<pre>Remove-Item -Path "Fallout 4 - Vault 13 Demo\cc*" -Recurse -WhatIf -Confirm</pre>
<pre>Remove-Item -Path "Fallout 4 - Vault 13 Demo\Data\cc*" -Confirm</pre>
** Y for each individual file, A for All, L will skip them all.
* Grab a copy of f4se for 1.10.163.0 and install that in "Fallout 4 - Vault 13 Demo" per the mod installation directions of the mod.
* Grab a copy of f4se for 1.10.163.0 and install that in "Fallout 4 - Vault 13 Demo" per the mod installation directions of the mod.
*# [https://www.nexusmods.com/fallout4/mods/42147?tab=files get old file version 0.6.23]
*# [https://www.nexusmods.com/fallout4/mods/42147?tab=files get old file version 0.6.23]

Revision as of 14:44, 10 August 2024

Stub page for thoughts

Fallout London requires 1.10.163.0 Vault 13 Demo requires 1.10.163.0 Fallout 4 Next Gen is > 1.10.163.0

I wonder if "Mod Organizer 2" would do what I'm trying to do (is it easier for me just figure out directory swapping?)


Read-Only

For Steam users, to stop Fallout 4 from auto updating to the latest version:

  • Find "appmanifest_377160.acf" and set it to Read-Only
    • I have two copies of the .acf, one each with the flag set differently

Clean Base Installs

Note: make sure you local saved games are safely backed up. I'm not sure I'll look too hard in how to manage saved games (maybe there is a mod for that).

1.10.163.0

  • Goal: Create a clean installation folder named "Fallout 4 - 1.10.163.0"
  • Pre-Requisite: .....\Steam\steamapps\appmanifest_377160.acf is set to Read-Only
    • See notes above
  • Background: Since the Nextgen update there have been mods coming out that require the pre-Nextgen Fallout installation to work. Creating a clean base install folder that can be used as the foundation for starting different mod installs seems like the way to go. G

1.10.984.0

  • Make sure that the current Fallout 4 isn't really needed.
  • From the library manager, remove the installation.
  • Start a fresh installation.
  • After install, before you run the game, copy the Fallout 4 folder
  • Rename the copied folder "Fallout 4 - 1.10.984.0"
  • Place the new folder at ...Steam\steamapps\common

Clean Base Prep Completed

You should now have a copy of each Fallout 4 base version, never run, at ...Steam\steamapps\common. Next steps will make copies of these folders in relation to the specific mod.

Vault 13 Demo

  • Go to ...Steam\steamapps\common
  • Shift+Right click in the folder and select Open Powershell Window Here or Open Command Window here
    • If the latter, type powershell.exe and press enter in the command window
  • Run the following command and wait while it copies files
Copy-Item -Path "Fallout 4 - 1.10.163.0" -Destination "Fallout 4 - Vault 13 Demo" -Recurse
  • Vault 13 Demo doesn't like cc (Creation Club) files. Run the following command
Remove-Item -Path "Fallout 4 - Vault 13 Demo\Data\cc*" -Confirm
    • Y for each individual file, A for All, L will skip them all.
  • Grab a copy of f4se for 1.10.163.0 and install that in "Fallout 4 - Vault 13 Demo" per the mod installation directions of the mod.
    1. get old file version 0.6.23
    2. https://f4se.silverlock.org/ - Programmer's site versions
Retrieved from "https://www.mikebeane.com/index.php?title=Fallout_4_Running_Multiple_Copies&oldid=1878"