You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to figure out what's going on here, not sure what it is.
Using the latest DepotDownloader, when attempting to download Monster Hunter World's Pre Iceborne builds 24th December, 2019, the preallocation portion only allocates 24GB of files. The download then completes without issue.
For reference, 5080591846956782264 is 51gb~
Attempting to download with username and password arguments 582010 582011 5080591846956782264.
If you go further back, it gets worse.
If you download the second oldest build, it only allocates 16GB.
Trying to run either of these downloaded manifests obviously causes the game not to launch.
Meanwhile? The lastest and last few builds download all 50+gb just fine. It's only these older ones.
Does anyone have any ideas? Maybe the manifests are corrupt on steams servers? Maybe the command silently omits any portions of file that timeout during lookup or something?
I believe this is reproducible as it's happened on my Windows PC, my Steam deck under Linux, and at work and at home.
The text was updated successfully, but these errors were encountered:
I'm trying to figure out what's going on here, not sure what it is.
Using the latest DepotDownloader, when attempting to download Monster Hunter World's Pre Iceborne builds 24th December, 2019, the preallocation portion only allocates 24GB of files. The download then completes without issue.
For reference, 5080591846956782264 is 51gb~
Attempting to download with username and password arguments 582010 582011 5080591846956782264.
If you go further back, it gets worse.
If you download the second oldest build, it only allocates 16GB.
Trying to run either of these downloaded manifests obviously causes the game not to launch.
Meanwhile? The lastest and last few builds download all 50+gb just fine. It's only these older ones.
Does anyone have any ideas? Maybe the manifests are corrupt on steams servers? Maybe the command silently omits any portions of file that timeout during lookup or something?
I believe this is reproducible as it's happened on my Windows PC, my Steam deck under Linux, and at work and at home.
The text was updated successfully, but these errors were encountered: