Actions

Fallout 4 Running Multiple Copies: Difference between revisions

From Mike Beane's Blog

Tag: Reverted
Tag: Reverted
Line 39: Line 39:
** If the latter, type powershell.exe and press enter in the command window
** If the latter, type powershell.exe and press enter in the command window
* Run the following command and wait.
* Run the following command and wait.
<br>
<pre>$sourceFolder = "Fallout 4 - 1.10.163.0"
<pre>$sourceFolder = "Fallout 4 - 1.10.163.0"
$destinationFolder = "Fallout 4 - Vault 13"
$destinationFolder = "Fallout 4 - Vault 13"
Line 52: Line 53:
}
}
</pre>
</pre>
<br>
* 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\cc*" -Recurse -WhatIf -Confirm</pre>

Revision as of 13:51, 10 August 2024

Stub page for thoughts

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


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.


$sourceFolder = "Fallout 4 - 1.10.163.0"
$destinationFolder = "Fallout 4 - Vault 13"

Write-Progress -Activity "Copying Files" -Status "Starting..." -PercentComplete 0

$totalFiles = (Get-ChildItem $sourceFolder -Recurse).Count
$copiedFiles = 0

Copy-Item -Path $sourceFolder -Destination $destinationFolder -Recurse -Filter * | ForEach-Object {
    $copiedFiles++
    Write-Progress -Activity "Copying Files" -Status "Copying File $($copiedFiles) of $totalFiles" -PercentComplete (($copiedFiles / $totalFiles) * 100)
}


  • Vault 13 Demo doesn't like cc (Creation Club) files. Run the following command
Remove-Item -Path "Fallout 4 - Vault 13 Demo\cc*" -Recurse -WhatIf -Confirm
Retrieved from "https://www.mikebeane.com/index.php?title=Fallout_4_Running_Multiple_Copies&oldid=1870"