ssokolow: These large sizes always irritate me because:

1. If the game is bigger than 4.4GiB, the first pieces don't neatly fit on a DVD+R like the old ~1.46GiB pieces did, so it's harder to pack the DVDs full while still being able to pack them in a way that makes them easy to file and flip through. (I have nearly 450 DVD+Rs full of GOG/Humble/Desura/etc. content)

2. They're more likely to fail before completion on a shaky connection. (My connection usually isn't shaky, but I do live in the countryside without the ability to upgrade beyond 5Mbit DSL)

3. Given that you've got a split point anyway, why not split at a low enough point that we don't have to use NTFS or UDF on our removable media when FAT32 and ISO9660 can handle the old 1.5GiB split point perfectly well?

skeletonbow: They've intentionally split up all of the games to fit within files 2GB or less before. I doubt they've changed that policy as nothing has changed on the user side to lower the importance of it so I assume that all that stuff is done by human hands and subject to human error rather than going through an automated process that tests things etc. It's probably one that just got through the cracks because someone was in a hurry to get home and play The Witcher 3. :)

rmyers: [..]I never could fit three of them on any DVD[..]In terms of FAT32, a 2 GiB size would work just as well [..]

phaolo: Fat32,DVDs.. those things are even older than my Win xp :P

rmyers: "1. If the game is bigger than 4.4GiB, the first pieces don't neatly fit on a DVD+R like the old ~1.46GiB pieces did, so it's harder to pack the DVDs full while still being able to pack them in a way that makes them easy to file and flip through. (I have nearly 450 DVD+Rs full of GOG/Humble/Desura/etc. content)"

I don't understand. The old pieces were about 1.5 GiB. I never could fit three of them on any DVD, neither +R nor -R. So I was always left with about 1.36 GiB of unused space on every DVD. Now with the new size, which are about 3.95 GiB, I'm only loosing 0.41 GiB per DVD. So I like it a lot better.

Were you ever able to actually fit three 1.5 GiB pieces on a single DVD? All mine are limited to 4.36 GiB.

In terms of FAT32, a 2 GiB size would work just as well for me as a 4 GiB size. Perhaps the best of both worlds.

BTW, if you'd like to split them up differently, pack all the pieces into a .zip file (just stored, not compressed.) Then use a freeware program like GSPLIT to split them up any way you like. Of course, that won't work if your using a file system like FAT32 that's limited to 2 GiB file sizes.

phaolo: Fat32,DVDs.. those things are even older than my Win xp :P

ssokolow: I fit them all the time. In fact, they fit perfectly on a DVD+R with only a hair to spare when I ask K3b to burn the default ISO+Joliet+RockRidge filesystem. (ISO9660 with DOS 8.3, Microsoft, and UNIX/Linux filenames and metadata)

I'm assuming something about your burning tool's default settings adds extra filesystem overhead. (Maybe it defaults to a hybrid ISO+UDF filesystem and the extra UDF overhead is too much?)

As for splitting them up differently, I don't even need to do that. There are free Linux tools which will just chop the raw bytes of the file so that all you need to do to recombine them is concatenate them with `cat piece1 piece2 > name_for_new_whole_file`. I prefer not to chop my files that way.

(Though I do repack the Linux tarballs using split 7zip with 4482 MiB volumes)

flashpulse: That little blue dot is easy to look over in the library. I had to come here to see what was updated.

ssokolow: [..]If I'm going to be storing terabytes of data, I want the ability to replace the drive mechanisms independent of replacing the data surface. Optical discs give me that. External hard drives don't. Hopefully, by the time the stock of good-quality BD-Rs starts to dry up, I'll have the funds to afford a suitably large RAID-10 NAS unit and some spare drives)

IAmSinistar: Wow, no joke. This is the first time I've noticed one, and I really had to hunt. Would really like them to turn the notification system back on instead.