ATF: kbDataModern Custom Database --- New Release

[kbluck]

As promised, I have jiggered the kbDataModern database to line up with corresponding units in database1, so it should import into stock scenarios properly now. However, I've found the scenario builder frequently (but not always) crashes when doing so. I'll see if I can squeeze them out.

http://www.wargames.warfarehq.com/forums/showthread.php?t=301

--- Kevin

[jdeluise]

If I asked really nice, could you rebuild your kbDVA scenario with the new database some day? :) That one is much more enjoyable than the stock version of DVA, but I want to update to your new database, so I can modify NTC2:Hidden Valley Attack and see how my infantry does now:)

[kbluck]

If I asked really nice, could you rebuild your kbDVA scenario with the new database some day? :) That one is much more enjoyable than the stock version of DVA, but I want to update to your new database, so I can modify NTC2:Hidden Valley Attack and see how my infantry does now:)


Well, I can rebuild it using a old copy of the kbDataModern DB. It won't be the "new" DB, but it should play as before, and you'll be able to install the new database without affecting it.

Download available from the archives:

http://www.wargames.warfarehq.com/forums/showthread.php?t=201

Actually, I'm interested to hear what you like about it (and what you don't) since this was my first real effort at scenario modification.

BTW, there is no need for you to do anything to NTC2 yourself. I've done it for you already, and the other 13 stock scenarios as well. Download here:

http://www.wargames.warfarehq.com/forums/showthread.php?t=302

--- Kevin

[CommC]

I have made a few modifications to the database1, editing a few pKs, and saved it to a new name. However, whenever I try to import this into a scenario, the scenario builder program crashes to desktop.

I am using v1.03 with Win XP.

Any suggestions?

[Pat Proctor]

First, I would try to download the sneak preview version 1.04. Then,

1. Select "New" from the "Database" menu in the Power Toolkit.
2. Select "Edit" from the "Database" menu and manually designate each of the files in the database.
3. Select "Save As" from the "Database" menu and save your database with a new name.

Let me know if this doesn't do it.

[kbluck]

I've never had good luck importing new databases into existing scenarios. 99 times out of 100, it throws a protection fault and crashes. (I say that because it actually worked, once only.) Version 1.04 does not seem to have improved the situation. I finally resorted to hacking the scenario files directly with a hex editor, with good results.

If you are comfortable performing the digital equivalent of transplant surgery, here is the procedure. You need a hex editor. WinHex is a good one. Text editors won't work, because the files have a lot of non-binary values, in particular null bytes. Notepad, for example, will thoroughly screw up your files. If you don't know what a "hex editor" or "null byte" is, or how to count in hexadecimal, you'd better stop right now.

You'll notice text strings are embedded in the various files. Each string is preceded by a length byte. For example, if you notice a reference to the file "database1.dbs", you'll see that the byte immediately preceding the filename is set to "0D", since the filename is 13 characters long. The key to success is that if you change the length of a string, you must change that length byte to match. For example, when I changed 'database1.dbs' to 'kbDataModern.dbs', which is three characters longer, I had to change that byte to '10'.

To "import" a database, you'll need to edit up to four scenario files: the *.asc file, which has five references to all five database files, and either two or three *.unt files, which each have one reference to the database's *.dbs file only. Change the strings to match your desired new database files, edit their length bytes to match, and save everything. Check your work by opening the scenario in the Scenario Builder. It will open without complaint if you've done everything correctly. It will die horribly if you haven't.

Every scenario I've "converted" has been done this way. There seems to be no obvious ill effects. Of course, I'd prefer to use the intended tool for its intended purpose, but what else can you do when it just won't work?

--- Kevin

[CommC]

I followed your instructions, Pat, regarding creating the modified database, but it still didn't work, same problem with the editor crashing upon the import.

I still haven't tried the hex editing method.

Thanks.

[CommC]

OK, I have tried the hex editing route and that seems to be working. Thanks kbluck. To help keep this simple, I make sure my new database name has the same number of characters as the original database1 name.

With the edited database, this sim is shaping up nicely. I recently upgraded my computer, so I have pulled ATF off the shelf, since it didn't run well on my old computer.