falcon4:database
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
falcon4:database [2008-05-09 01:52] snakeman added addvehicle_tutorial link |
falcon4:database [2010-07-27 16:00] snakeman added ff55database link. |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| [[falcon4:database:sp42database|SP4.2 Database]] - list of bunch of items in database like squadrons and battalions. | [[falcon4:database:sp42database|SP4.2 Database]] - list of bunch of items in database like squadrons and battalions. | ||
| + | |||
| + | [[falcon4:database:ff55database|FreeFalcon 5.5 Database]] | ||
| + | |||
| ====== Background ====== | ====== 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 | + | 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 the terrdata\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. | [[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. | + | The F4Browse measurements are in for example fuel: **lbs**, range: **nautical miles** values (note most of all ranges in F4browse refer to Km distances for VCD, WCD etc and in feet for radar (RCD) and all dat files of simdata.zip ). 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 ====== | ====== Adding, Deleting and Editing ====== | ||
| Line 21: | Line 25: | ||
| Read Jerry "Pookie" Davis written [[addvehicle_tutorial|Adding new vehicles to the TE and Dogfight modules 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 ====== | ====== 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. | + | 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 aircraft's, 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:\\ | This example shows you how to copy F-4E SK squadron:\\ | ||
| Line 34: | Line 41: | ||
| * edit 522, change SSD Ind to new SSD number, update | * 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. | * 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 ====== | ====== Rack.dat explanation ====== | ||
| Line 41: | Line 49: | ||
| The new rack specification. This is defined through the rack.dat file. This file specifies two things. | 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 | * 1) RackGroups - these are groups of common rack definitions | ||
| - | * 2) Racks - this sepcifies an individual rakc, its capacity and visual | + | * 2) Racks - this specifies an individual rack, its capacity and visual |
| ====== Rack Groups ====== | ====== Rack Groups ====== | ||
| Line 52: | Line 61: | ||
| which says rack group 0 contains racks 0, 1 and 2. | which says rack group 0 contains racks 0, 1 and 2. | ||
| - | ====== Rack Defintions ====== | + | |
| + | ====== Rack Definitions ====== | ||
| These define the individual racks, from 0 to N, where again N is defined in the rack.dat file. | These define the individual racks, from 0 to N, where again N is defined in the rack.dat file. | ||
| Line 62: | Line 72: | ||
| Rack1 1982 1 # helo one rack | 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. | + | Having defined all the available racks and rack groups, 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 rack group 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. | + | Then, in the aircraft.dat file, the hard point specifies the rack group that this hard point can carry. So, for instance, and F-16 might specify hard point 7 has rack group 1, which in turn says racks 3 4 5 and 6 can be attached to this hard point. |
| - | 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.\\ | + | Now - all that has to happen is for a the weapon and hard point to be matched up. So, say we wish to load a 2 mavericks on a F-16 hard point 7. We find the rack group for hard point 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\\ | So, the chosen rack must be\\ | ||
| - | a) part of the rackgroup for HP7\\ | + | a) part of the rack group for HP7\\ |
| - | b) part of the rackgroup for maverick\\ | + | b) part of the rack group for maverick\\ |
| c) allow 2 or more weapons to be carried.\\ | c) allow 2 or more weapons to be carried.\\ | ||
falcon4/database.txt · Last modified: 2016-11-05 19:52 by snakeman
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
