{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/1/2017 8:42:51 AM
4
Moving game folder.
Hello, I want to put destiny 2 in my new ssd, I was wondering if I can simply copy paste the game folder or if I have to redownload/reinstall the whole thing one more time. I wasn't able to find useful information by googling.
Thanks
-
Just moved the game to a new hard drive. Works fine. 1) Cut and paste the Destiny 2 folder to your new drive. 2) Open the settings in the Blizzard Launcher. 3) Click Game Install/Update tab. 4) Change the path to the new location under "Folder used for gameplay." 5) Launch and play.
-
Have you tried moving it and clicking "Already installed? Locate the game." next to the Install/Play button in the Blizzard Launcher?
-
Edited by suttungur: 12/2/2017 3:13:12 AMI moved it. Here's what I did: 1. Install to e.g. C:\Games\Destiny 2 2. Move Destiny 2 directory (CTRL+X) to e.g. Z:\Games 3. Create a symlink inside C:\Games (open cmd here), with command: [quote]mklink /J "Destiny 2" "Z:\Games\Destiny 2"[/quote] This way, you won't need to change the path in the blizzard launcher. EDIT: Nevermind, just saw you wanted to have it on your new SSD and not move it elsewhere... However, if the drive letter for the new SSD is the same as the old one, it should work...
-
3 RepliesI wouldn't recommend it. While I don't know how the Blizzard launcher works, any menu shortcuts, desktop icons, etc. all point to a specific spot on your hard drive. If you move the files to a new location, those shortcuts will no longer point to a valid file location. You could manually edit the paths for the shortcuts/icons to point to the new locations, but then there's still the possibility of the game relying on entries to your system registry, which is something you [i]absolutely do not[/i] want to mess with unless you really know what you're doing. You could always try it and see what happens. You could copy the folder to the SSD, then rename the orginal folder to "hide" it, and try running the executable from the new SSD location to see if it works, and if not, delete the SSD folder and change the original folder back to it's original name. But just deleting and reinstalling would be the safest way to ensure that it all gets put back properly.
