- NOTE: Due to a timestamp check, the following unpacked files will
cause the game to crash and must be deleted before the game is
launched:
data\descr_geography_new.txt
data\descr_geography_new.db
advice is given in various places including the closed stickie about the use of the unpacker
http://www.twcenter.net/forums/showt...50#post1679750
however, it's actually been known for a few years that you can retain (and even modify the geography files) if you add
Code:
[misc]
rebuild_geography_db = true
to the .cfg file used to run the game/mod
that then causes the _db file to be rebuilt from the .txt file each time the game launches, which gets round the time stamp issue and allows modded descr_geography_new.txt files to be used to make changes to battlemap textures, vegetation quantity and hilliness etc.
#############################################################
UPDATE:
from the end result of this thread;
http://www.twcenter.net/forums/showt...9#post12568729
it looks like the rebuild process can overload memory/texture space when the campaign is launched later. Revised recommendation in the light of that is use the "rebuild_geography_db = true" process when you're deliberately modding the geography file only. The rest of the time, re-name the descr_geography_new.txt
file so it's not used. Keep descr_geography_new.db in your modfolder, if you're running an amended one. And remove the "rebuild_geography_db = true" chunk from your .cfg (or it will try and regenerate the db from the .txt file in the Packs).
Battles should be fine with a revised .db in the modfolder and without the rebuild process in .cfg so long as the text file is removed/re-named.