PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Database ======

Falcon 4 Database Editing (<THEATER>\objects dir or terrdata\objects for Korea).

[[falcon4:database:files|Object files]] - descriptions and functions.

Creating and Editing [[falcon4:database:airbases|Airbases]]

[[falcon4:database:sp42database|SP4.2 Database]] - list of bunch of items in database like squadrons and battalions.

====== Background ======

The Falcon 4 database is edited with [[falcon4:tools:f4browse|F4Browse]] by Julian "Codec" Onions, you can always download the latest from our [[http://tactical.nekromantix.com/f4/downloads.php|downloads]] page. Using this program you can access pretty much all the database stuff in theterrdata\objects directory. New theaters use their own objects directories, for example [[http://tactical.nekromantix.com/f4/desertstorm.php|ODS]] uses "Theaters\DesertStorm\objects", [[http://tactical.nekromantix.com/f4/vietnam.php|Vietnam]] uses "Theaters\Vietnam\objects" and finally 
[[http://tactical.nekromantix.com/f4/europe.php|Europe]] uses "Theaters\Europe\objects" directory.

The F4Browse measurements are in for example fuel: **lbs**, range: **nautical miles** values. In the view option you cannot see measurements, also F4Browse view is mirror image of real world. There is export and import function in F4Browse which you can use the transfer individual edits in and out of the database you are working on with someone. Just make sure that when you're importing stuff in, its correctly edited, always make backups of the original database you're creating so if wrong data is imported, you can revert back to the "working" database.


====== Adding, Deleting and Editing ======

Read ranger822's [[falcon4:database:editingtutorial|Database Adding, Deleting and Editing]] tutorial.

Read Jerry "Pookie" Davis written [[addvehicle_tutorial|Adding new vehicles to the TE and Dogfight modules tutorial]].

Read [[falcon4:database:addweapon_tutorial|How to add a new weapon]] tutorial by Dragon.

====== Adding Aircraft Copy ======

Here is example of how to add new CT record of aircraft squadron so you can use both the old squadron and this new edited squadron you just made. For example if you want to have one theater but with two time periods like Desert Storm. 1991 ODS and present day Black Phoenix. Both used the F-16 aircrafts, but in ODS they didn't have AIM-120's or LGB's which Black Phoenix has. 

This example shows you how to copy F-4E SK squadron:\\
  * units -> f4esk -> add copy, update [record UCD number, call it U] 
  * classtable -> no354 -> add copy, change File offset to unit number [U], update note CT number of this new one, call it [C] 
  * back to unit view, reedit new unit, change CT Ind to [C], Update 
  * bring up dialog for Unit [U], look for SSD record number 
  * go to SSD view, and copy SSD used by [U]. remember the new SSD number 
  * edit 522, change SSD Ind to new SSD number, update 
  * edit 522 again, click on SSD Ind button should see the SSD record click on used by - should see just used by one squadron.

====== Rack.dat explanation ======

Here is what I have. Shawn is the expert now though :-)

The new rack specification. This is defined through the rack.dat file. This file specifies two things. 
  * 1) RackGroups - these are groups of common rack definitions
  * 2) Racks - this sepcifies an individual rakc, its capacity and visual

====== Rack Groups ======

These are number from 0 to N, N being specified in the file as the maximum number currently defined. The specification is\\
Group [n] [racks]\\
as in\\
Group0 0 1 2\\
Group1 3 4 5 6\\
which says rack group 0 contains racks 0, 1 and 2.

====== Rack Defintions ======

These define the individual racks, from 0 to N, where again N is defined in the rack.dat file. 

The specification is\\
Rack [n] [CTid] [MaxCount]\\
as in\\
Rack0 0 0\\
Rack1 1982 1 # helo one rack

Having defined all the avilable racks and rackgroups, then it is time to match them up. This is done in the following way. In the weapon file, a new field (well an old one that wasn't used) is used to specify the rack group for this weapon. Through this, you can specify all the racks that can potentially carry the weapon. E.g., in the above, if the rackgroup was 0, then the weapon could potentially be carried on any of racks 0, 1 or 2. 

Then, in the aircraft.dat file, the hardpoint specifies the rack group that this hardpoint can carry. So, for instance, and F-16 might specify hardpoint 7 has rackgroup 1, which in turn says racks 3 4 5 and 6 can be attached to this hardpoint. 

Now - all that has to happen is for a the weapon and hardpoint to be matched up. So, say we wish to load a 2 mavericks on a F-16 hardpoint 7. We find the rackgroup for hardpoint 7, we find the rack group for the maverick, and then we go through the list of racks in each looking for the first match with enough capacity to carry the given load of weapons.\\
So, the chosen rack must be\\
a) part of the rackgroup for HP7\\
b) part of the rackgroup for maverick\\
c) allow 2 or more weapons to be carried.\\

Julian. 

This tutorial is under work and we will be adding more stuff to it. Send info/comments to [[http://tactical.nekromantix.com/forum/|our forum]].
PMC Editing Wiki

User Tools

Site Tools

Page Tools
