 |
Should the BIC files be compressed?
This poll is closed. |
| Yes, compress them. They are too big for my tastes. |
   |
11 |
13.10% |
| No, they're fine the way they are. |
   |
53 |
63.10% |
| I don't know and/or I don't care. |
   |
20 |
23.81% |
| Total: |
84 voters |
100% |
|
|  |
 |
|
Mike Breitkreutz FIRAXIS
|
|
Hunt Valley, MD
May 2001 time: 00:19
|
|
Does anyone think the BIC files are too large? Does anyone want the BIC files to be compressed (in the same manner as the saved games)? Or are you all happy with the size of BIC files?
|
|
|  |
 |
|
Bane Star
|
 |
Adelaide, Australia
Sep 2000 time: 14:49
|
|
Lol, doubt it, If the save file is less than a 1.4 floppy, who cares, If they take longer to save and load, then NO dont do it, and If it makes it hard to change them with an editor, then Definately NO dont do it, But the average computer that'd requires to Run the game has at least a 5Gb H.D.D. So whats 1Mg when it comes down to it
(I have 2x30Gb HDD at 10K Rpms so I dont care if the file is 5Mg per save, just as long as its fats to load and save and editable)
|
|
|  |
 |
|
Gelvan
|
|
Switzerland
Nov 2001 time: 06:19
|
|
How many people have a PC which meets the requirements and don't have Gigabyte Harddisks? I don't know it really, but I suppose most people have enough hard disk space. And for sending it around the web, they can be zipped easily. So I don't think it's a good idea to compress them, makes tools more difficult to produce and use and will entail longer loading times.
And I agree, that there should be an option available for NOT saving SAV's together with the BIC of this SAV, because this is a real pain for creating scenarios/mods. (intrduced with 1.21 for unknown reason?)
|
|
|  |
 |
|
Gelvan
|
|
Switzerland
Nov 2001 time: 06:19
|
|
well, because I'm in modding right now, I reload quite often. And I restart a game even more often, because this unwanted SAV/BIC-Problem, introduced with 1.21.
I know I'm a bit repetetive on this, but it's really annyoing. Why did you do this? The Multiplayer-Community is surely not as big as the Modmaker-Community, and they rely on "modcom" Maps and Mod's anyway. So if you want to make most customer's happy, only change things which are really wanted.
Which leads us to another repetitive task: the minimap. I'm 100% sure, that there are more people waiting and hoping for this one, than for compressed sav or bic files.
|
|
|  |
 |
|
kring
|
 |
Wichita,KS,USA
Dec 2001 time: 23:19
|
|
quote: Originally posted by Adm.Naismith
Ok, compressed save files don't slow down my system, so I like more a directory of smaller files without the need for frequent delete of files. You can't have enough space for long, you GigaOwner so better reduced size than sorry.
Loading time slowdown? Come on, how often do you reload your save game? Is it really a great problem? 
I spend more time using my PC with its always full disk than reloading save game.
About compressed BIC, I suppose that any good programmer can cope with a know, easily available compression schema, as PKWARE library IIRC.
I prefer a "ready to transfer/store" file than a bloated "quick to read", long time spent deleting/defragmenting an HD. |
I appear to be in the minority vote, but I say either compress them or GIVE the option to have compress/noncompress.
As others have pointed out, many people don't have the extra HD space, and yes some files are already 600k+ in size. Why should these people have to buy floppy disks to keep them on?
When I bought my 20 GB HD system, I was led to believe it would take a long time to fill it up. That may be true if you don't buy a decent number of PC games. Shogun TW/WE easily takes over 1 GB of memory. I am down to just over 6 GB, and have NOT loaded Shogun or several other new games I have bought.
Speaking as a GigaOwner, I say either compress or give the option to decide compress/noncompress.
What too many people voting no don't realize is that many people CAN'T either: upgrade memory and/or buy a new computer. I visit about a dozen Civ3 sites on a regular basis, and many of the people I have talked with are running the game on a system that is barely capable of holding the game as it is. They have opted to buy games, instead of upgrade their systems.
Hopefully, the CD case will give accurate information on how much space is required to install the game, since the CD said 400 MB, and the game when to be installed said 500+ MB.
|
|
|  |
 |
|
FrantzX
|
|
What is you included the civlopedia and/or the diplomancy text files in the bic? That you be one less file to back up/copy when playing mods/scenarioes an would give a goo reason for bic compression.
|
|
|  |
 |
|
wervdon
|
|
Why don't you just do what zsnes does and have the game able to look inside of any .zip file it sees in its directory and grab bic files out of them for use.
|
|
|  |
 |
|
Mike Breitkreutz FIRAXIS
|
|
Hunt Valley, MD
May 2001 time: 00:19
|
|
Since many people have asked, here are the reasons for and effects of, compressing BIC files:
Compressing BIC files will make them smaller. This is really the only reason to compress them.
Loading and saving a compressed BIC file will take slightly longer but it will not change the time it takes to load saved games. Also, the speed decrease caused by compressing the BIC files will not be as much as compressing the saved files (uncompressed saves are larger than uncompressed BIC files which means compression takes longer on saves). Most likely, the speed difference between compressed and uncompressed BIC files will not be noticeable since they are not be loaded during gameplay.
Compressed BIC files will be more difficult to modify outside of Civ3Edit -- the many tools that exist that modify BICs will have to have the compression algorithm built into them. However, the algorithm will be identical to that used in saved games so it wouldn't be impossible to add it to the tools (especially for Gramphos' and jimmyh's tools since they have already handled the compression in their saved game editors).
|
|
|  |
 |
|
The Viceroy
|
 |
tu mumbai se, mai Bombay se
Nov 2000 time: 05:19
|
|
It would be more work to include the option certainly .. but how much more work, depends on the setup of the code ..
If you want to add compression (no options) all you have to do is slap on the compression algorithm to the existing Load & Save options .. no so complicated if the algorithm already exists ..
To add the option, would mean a re-build of the GUI , additional functions to handle the on/off state, additional variable to remember the state, and then you can add the compression algorithm in the load/save IF the var says the user has selected compression.
of course, personally, id opt for the save box to have a compress option, but the load to auto detect from the BIC file if it is compressed or not .. cos at least then you can load either, regardless of the user selecting compress, and you don't need to bother with an additional member variable\functions holding Compression status ..
|
|
|  |
All times are GMT. The time now is 05:19. Apolyton Time is 00:19. |
top of page
|
|
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|