PMC websites shut down November 13th 2025 unless web hosting fees are paid. See up to date status from PMC Website Hosting and Domain Registration Fee Status forum topic. Please Support PMC to help keep these websites online.

Enjoyed or found this pages content useful, please Support PMC to help me keep this web page online beyond November 13th 2025 when web hosting fees are due.

PMC Editing Wiki

User Tools

Site Tools

Trace:
arma:modeling:model_config

Differences

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

Link to this comparison view

Next revision		Previous revision
arma:modeling:model_config [2007/07/13 12:44] – created model_config initial page snakemanarma:modeling:model_config [2024/08/01 09:39] (current) – links added. snakeman
Line 1: Line 1:
-====== Model Config ======+====== ArmA 1 Model Config ====== 
 + 
 +[[https://www.pmctactical.org/forum/viewforum.php?f=42|ArmA 1 Forum]], [[:arma|ArmA 1 Home]], [[arma:config|ArmA 1 Config]], [[arma:tools|ArmA 1 Tools]], [[arma:file_formats|ArmA 1 File Formats]], [[arma:missions|ArmA 1 Missions]], [[arma:modeling|ArmA 1 3D Modeling]], [[arma:terrain|ArmA 1 Terrain]], [[arma:texturing|ArmA 1 Texturing]], [[arma:scripting|ArmA 1 Scripting]] 
 + 
 +**ArmA 1** aka Armed Assault (ArmA)
  
 **Description** **Description**
  
-The model configuration file (model cfg for short) is the interface between a (P3D) model and the program.+The model configuration file (model cfg for short) is the interface between a (P3D) model and the program. The model.cfg would only be necessary if you intend to preview animations and such in O2 using your model.
  
 It is a look-up table which is processed during the binarization process, to tell the program what the various sections of the model are, which skeleton it uses and how it is animated. It is a look-up table which is processed during the binarization process, to tell the program what the various sections of the model are, which skeleton it uses and how it is animated.
Line 15: Line 19:
 Most models will be able to inherit definitions from basic definitions on higher levels in the data hierarchy. An example hierarchy is described and illustrated below. Most models will be able to inherit definitions from basic definitions on higher levels in the data hierarchy. An example hierarchy is described and illustrated below.
  
-p:\ofp2\vehicles\model.cfg - Defines a class Default. +p:\ofp2\vehicles\model.cfg - Defines a class Default.\\ 
-p:\ofp2\vehicles\land\wheeled\model.cfg - Defines a class Car.+p:\ofp2\vehicles\land\wheeled\model.cfg - Defines a class Car.\\
 p:\ofp2\vehicles\land\wheeled\landrover\model.cfg - Defines a class LandRover. p:\ofp2\vehicles\land\wheeled\landrover\model.cfg - Defines a class LandRover.
  
-p:\ofp2\vehicles\land\wheeled\landrover\lr6x6_3 - In the model is a property config=LandRover (this feature is not implemented and may never be).+p:\ofp2\vehicles\land\wheeled\landrover\lr6x6_3 - In the model is a property config=LandRover (this feature is not implemented and may never be).\\
 p:\ofp2\vehicles\land\wheeled\landrover\lr6x6_mg240 - Has a LR6x6_MG240.cfg, which inherits from class LandRover and adds definitions for a turret. p:\ofp2\vehicles\land\wheeled\landrover\lr6x6_mg240 - Has a LR6x6_MG240.cfg, which inherits from class LandRover and adds definitions for a turret.
  
-{{ http://tactical.nekromantix.com/images/wiki/ModelConfig_ModelCfg1.jpg }}+{{ https://pmc.editing.wiki/images/ModelConfig_ModelCfg1.jpg }}
  
 ====== Notes ====== ====== Notes ======
Line 36: Line 40:
 There are model cfg files that do not relate directly to a specific model, but are used for the generic base class definitions, such as class Default. There are model cfg files that do not relate directly to a specific model, but are used for the generic base class definitions, such as class Default.
  
-The functionality of the animations has been extended, allowing to do in scripting what was done before using RTM animations. +The functionality of the animations has been extended, allowing to do in scripting what was done before using RTM animations.
 In addition, animation controllers were introduced, which allow for the control of different animations at the same time. This opens up possibilities like having several turrets on a tank. In addition, animation controllers were introduced, which allow for the control of different animations at the same time. This opens up possibilities like having several turrets on a tank.
  
Line 50: Line 54:
 <code> <code>
 //Declare base classes //Declare base classes
-class CarAnimations +class CarAnimations
 { {
  class IndicatorSpeed;  class IndicatorSpeed;
Line 57: Line 61:
 { {
  class Car; //Declare base class  class Car; //Declare base class
- class Vodnik: Car + class Vodnik: Car
  {  {
  sectionsInherit = "Car"; //Inherit all sections from class Car  sectionsInherit = "Car"; //Inherit all sections from class Car
Line 66: Line 70:
  };  };
  skeletonName = "Vodnik"; //Use the Vodnik skeleton  skeletonName = "Vodnik"; //Use the Vodnik skeleton
-  +
  class Animations: CarAnimations //Inherit from generic animations  class Animations: CarAnimations //Inherit from generic animations
  {  {
Line 83: Line 87:
  
 <code> <code>
-class CfgSkeletons  +class CfgSkeletons 
-{ +{
  class Car; //Define base class  class Car; //Define base class
- +
  class Vodnik: Car  class Vodnik: Car
  {  {
Line 103: Line 107:
 This segment is part of class cfgModels and defines all animations used by the model. This segment is part of class cfgModels and defines all animations used by the model.
  
-<code>  +<code> 
-class Animations +class Animations
 { {
  class FrontWheelR  class FrontWheelR
Line 140: Line 144:
 | aileronB | The bottom speed brake as opening ailerons | Airplane | | aileronB | The bottom speed brake as opening ailerons | Airplane |
 | aileronT | The top speed brake as opening ailerons | Airplane | | aileronT | The top speed brake as opening ailerons | Airplane |
-| aoa | The Angle Of Attack | Airplane | +| aoa | The Angle Of Attack | Airplane |
 | elevator | The elevators | Airplane | | elevator | The elevators | Airplane |
 | flap | The flaps | Airplane | | flap | The flaps | Airplane |
Line 240: Line 244:
  //Used by animations called Door1, which don't define the source  //Used by animations called Door1, which don't define the source
  //parameter or by animations that define source Door1;  //parameter or by animations that define source Door1;
- class Door1 + class Door1
  {  {
  source = "user"; //The controller is defined as a user animation  source = "user"; //The controller is defined as a user animation
Line 259: Line 263:
  
 You can find a howto for the CfgModels (a working attack helicopter) as well as a howto on cfgModels & cfgSkeletons with additional description and examples. You can find a howto for the CfgModels (a working attack helicopter) as well as a howto on cfgModels & cfgSkeletons with additional description and examples.
 +
arma/modeling/model_config.1184330657.txt.gz · Last modified: 2007/07/13 12:44 (external edit)