Isn't there a setting to make any base have available all aircraft from the airfield? the bits I think would correspond to 512 from what I recall?

runways.dat
To make the use of 32 airfield runway types
is now possible to use the new airfields you need to use the newer runways.dat

and to have additonal runways displayed in game you would need to add airfld.3dz files for the runways you make

runways.dat changes:

The runwways.dat differences are mainly the addition of a 'shadow record' in the first entry of runways.dat to use for carriers, and then the addition of some 28 records at the end of the noraml default records.

to compare the 1.2 default to the new I make some pics available;

this pic shows the first record and the new header pointer which is 20h instead 0Bh meaing there are now 20h (32 in decimal) records in the file instead of 0Bh (11 decimal)

i this example the 1.28B ruways.dat on left compared to the 1.2 default on the right

the second shows the end of the file, on the right the old 1.2 default end of record and left with hexeditor highlighting the last byte in the new file where the old data last byte occurs

to use the new and combine with an old runways.dat you have customed you can see what you would need to add with a hex editor, use the new first record and header and then at the end tack on all the extra bytes of data
or simply paste your current data into the new in the proper area

Take note that this is only the 1.28b release runways.dat shown here, later ones, or those used by customized campaigns like SPAW, etc. may differ in the data


--
1.28a and on
Again not all changes recorded here yet 1/2010

in additon to the runways.dat described above..

1.28a and (by inheritence later .exes that may use the same data.cdf conating the .dats) have change to the targets.dat, tardata.dat, griddata.dat and airfield.dat files

The main change is due to the editing of Mr Jelly who added an extra base to targets.dat and airfield record to airfiled.dat as well as corresponding griddata changes, and a change of tardata.dat record locations pointed to from targets.dat

I only realized this recently so am only noting it now

The only part I document here is only the changes to targets.dat records pointers -
is found out by using my 2datscheck.exe program, which scans a targets.dat and airfield.dat file and makes a text file record output for the data from the 2 files to compare.
the comparison of the targets.dat and pointers in 1.28a (1.28b shown but the changes started in 1.28a and later) vs those of the 1.28 which had no such changes but adhered to the default 1.2 schema are shown in my pics here.

on the left in the pictures you see the 1.28b data and on right the 1.28 standard data

(My program uses a zero based offset to show here meaning the records start from 0 a 1 based offset shown in parenthesis() )
Except for the pointers to tardata.dat are different all is same until:
The first change you notice is at record #120 (121) things have changed, some records shifted around, so be aware of it
--




--
next you see major change at record #127 (128) a base was added with a new Acode
--
(2 more pics not shown here)
--
the effects of this are:
- a new base record which means the total number of bases is increased by 1 and so the targets.dat contains an extra record

- all bases afterwards are shifted in the records by increase of 1

- a new airfield.dat record and thus the airfield. dat since 1.28a has an extra record in it



- This makes it a inconvent for modders to try to use old data with the new, If you use my old tools or old documents you have to take the changes and data shift into account

- Also it means if you use a scenario / mission / campaign you cannot mix and match files
you would need targets.dat, tardata.dat, airfield.dat, griddata.dat all matching or you will get errors, ctds

- The possible effects on campaigns is unknown at this time