midnight dew
The last few times I've updated, instead of just downloading the update, steam is redownloading the whole game. Screenshots provided. Can I please get some troubleshooting help to figure out why. I've been told it's reading the files but the network tab in my task manager says otherwise. And steam is also showing it downloading.
midnight dew
Can someone please assist me, this does not look right at all. I have the game installed on my D: drive which is seen in the screenshot but my E: drive is running at close to 100% while the game in "installing" in steam. I have used the steam functionality to move the game from the E: drive to the D: drive previously, but it seems like there may be some lingering pointers or perhaps symbolic links or something that is still referencing the game being installed on the E: drive. This has not happened for any other game updates that I have moved between drives.
Why are write's being shown on the drive that doesn't have the game installed on?
midnight dew
What can I do to troubleshoot the issue to fix this?
midnight dew
Another update is available and I'm hesitant to press update because it will go through this "re-download of the whole game" process. Please, are there any devs out there that can help me figure this out? I cannot keep downloading ~70gb when an update is released.
errant bridge
Based on my experience on similar issues:
Better check your disk first. There could be some damaged sectors and when game is trying to verify itself it finds out corrupted files. Full redownload as a result.
midnight dew
Thank you so much for your suggestion. When you say check the disk/damaged sectors, is a chkdsk sufficient? I ran chkdsk D: and it found no errors.
I disabled set my E: drive to "Offline" in my disk management mmc and when I try to update the game, steam is saying that there is a disk write error. This is what is leading me to believe there is something referencing the game being installed on E: drive even though the game is actually installed on the D: drive.
zenith veldt
Another update is available and I'm hesitant to press update because it will go ...
Its not redownloading the game, its updating its files, this is just how they send out updates, and/or the updated files go through the whole game
midnight dew
@zenith veldt Not sure if you saw the screenshots I attached at the start of this thread but I believe they show sufficient proof it is redownloading the game in full during the "update" phase.
midnight dew
If you look at the screenshots, underneath the blue progress bar there is a download icon and next to the icon is 66.8GB/66.8GB. In another of the screenshot provided, it shows 51.7GB/66.8GB.
stoic tiger
Just a thought: maybe 50 GB is not enough free space for the patch to be applied and it decides to redownload and replace the files instead?
pastel sable
the last hotfix was 500 megs, however it needs to touch the whole game to do it, thus the 68 gigs being shown
midnight dew
the last hotfix was 500 megs, however it needs to touch the whole game to do it,...
The 68GB I have referred to again and again is the download value. Feel free to check the screenshots where that value is next to the download icon in steam and next to the download value on the right is the storage value (with a disk drive icon) also 68GB. Attached is a screenshot of the patch I downloaded at 468.6MB after fixing the issue and successfully downloading the patch only, and not the whole game (note: the value next to the download icon is 468.6MB, NOT 68.8GB).
I have fixed the issue, after scouring the logs and checking steam forums.
In a nutshell, it had to do with steam utilizing "staging folders" when you register multiple drives to store your steam games. Steam will download and copy the game to a hdd, perform the patch, then copy the updated game files back to it's designated location. More info can be found in the thread (https://steamcommunity.com/discussions/forum/1/2254559285380493121/).
In addition to that, there were files in the steamapps/downloading folder on the E: drive with the appid of remnant2 (1282100) that must have been from a failed update a while ago. I'm not 100% sure that this is what was causing it to redownload the whole game but after removing those files and updating the steam appmanifest of remnant2 to not use staging folders, I could update the game without having to redownload the whole game.
Is this a remnant 2 issue? Well, after what I've discovered and fixed, I wouldn't say it is BUT Steam is the platform you've chosen to provide the game to customers. At least a LITTLE direction would have been nice. It's frustrating when the evidence is provided in multiple screenshots yet I'm continually told it's not redownloading the whole game.