Cockpit.ini list of items and documentation for creating

[+denissoliveira 1,319]

I'm starting cockpit construction and need this information if anyone has any documentation, a list of these types.

 

I need this information, the list of These types:

Type = is how many? there list?

MovementType = how many are? there list?

ValueUnit = how many are? there list?

CounterNodeFormat = how many are? there list?

ItemNumber = que this is associated?

[+logan4 845]

CounterNodeFormat is actually refers to the individual mesh names that are part of a counter instrument - either analog or digital.

The name itself can be anything you give to them, I always try to give names that refer to what instrument or function they serve or for.

These can go with instruments as

MovementType=ANALOG_COUNTER

MovementType=DIGITAL_DISPLAY

 

CounterNodeFormat=Ripint_dig%d

 

Where existing meshes of the counter are the following: Ripint_dig1,Ripint_dig2,Ripint_dig3. 

 

Bellow is a sample of it in linking structure.

 

MFD_L_AGmode [13 polys, 13 verts] 'Arch & Design (mi)_18'

        Light_Ripqty [2 polys, 4 verts] 'Lights'

                  Ripqty_dig1 [2 polys, 4 verts] 'Arch & Design (mi)_19'

                  Ripqty_dig2 [2 polys, 4 verts] 'Arch & Design (mi)_19'

       Light_RipInt [2 polys, 4 verts] 'Lights'

                  Ripint_dig1 [2 polys, 4 verts] 'Arch & Design (mi)_22'

                  Ripint_dig2 [2 polys, 4 verts] 'Arch & Design (mi)_22'

                  Ripint_dig3 [2 polys, 4 verts] 'Arch & Design (mi)_22'

 

_dig1 shows: single number

_dig2 shows: tens

_dig3 shows: hundreds

 

In cockpit.ini the above looks such:

 

[Ripple_Quantity]

Type=RIPPLE_QUANTITY

MovementType=DIGITAL_DISPLAY

CounterNodeFormat=Ripqty_dig%d

 

[Ripple_interval]

Type=RIPPLE_INTERVAL

MovementType=DIGITAL_DISPLAY

CounterNodeFormat=Ripint_dig%d

 

 

Not sure what is the limit. I have digital counters for 5 digit display capability working fine.

[+logan4 845]

ItemNumber is a bit trickier than the above mentioned one. It can refer to several things, depend on what entry it is used with.

 

A - With engine related instruments/entries (tachometer/fuelflow/temperature/fire,etc) it always refers to the EngineID in the AC_data.ini, as an example:

 

[TachometerL]

Type=TACHOMETER

CounterNodeFormat=RPML_dig%d

MovementType=DIGITAL_DISPLAY

ItemNumber=1   <--- EngineID=1

Scale=100

 

[TachometerR]

Type=TACHOMETER

CounterNodeFormat=RPMR_dig%d

MovementType=DIGITAL_DISPLAY

ItemNumber=2   <--- EngineID=2

Scale=100

 

Max number of it same as the number of engines exist on the aircraft. 

 

 

B  -  When it is part of a Type=WEAPON_TYPE_SELECTOR entry it refers to the following

 

1  - Gun

2  - IRM

3  - Radar guided weapons either SHAM or AHM

4  - Bomb  (unguided)

5  - EO weapons

6  - ARM missiles

7  - Rocket Pods

8  - Laser guided weapons

 

An example:

 

[GUN_Selector]

Type=WEAPON_TYPE_SELECTOR

NodeName=Gun_select

MovementType=LIGHT

ItemNumber=1

 

Maybe there are more of it but these are the 8 I know of.

 

 

C  -  When it is associated with Type=WEAPON_STATION_SELECTOR entry it refers to the StationID= in the AC_Data.ini.

 

Few examples:

 

[iRM_Station1]

Type=WEAPON_STATION_SELECTOR

NodeName=Light_IRM1

MovementType=LIGHT

ItemNumber=10   <--- StationID=10

 

[MRM_Station7]

Type=WEAPON_STATION_SELECTOR

NodeName=Light_MRM7

MovementType=LIGHT

ItemNumber=7   <--- StationID=7

 

[ARM_Station1]

Type=WEAPON_STATION_SELECTOR

NodeName=Light_ARM1

MovementType=LIGHT

ItemNumber=1   <--- StationID=1

 

[RP_Station2]

Type=WEAPON_STATION_SELECTOR

NodeName=Light_RP2

MovementType=LIGHT

ItemNumber=26   <--- StationID=26

 

Max number of it same as max number of weapon stations - 32.

 

 

C2  

The same principle can be used with Type=WEAPON_QUANTITY as could be used to show loaded weapon. In modern MFD display environment this is applicable to stations with a dedicated single type weapon station (fueltank/rocketpod,etc) where only that one thing is ever loaded. This solution provides an alternative to the WeaponTypeID system. However you can use it also on old pit variants where there is only a light or simple text that shows loaded/empty state.

An example:

 

[RP_Station4load]

Type=WEAPON_QUANTITY

NodeName=Light_RP4L

MovementType=LIGHT

ItemNumber=28   <--- StationID=28

Set[01].Position=0.0 

Set[01].Value=0.0     <---OFF

Set[02].Position=1.0

Set[02].Value=1.0     <---ON

 

 

C3

If you associate it with Type=WEAPON_TYPE_ID entry to show what type of weapons are loaded/selected, same as the previous two type, it looks for StationID= in AC_data.ini

As an example:

 

[LGB_Station2load]

Type=WEAPON_TYPE_ID

NodeName=Light_LG2L

MovementType=LIGHT

ItemNumber=2   <--- StationID=2

Set[01].Position=0.0   <---OFF

Set[01].Value=60.5

Set[02].Position=1.0   <---ON

Set[02].Value=61.0

Set[03].Position=1.0   <---ON

Set[03].Value=71.0

Set[04].Position=0.0   <---OFF

Set[04].Value=71.5

 

the Value parameter in this example refers to the items listed under the [WeaponTypeID] system entry in the cockpit.ini, relevant section for comparison. 

CBU-24B=57

Rockeye=58

xxxxx=59

xxxxxx=60

//LGs

BGL400=61

BGL1000=62

AS-30L=63

FR GBU-12D=64

FR GBU-16=65

FR GBU-22=66

FR GBU-24=67

GBU-10=68

GBU-12=69

xxxxxxx=70

xxxxxxxx=71

//EOG-CGR

MARTEL_TV=72

AS30=73

 

 

 

D  -  With gear system related instruments/entries (landing gear indicator/break/open/close,etc) it always refers to the gears in the AC_data.ini.

 

ItemNumber=1   <--- nose gear

                      2   <--- left maingear

                      3   <--- right maingear

 

Maybe others but this 3 I use.

 

 

 

E  -  When it is associated with Type=EXTERNAL_ANIMATION_LINK entry it refers to the AnimationID= in the AC_Data.ini.

 

[Canopyhandle]

Type=EXTERNAL_ANIMATION_LINK

NodeName=Canopyhandle

MovementType=ROTATION_X

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=40.0

Set[02].Value=1.0

ItemNumber=8    <--- AnimationID=8

 

Max number can be 10, as only 10 Animation slots exists currently in game's Aircraft models.

 

 

There could be other applications or meanings but the above are what I know and use.

Edited August 13, 2016 by logan4

[+yakarov79 10,503]

Cockpit movements:

 

ROTATION_X,
ROTATION_Y,
ROTATION_Z,
POSITION_X,
POSITION_Y,
POSITION_Z,
ANIMATION,
TEXTURE_U,
TEXTURE_V,
ORIENTATION,
ATTITUDE,
STICK_ORIENTATION,
ANALOG_COUNTER,
DIGITAL_DISPLAY,
LIGHT

 

gauges:
AIRSPEED_INDICATOR,
TRUE_AIRSPEED_INDICATOR,
GROUND_SPEED_INDICATOR,
MACH_NUMBER_INDICATOR,
SIDESLIP_VELOCITY_INDICATOR,
TURN_INDICATOR,
PRESSURE_ALTIMETER,
PRESSURE_ALTIMETER_1,
PRESSURE_ALTIMETER_2,
PRESSURE_ALTIMETER_3,
RADAR_ALTIMETER,
LOW_ALT_WARNING_LIGHT,
VERTICAL_VELOCITY_INDICATOR,
ACCELEROMETER,
ANGLE_OF_ATTACK_INDICATOR,
ANGLE_OF_ATTACK_INDEXER,
ATTITUDE_DIRECTOR_INDICATOR,
BANK_INDICATOR,
BEARING_MARKER,
HEADING_MARKER,
COURSE_ARROW,
COURSE_DEVIATION,
MAGNETIC_COMPASS,
GYRO_COMPASS,
RANGE_INDICATOR,
TACHOMETER,
MANIFOLD_PRESSURE,
INETERNAL_FUEL_QUANTITY_INDICATOR,
EXTERNAL_FUEL_QUANTITY_INDICATOR,
TOTAL_FUEL_QUANTITY_INDICATOR,
FUEL_FLOW_INDICATOR,
INLET_TEMPERATURE_INDICATOR,
EXHAUST_GAS_TEMPERATURE_INDICATOR,
NOZZLE_POSITION_INDICATOR,
OIL_PRESSURE_INDICATOR,
HYDRAULIC_PRESSURE_INDICATOR,
PNEUMATIC_PRESSURE_INDICATOR,
THREAT_AIR_INTERCEPT_WARNING_LIGHT,
THREAT_GROUND_RADAR_WARNING_LIGHT,
THREAT_LAUNCH_WARNING_LIGHT,
MASTER_CAUTION_LIGHT,
LANDING_GEAR_WARNING_LIGHT,
INLET_TEMPERATURE_WARNING,
ENGINE_OVERHEAT_WARNING_LIGHT,
ENGINE_FIRE_WARNING_LIGHT,
HUD_MODE_INDIDCATOR,
WEAPON_TYPE_SELECTOR,
AIR_TO_AIR_MODE_INDICATOR,
AIR_TO_GROUND_MODE_INDICATOR,
GUN_ROUNDS_INDICATOR,
GUNSIGHT_DEPRESSION_INDICATOR,
GUN_GROUP_INDICATOR,
RADAR_MODE_SELECTOR,
WEAPON_STATION_SELECTOR,
MASTER_ARM_INDICATOR,
RADAR_IN_RANGE_INDICATOR,
EXTERNAL_TANK_INDICATOR,
CONTROL_STICK,
CONTROL_STICK_PITCH,
CONTROL_STICK_ROLL,
RUDDER_PEDAL,
THROTTLE_CONTROL,
THRUST_VECTOR_CONTROL,
LANDING_GEAR_INDICATOR,
AIR_BRAKE_INDICATOR,
WHEEL_BRAKE_INDICATOR,
FLAPS_CONTROL_HANDLE,
ARRESTING_HOOK_INDICATOR,
RADAR_SCOPE,
RWR,TV_SCOPE,
MOVING_MAP,
THREAT_INDICATOR,
MULTI_FUNCTION_DISPLAY,
CLOCK_SECOND,
CLOCK_MINUTE,
CLOCK_HOUR,
HUD,
REFLECTION,
MIRROR,
ECM,
PITCH_INDICATOR,
ROLL_INDICATOR,
GUN_FIRE_ANIMATION,
GUN_RELOAD_ANIMATION,
MAX_G,
CAGED,
AA,
AG,
6TO12,
3TO9

[+logan4 845]

SF2 has few more:

 

BINGO_FUEL_INDICATOR

MISSION_TIMER

INTERNAL_FUEL_QUANTITY_INDICATOR  -   the same in SF1 is:  INETERNAL_FUEL_QUANTITY_INDICATOR

EXTERNAL_ANIMATION_LINK

AFTERBURNER_INDICATOR

WEAPON_SHOOT_CUE

RADAR_BREAK_X

WEAPON_QUANTITY

RIPPLE_QUANTITY

RIPPLE_INTERVAL

WEAPON_TYPE_ID

CHAFF_COUNTER

FLARE_COUNTER

AUTO_PILOT

ILS_TOGGLE

GLIDE_SLOPE_INDICATOR

[KJakker 875]

This thread is looking like it is a contender for the Knowledge Base.

Edited August 13, 2016 by KJakker

[+denissoliveira 1,319]

Thank you very much !!!

I will use the existing cockpit to find out more!

Sorry for the topic in the wrong place.

as to

POSITION_XYZ - the first define what position? position 0 and position 1 (with distacia value of the initial position?)

  and ANIMATION - use animation in the cockpit and set the start trigger button?

[+logan4 845]

The bellow is an example of a rudder pedal moving linear way

 

[LeftRudder]

Type=RUDDER_PEDAL

NodeName=PedalL

MovementType=POSITION_Y

Set[01].Position=0.05   <---- moved 5cm forward

Set[01].Value=-1.0       <---- right max input

Set[02].Position=0.0    <---- original position

Set[02].Value=0.0        <---- no input on rudders

Set[03].Position=-0.05   <---- moved 5cm back (toward pilot)

Set[03].Value=1.0         <----- left max input

 

Game will move only according the input level you apply on the game control.

 

Set(%d)Position always equals the amount you want to move the object 0.001 is 1mm, as in above 0,05 is 5cm 

Set(%d)Value always the movement's "triggering" parameter.

 

You can set multiple ones for a single object, all depends on the movements you want to generate. Only rule is, they always go in pairs, meaning you can not have a set(x)position without a matching set(x)value entry.

 

How ever you can use other Value= than 1, if you want an earlier or several response from a switch object, range is 0.001-1.000.

[+denissoliveira 1,319]

Value Unit = there is a list of this?

Is there any documentation to download?

[+logan4 845]

Might be not all of valueunits..

 

NM

FEET

LB

KG

KM

METERS

DEG

KNOTS

KMPH

MPS

FPM

 

 

My last post above (nr8) about set(x)position/value parameters only reflect the Position_x/z/y as that was the question.

If you have Rotation_X/Z/Y or Light then the range can depend on the instrument you try to make.

 

[Light_Bingosys]

Type=BINGO_FUEL_INDICATOR

NodeName=Light_Bingosys

MovementType=Light

ValueUnit=KG

Set[01].Position=1.0

Set[01].Value=0.0

Set[02].Position=1.0

Set[02].Value=550.0

Set[03].Position=0.0

Set[03].Value=600.0

Set[04].Position=0.0

Set[04].Value=9000.0

 

[VelocIndA]

Type=AIRSPEED_INDICATOR

NodeName=VelocidadIndicada

MovementType=ROTATION_Z

ValueUnit=KMPH

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=1080.0

Set[02].Value=3000

 

 

[+denissoliveira 1,319]

This does not work, it does not move

 

[gearBotao]

Type=LANDING_GEAR_INDICATOR

NodeName=GearLever

MovementType=ROTATION_X

ItemNumber=1

Set[01].Position=0.0

Set[01].Value=0

Set[02].Position=35

Set[02].Value=1

[+Cliff7600 1,120]

It could be because the instrument list is incorrect :

 

Instrument[001]=ClockMinute

Instrument[002]=AirspeedIndicator

Instrument[003]=VerticalVelocityIndicator

Instrument[004]=OilPressureGauge

Instrument[005]=Altimeter

Instrument[006]=Tachometer

Instrument[008]=gearBotao

 

but that still would work :

 

Instrument[001]=ClockMinute

Instrument[002]=AirspeedIndicator

Instrument[003]=VerticalVelocityIndicator

Instrument[004]=OilPressureGauge

Instrument[005]=Altimeter

Instrument[006]=Tachometer

Instrument[007]=

Instrument[008]=gearBotao

 

-------------------------------------------------------------

it could be because the mesh name is incorrect :

 

[gearBotao]

Type=LANDING_GEAR_INDICATOR

NodeName=GearLever

MovementType=ROTATION_X

ItemNumber=1

Set[01].Position=0.0

Set[01].Value=0

Set[02].Position=35

Set[02].Value=1

 

Check with the Mue's LOD viewer, or in the OUT file of the cockpit that "GearLever" is the correct name.

 

-------------------------------------------------------------

It could be that the lever is actually moving but you can't see it because you chose the wrong axis and it rotates around its length axis.

Try "MovementType=ROTATION_Y" and "MovementType=ROTATION_Z"

 

-------------------------------------------------------------

(And it may have been because the position settings 1,2,3,... of the rotation are not decreasing or increasing in the same direction for all the values. Not the case here.)

 

-------------------------------------------------------------

It could be because there's another instrument that already uses the "GearLever" mesh with the same MovementType.

The same mesh could appear in several instruments but only for one and only movement type of each kind

(ex : one for a rotation + one for a position, or one for a position + one for a light)

 

 

If "it does not move" it's because you did something wrong. Other than that everything can move (maybe not the way you want, but it will move)

Edited August 14, 2016 by Cliff7600

[+logan4 845]

Denis,

you do not need to use the itemnumber=1 in that statement. Yes, I know might be confusing, but sometimes you can get away with things like this.

 

I use the bellow way and works OK. Depend on how you have the lever in the pit model, you sometimes need to flip values in the cockpit.ini

 

[LandingGearLever]

Type=LANDING_GEAR_INDICATOR

NodeName=Gearlever

MovementType=ROTATION_X

Set[01].Position=-45.0

Set[01].Value=0

Set[02].Position=0.0

Set[02].Value=1

 

Other things can be as Cliff7600 wrote.

[+denissoliveira 1,319]

Need help,

I need an altimeter with 10000, 1000, 100 and 10,

use digit ALTI_dig_%d,%d equal to 3.2 and 1, if I put a %d equal to 4 and put the Set [02] .Value = 100.0 with the value 10.0 will work?

 

example: the display digit appears 1/1/1/89 (11189 ft),%d = 4/3/2/1

 

 

And FUEL_FLOW_INDICATOR with four digits

Edited August 15, 2016 by denissoliveira

[+denissoliveira 1,319]

I have problem in rotation with the selection of weapons, it does not rotate on the same axis, this is in degrees or meters.

And problem with instruments with 4 digits.

 

[FuelFlowIndicator]

Type=FUEL_FLOW_INDICATOR

CounterNodeFormat=counter_FF_%d

MovementType=ANALOG_COUNTER

ValueUnit=KG

SmoothCounter=TRUE

 

[Altimeter2]

Type=PRESSURE_ALTIMETER_3

NodeName=NeedleAlti100

CounterNodeFormat=ALTI_dig_%d

MovementType=ROTATION_X

ValueUnit=FEET

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=360.0

Set[02].Value=10.0

SmoothCounter=TRUE

 

 

 

[+yakarov79 10,503]

for analog altimeter try this:

 

[RadarAlt]
Type=RADAR_ALTIMETER
CounterNodeFormat=alt_dig%d
MovementType=ANALOG_COUNTER
ValueUnit=FEET

 

no need to putthis:

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=360.0

Set[02].Value=10.0

SmoothCounter=TRUE

 

MovementType=ROTATION_X

 

and make seperate entry for clock type altimeter

[+logan4 845]

If you use a dial type of instrument then rotation axis is mostly _Y not X - unless you turn its pivot.

 

If you use a dual digit (tens) for the "single" analog counter node then use "Scale=10" otherwise would not count properly.

 

As Yakarov showed do not put underline in the format dig_% it is only dig%.

 

For a weapon type selector you have on the pic, use something like the bellow example. You might have to fiddle with the degrees value depend on if you use a needle or the plate to move. on a dial like instrument/rotating object the position part is always in degree, the value section in this instruments relate to weapon types as listed in post#3 sectionB

 

[WPSelector]

Type=WEAPON_TYPE_SELECTOR

NodeName=WPselect

MovementType=ROTATION_Y

Set[01].Position=-90.0

Set[01].Value=1.0

Set[02].Position=-90.0

Set[02].Value=2.0

Set[03].Position=-90.0

Set[03].Value=3.0

Set[04].Position=90.0

Set[04].Value=4.0

Set[05].Position=0.0

Set[05].Value=5.0

Set[06].Position=0.0

Set[06].Value=6.0

Set[07].Position=0.0

Set[07].Value=7.0

Set[08].Position=90.0

Set[08].Value=8.0

 

[+denissoliveira 1,319]

Thanks, these work now.

 

to the altimeter, created a second with different scale, only 3 digits, 4 not works.

 

[Altimeter](ALTI_dig_3,2, 1 and needle , for 10000, 1000, 100 Feet)

Type=PRESSURE_ALTIMETER_3

NodeName=NeedleAlti100

CounterNodeFormat=ALTI_dig_%d

MovementType=ROTATION_X

ValueUnit=FEET

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=360.0

Set[02].Value=100.0

SmoothCounter=FALSE

 

[Altimeter2] (and ALTI_dig2_1, for 10 FEET)

Type=PRESSURE_ALTIMETER_3

CounterNodeFormat=ALTI_dig2_%d

MovementType=ROTATION_X

ValueUnit=FEET

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=360.0

Set[02].Value=10.0

SmoothCounter=TRUE

 

so it works well!

 

 

Now, the FUEL_FLOW_INDICATOR does not work, my unit is in KG

 

[FuelFlowIndicator]

Type=FUEL_FLOW_INDICATOR

CounterNodeFormat=counter_FF_%d

MovementType=ANALOG_COUNTER

ValueUnit=KG

SmoothCounter=TRUE

[+yakarov79 10,503]

not sure but for

Type=FUEL_FLOW_INDICATOR

should be set: value 0 and max value of "flow"

so not sure if analog counter will work here since it shows diferent values depending on engine throttle.

 

but you can st analog counter for fuel quantity.

[Peugeot205 2,745]

Are you working on the Etendard IV cockpit?

[+denissoliveira 1,319]

This ?

 

[FuelFlowIndicator]

Type = FUEL_FLOW_INDICATOR

CounterNodeFormat = counter_FF_% d

MovementType = ANALOG_COUNTER

ValueUnit = KG

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=360.0

Set[02].Value=1.0

SmoothCounter = TRUE

[+logan4 845]

I think with the analog altimeter the main issue was that you used Type=Pressure_Altimeter_3.   And my bad on the scaling parameter instead of Scale=10 should be Scale=0.1

 

I normally only use the simple Type=Pressure_Altimeter  without any numbering and works fine with 4 or even 5 digit counter.

As you can see it on this pic. I set up 2 analog counters beside my digital counter instrument for comparison. The 4 wheel counter works with 10feet on last digit the one bellow with 5 wheel works on single feet.

 

 

These are the setting I used for it, no need for anything else with position/value parameter.

 

[AltimeterAn1]

Type=PRESSURE_ALTIMETER

CounterNodeFormat=Altan_dig%d

MovementType=ANALOG_COUNTER

ValueUnit=FEET

Scale=0.1     <----will show 10ft increment

 

[AltimeterAn2]

Type=PRESSURE_ALTIMETER

CounterNodeFormat=Analt_dig%d

MovementType=ANALOG_COUNTER

ValueUnit=FEET

Scale=1

 

Regarding the fuel flow it can be analog counter. As the pic show works fine.The only thin with KG unit is that need to use scale value as not sure if it measures in KG/sec or Kg/min.

As on the pic, it works OK.

 

 

These are the settings for it:

 

[FuelFlowCounter]

Type=FUEL_FLOW_INDICATOR

CounterNodeFormat=FFlow_dig%d

MovementType=ANALOG_COUNTER

ItemNumber=1

ValueUnit=KG

Scale=10

 

 

 

 

[+denissoliveira 1,319]

Yes

I added a 4 digit individual 10000feet, works well, thank you.

 

on fuel, I do not know the scale in data.ini, not where you configure. but the instrument put kg. I will test this configuration.

 

About flaps (my last question) as I do so only move on the last stage (landing) and do not move at takeoff?

[+logan4 845]

In theory should move on both cases. What controller you use for it? FLAPS_CONTROL_HANDLE or FLAP_ANGLE or EXTERNAL_ANIMATION_LINK?

 

Should work with something like this.

 

[FlapLever]

Type=FLAPS_CONTROL_HANDLE

NodeName=Flap_Lever

MovementType=ROTATION_X

Set[01].Position=0.0

Set[01].Value=0.0

Set[02].Position=25.0

Set[02].Value=1.0

Set[03].Position=45.0

Set[03].Value=2.0

Edited August 16, 2016 by logan4

[+denissoliveira 1,319]

The flaps are animation, decided to increase the angle and only displaying the last stage. Solved

The fuelflow, there were 2 instruments, for this reason he did not work, now it's ok!

Question, the fuelflow is in hours minutes of consumption?