User Tools

Site Tools


falcon4:database:editingtutorial

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
falcon4:database:editingtutorial [2008-12-23 23:36]
snakeman fixed typos.
falcon4:database:editingtutorial [2017-10-06 14:23] (current)
snakeman http to https switch.
Line 30: Line 30:
 -File -> Open Model File... -File -> Open Model File...
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_1.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_1.jpg }}
  
 Browser to your finished model and open it. Browser to your finished model and open it.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_2.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_2.jpg }}
  
 You will see this screen below next, play special attention to the detail highlighted in the red block. ​ It is a good idea to write this info down on a separate piece of paper or in Notepad/​Wordpad. ​ This is basically telling you what the last known numbers in the database are and it makes it easier to locate your new entry later as you go along. You will see this screen below next, play special attention to the detail highlighted in the red block. ​ It is a good idea to write this info down on a separate piece of paper or in Notepad/​Wordpad. ​ This is basically telling you what the last known numbers in the database are and it makes it easier to locate your new entry later as you go along.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_3.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_3.jpg }}
  
 Now, click on th **Edit LOD** button and you will see a screen similar to the one below. ​ Under **Utilities** choose **Model/​Texture SetUp** Now, click on th **Edit LOD** button and you will see a screen similar to the one below. ​ Under **Utilities** choose **Model/​Texture SetUp**
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_4.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_4.jpg }}
  
 The next screen you see you need to follow these simple steps: The next screen you see you need to follow these simple steps:
Line 50: Line 50:
 - Then click on **OK** - Then click on **OK**
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_5.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_5.jpg }}
  
 Now do the same for the **Append/​Select LOD** the menu will ask you to locate the LOD file of your model on your hard drive and after that some distance view information. ​ I am not sure what these numbers really mean so I follow Maddog'​s advice and type in the number 10000 and click **OK** Now do the same for the **Append/​Select LOD** the menu will ask you to locate the LOD file of your model on your hard drive and after that some distance view information. ​ I am not sure what these numbers really mean so I follow Maddog'​s advice and type in the number 10000 and click **OK**
Line 56: Line 56:
 The distance data can be changed after wards anyway, so don't worry too much about that for now. The distance data can be changed after wards anyway, so don't worry too much about that for now.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_6.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_6.jpg }}
  
 Now click on **Update Parent Record**\\ Now click on **Update Parent Record**\\
Line 70: Line 70:
 In F4Browse go down to Vehicle folder and click on it to open the sub folders and then click on Aircraft. ​ Now find and existing aircraft that best matches the new aircraft you want to add.  In Maddog'​s example he selected a Mirage -IIIE as his template because he was adding a Mirage IIIR2Z which is quite similar. ​ The selection should try to match up an existing aircraft that is closes in role, performance,​ etc since it is entirely likely that parts of a/c data entries can be used with less modification. ​ So, Right click on the list listing and choose **Add Copy** In F4Browse go down to Vehicle folder and click on it to open the sub folders and then click on Aircraft. ​ Now find and existing aircraft that best matches the new aircraft you want to add.  In Maddog'​s example he selected a Mirage -IIIE as his template because he was adding a Mirage IIIR2Z which is quite similar. ​ The selection should try to match up an existing aircraft that is closes in role, performance,​ etc since it is entirely likely that parts of a/c data entries can be used with less modification. ​ So, Right click on the list listing and choose **Add Copy**
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_7.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_7.jpg }}
  
 The new entry will be copied to the bottom of the a/c list.  So, scroll down to the bottom and locate your copied template The new entry will be copied to the bottom of the a/c list.  So, scroll down to the bottom and locate your copied template
Line 79: Line 79:
 - Click on **Update** - Click on **Update**
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_8.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_8.jpg }}
  
 - Click on Class Table on the left, sort the list by No, then locate the CT Ref No of the template that you copied, in this example it is entry 2500.\\ - Click on Class Table on the left, sort the list by No, then locate the CT Ref No of the template that you copied, in this example it is entry 2500.\\
 - Right click and **Add Copy**. - Right click and **Add Copy**.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_9.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_9.jpg }}
  
 - You new entry will be added, as always to the bottom of the Class Table list so scroll down and locate it\\ - You new entry will be added, as always to the bottom of the Class Table list so scroll down and locate it\\
 - Double click to edit your new CT entry - Double click to edit your new CT entry
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_10.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_10.jpg }}
  
 - Write down the new **CT Ref No** (in this example 3508)\\ - Write down the new **CT Ref No** (in this example 3508)\\
Line 97: Line 97:
 - Locate your new model and double click to edit it again. - Locate your new model and double click to edit it again.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_11.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_11.jpg }}
  
 - In the CT Recd box enter the CT Ref No you just created in the step before (in this example is was 3508).\\ - In the CT Recd box enter the CT Ref No you just created in the step before (in this example is was 3508).\\
Line 111: Line 111:
 - This is where those who did not write things down will panic. ​ In Part 1 of this tutorial, when you added the new LOD you needed write down the new LOD number and Parent ID number. ​ Remember the screen see pic below. - This is where those who did not write things down will panic. ​ In Part 1 of this tutorial, when you added the new LOD you needed write down the new LOD number and Parent ID number. ​ Remember the screen see pic below.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_12.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_12.jpg }}
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_13.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_13.jpg }}
  
 In the screen below we have changed the template Parent ID to my new Parent ID (3800_ which contains the reference to the actual LOD model. In the screen below we have changed the template Parent ID to my new Parent ID (3800_ which contains the reference to the actual LOD model.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_14.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_14.jpg }}
  
 If you click on the **Normal** button in the Parent Box (screen above) you will see it takes you to your LOD file you added in Part 1 (in this example it is 6433). ​ You should not have to change anything here. If you click on the **Normal** button in the Parent Box (screen above) you will see it takes you to your LOD file you added in Part 1 (in this example it is 6433). ​ You should not have to change anything here.
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_15.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_15.jpg }}
  
 That is basically it for adding a model to the database. ​ If you click on the **3d Viewer** you should be able to view your model. ​ Now that you have added the model to the database lets move to Part 4 which will discuss how to get your model to actually fly. That is basically it for adding a model to the database. ​ If you click on the **3d Viewer** you should be able to view your model. ​ Now that you have added the model to the database lets move to Part 4 which will discuss how to get your model to actually fly.
Line 132: Line 132:
 First fire up F4Browse again - - Click on the CT Tree and scroll down to the Vehicles >>>>​Aircraft tab again. ​ Locate Maddog'​s Mirage IIIE which he used for his example. ​ Open the Mirage IIIE record and you will notice the **Units with this** box on the right side of the Vehicle Data Details window. ​ You will see two Units identified as Fighter 501 and Fighter 500.  These are the unit flight and unit squadron First fire up F4Browse again - - Click on the CT Tree and scroll down to the Vehicles >>>>​Aircraft tab again. ​ Locate Maddog'​s Mirage IIIE which he used for his example. ​ Open the Mirage IIIE record and you will notice the **Units with this** box on the right side of the Vehicle Data Details window. ​ You will see two Units identified as Fighter 501 and Fighter 500.  These are the unit flight and unit squadron
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_16.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_16.jpg }}
  
 - Double Click on each of these Units in turn.  When you do you will notice it will bring up the Unit View window. ​ In the upper left corner you will see the CT Index (CT Ind) and then a window with a number. ​ This is the CT Index for the unit.  Write this number down (in this example the Fighter 501 = CT2668, and Fighter 500 = CT2667).  ​ - Double Click on each of these Units in turn.  When you do you will notice it will bring up the Unit View window. ​ In the upper left corner you will see the CT Index (CT Ind) and then a window with a number. ​ This is the CT Index for the unit.  Write this number down (in this example the Fighter 501 = CT2668, and Fighter 500 = CT2667).  ​
  
-{{ http://tactical.nekromantix.com/images/wiki/​DB_Tut_17.jpg }}+{{ https://pmc.editing.wiki/​images/​DB_Tut_17.jpg }}
  
 - Now close the Unit View Window and go to the CT Tree view and click on the top of the tree **Class Table**, when you do it will sort the CT list numerically from lowest to highest.\\ - Now close the Unit View Window and go to the CT Tree view and click on the top of the tree **Class Table**, when you do it will sort the CT list numerically from lowest to highest.\\
Line 166: Line 166:
  
 Now that we have successfully added a new vehicle entity and the two required unit entities lets dig into the the other parts of database editing that will now make the new vehicle entity perform uniquely. ​ You might recall that when you did your add/copy of the vehicle and unit CTs - you also copied all the data that goes with the CT's you copied. ​ Unfortunately,​ a lot of the data loaded into any given CT is going to need to be adjusted in some way.  Further, we will need to take a detailed look at the vehicle data entry and discuss each of the database entry points, what it does, and how it relates to other parts of the database. ​ Just as a side note, parts of the Falcon database are shared across different CTs and records - you must be aware of changes that you make because if you make a change in a record - you must ensure that it doesn'​t affect other records that might share the data record. ​ This also requires the DB editor (you) to thoroughly review a record prior to editing and identify all the users, if any, of the data record. ​ We will talk a little bit more in depth about this when we talk about squadron stores, radars and flags. Now that we have successfully added a new vehicle entity and the two required unit entities lets dig into the the other parts of database editing that will now make the new vehicle entity perform uniquely. ​ You might recall that when you did your add/copy of the vehicle and unit CTs - you also copied all the data that goes with the CT's you copied. ​ Unfortunately,​ a lot of the data loaded into any given CT is going to need to be adjusted in some way.  Further, we will need to take a detailed look at the vehicle data entry and discuss each of the database entry points, what it does, and how it relates to other parts of the database. ​ Just as a side note, parts of the Falcon database are shared across different CTs and records - you must be aware of changes that you make because if you make a change in a record - you must ensure that it doesn'​t affect other records that might share the data record. ​ This also requires the DB editor (you) to thoroughly review a record prior to editing and identify all the users, if any, of the data record. ​ We will talk a little bit more in depth about this when we talk about squadron stores, radars and flags.
- 
falcon4/database/editingtutorial.1230075414.txt.gz ยท Last modified: 2008-12-23 23:36 by snakeman