This is coming in the next version. Incremental patches (vs. the current "direct patches") will make sure the updates are tiny and the uploads are tiny. The only downside to "incremental patches" is that a customer running a really old version of your software will have to download every update that came between their version all the way to the newest version (which may or may not be the best default behavior for you).
Feedback: Smaller updates needed!
spacejimI've been using wyUpdate for about a year now, and my game updates are really piling up!
Despite deleting a lot of my past versions (leaving them to the "catch-all" update at 700mb), I have 25 different *.wyu files to upload, averaging over 100mb each, totaling about 2.5gb.
This means, if I do a couple of bug fixes, and recompile just the games main .exe file (5mb), I have to rebuild everything in wyupdate, and then upload 2.5gb of files to the server. Thats a 2.5gb upload just so I can update a 5mb file. And this is going to keep getting worse as I make regular updates.
There needs to be a cut-off point somewhere, some way wyBuild can just keep all the old .wyu files already on the server and start fresh with new updates, so that on the user-side it will download say 2 or more .wyu update files as needed. Some way that I can go "Look wyBuild, I'm just changing this one file ok?" and wyBuild will build it in a flash and only need to upload that 5mb worth of data, and then I can get on with working.
spacejimThat would be good indeed. Theoretically, if the patches are all downloaded and installed automatically the customer shouldn't notice the difference, right?
Right -- it's just a design tradeoff you need to be aware of.