An installable version is planned but not there yet. Sorry for the wrong information on the README.One question though...
The README.md mentions an installable version via WUP Installer, but there's none on the repo.
Is that right?
The thing is... I already made one, that's why I'm asking.An installable version is planned but not there yet. Sorry for the wrong information on the README.
I have had the app freeze before and I just left it as is and after a while (about 15 mins) the download started again and finishedso after ~4 hours downloading the WiiU froze and had to be force-shut down. When I rebooted I tried downloading the same title to see if the download could resume right where it left off, but unfortunately, the download started completely over, even though I received the warning "WARNING: The download directory already exists" (this made me hopeful that it was going to scan the existing files)
In a future release, it would be great to only need downloading the remaining files that hadn't completed successfully
I waited for 5-10 and thought that was enough that it would have resumed if it were possible... if it freezes again I'll leave it for 20 minutes to make sure it can't come backI have had the app freeze before and I just left it as is and after a while (about 15 mins) the download started again and finished
It should continue where it stopped but there's a bug. Sorry about that, will be fixed in the next release (which happens as soon as I'm able to build a channel version).Click resume, downloads for a long time again, but ultimately fails every time.
It should continue where it stopped but there's a bug. Sorry about that, will be fixed in the next release (which happens as soon as I'm able to build a channel version).
in 1.5 the app freezes before starting to download the games, I tested 3 games and before starting to download it freezes, I went back to 1.4 and it worked normal
It skips files already completely downloaded but does not continue single failed files. The latter is a planned feature but needs more research as the NUS is a bit tricky here.Does this app resume partial downloads, without downloading the entire file again? I tried reading the source to see if it does but I suck at reading and understanding C. If it doesn't, I wanted to throw it out there that NUS supports Range Requests and you can request a specific range of data in your request header. Thanks for your contribution.
NUS responds to the Range request just like you would expect from any modern server. In your request header just add:It skips files already completely downloaded but does not continue single failed files. The latter is a planned feature but needs more research as the NUS is a bit tricky here.
Range: bytes=<partialFileSize>-
rqst = urllib2.Request(url)
rqst.add_header("Range", "bytes={}-".format(partialFileSize))
Sadly it does not. Or... Well, most of the times it does but there are rare exceptions.NUS responds to the Range request just like you would expect from any modern server.
Hmm... Must be really rare. I wrote a PC application called Funkii-UI that was once mildly popular. I had a version that I never released that resumes partial downloads just fine using the method I described. I tested it hundreds of times and even had other users test it more times than I could remember. Never had it fail, not even once.Sadly it does not. Or... Well, most of the times it does but there are rare exceptions.
Actually, if I remember correctly, even USB Helper has a hard time resuming partial downloads and sometimes fails. uTikDownloadHelper did it as well, and even freeShop from the 3DS couldn't do it until the devs added Sleep Downloads, which meant that practially freeShop was downloading in the same way the 3DS eShop downloads games.Hmm... Must be really rare. I wrote a PC application called Funkii-UI that was once mildly popular. I had a version that I never released that resumes partial downloads just fine using the method I described. I tested it hundreds of times and even had other users test it more times than I could remember. Never had it fail, not even once.
To be honest it had hiccups when I tested it but NUSspli was in alpha state back then, so it might have been some other (memory corrupting?) issue. Anyway, the largest single file I saw was 1,28 GB and that was with a title around 18 GB in size, so not continuing a single file shoudn't be that bad? Will have a fresh look into it soon anyway but there are more important things on my todo list.I had a version that I never released that resumes partial downloads just fine using the method I described. I tested it hundreds of times and even had other users test it more times than I could remember. Never had it fail, not even once.