We left off at the point of.. finding a suitable allied base for moving, so we will do that now: Be aware that if expecting to code more than one base in the general area it will be necessary to use an available Griddata address.Often there is not many available uncoded data locations.So if another base is to be in the area it is wise to make a base selection based on T-codes that will allow numerical sequencing for the Griddata.dat. Also, the formerly coded default Griddata address for the bases will have to be removed.It is easier to do so if the bases already occur at a single Griddata, it pays to do a little investigation. Using the HillGmap.jpg is convenient also.Often bases that are located closely together will be coded at a single Griddata address.
![]() A lot of the close UK bases are sequential. Here I checked the above and the ABTGList.rtf then compared with the EAWK3wdb.html and found that Rattlesden - (231) and Knettishall - (141) are both sequential and coded at address1688 in Griddata.
![]() Rattlesden is T-code; 42 and Knettishall T-code; 43 All I have to do is "zero" the default data here
Now to place them in Griddata: In Page 1 of the tutorial I already checked the x , y in the EAW World location for placement of one base at Column 580 , Line 65 with the Vertcon program.
![]() Yes, I'm luck! It can use address 1576
The newly coded Griddata Now to the Targets.dat to change the x , y EAW World location data:
Shown here: Rattlesden's default Targets.dat data at jump 2112
Now I set the new EAW World location data for Rattlesden taken from Vertcon
After doing the same process for Knettishall Now to test this out:
Place the newly made Targets.dat , Griddata.dat , and Frntline.dat in EAW.
This is the new "Tutorial Mission" - I selected Rattlesden to take off from on a sweep to Berlin
Well its about time to continue this on Page 3.. |