Repository navigation
Handle multi-piece PS4 updates properly - #89
Closed
AphelionWasTaken wants to merge 2 commits into
Closed
AphelionWasTaken wants to merge 2 commits into
AphelionWasTaken wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewrite the PS4 search path and download function to handle PS4 updates properly. Also check for correct hashes and sizes of newly downloaded files more gracefully.
PS4 games have cumulative updates, meaning some of them are very large. Sony splits these up into multiple files, and previously PySN was only fetching the last file in the list. This PR allows PySN to find all of the piece files, download them all, and then combine them into a single update file.
Also change the hash and size checking logic to bypass is_shit_there(). We already know the file is there, so we can just move on with checking the hashes and sizes. Doesn't save much in terms of time or resources, but it is more efficient this way.