We thought about switching over to the ZIP format for C4Groups, but wouldn't it be better just to drop packed groups?
+ We already have the code for handling unpacked groups.
+ Resource loading over network would be more efficient because only changed files would need to be loaded.
+ We cannot pack subfolders in a zip group without losing random access, so we would have to add an implementation just for that parent group.
+ For the sake of compatibility, we could modify C4Group in order to unpack packed groups permanently.
+ Pretty all developers unpack their files to develop and pack them to publish them in order to keep the engine from going crazy.
+ We already have the code for handling unpacked groups.
+ Resource loading over network would be more efficient because only changed files would need to be loaded.
+ We cannot pack subfolders in a zip group without losing random access, so we would have to add an implementation just for that parent group.
+ For the sake of compatibility, we could modify C4Group in order to unpack packed groups permanently.
+ Pretty all developers unpack their files to develop and pack them to publish them in order to keep the engine from going crazy.
>+ Resource loading over network would be more efficient because only changed files would need to be loaded.
How do you find changed files?
>+ Pretty all developers unpack their files to develop and pack them to publish them in order to keep the engine from going crazy.
And in order to upload them somewhere. If you want to put them online, you would have to pack pack them anyway
IIRC, windows was pretty slow with loading hundreds of files from diskā¦
When you have single files, you cannot guarantee that they are saved in adjacent sectors on a HDD, which can make loading pretty slow, because the HDD has to jump around quite a bit. So even if we dropped the compression, we might want to continue .tar-ing the files or something..
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill