Question about cockpit interactive light

[Velo]

Hi, i`m learning to make a cockpit. Now just have a prototype for study.

I stuck in interacive light. I dont kown where  i wrong, either texturing in 3dsmax or coding in INI file. Here `s my work.

 

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

I try to make 3 lights in my cockpit. "A" indicates AA weapon, "B" for AGweapon, and "C" for hook. These symbols are already made in my TGA file, which of course in alpha channel. See my game and 3DSMax screenshot.

Now the light just show the ABC, no interactive funcation at all. So ,there are 3 questins:

 

1, Am I wrong in texture setting in 3dsmax? 

2, The code is not correct? How to fix it ?

3, What is "Position=0.0" stand for? and what is the meaning of Value=0,1,2   ?

 

I put my INI and Max file here.  Hope someone can help.

 

COCKPIT_test.zip

 

--

 

 

 

 

-----------

and here is my code. I am sure NodeName are correct.

Instrument[002]=MARM_AA
Instrument[003]=MARM_AG
Instrument[004]=HookLight

[MARM_AA]
Type=HUD_MODE_INDIDCATOR
NodeName=AALight
MovementType=LIGHT
Set[01].Position=0.0
Set[01].Value=0
Set[02].Position=1.0
Set[02].Value=1
Set[03].Position=0.0
Set[03].Value=2

[MARM_AG]
Type=HUD_MODE_INDIDCATOR
NodeName=AGLight
MovementType=LIGHT
Set[01].Position=0.0
Set[01].Value=0
Set[02].Position=0.0
Set[02].Value=1
Set[03].Position=1.0
Set[03].Value=2

[HookLight]
Type=ARRESTING_HOOK_INDICATOR
NodeName=HookLight
MovementType=LIGHT
 

Edited February 5, 2015 by Velo

[yakarov79]

Do you have instrument[001]=   there ?

If not game will not pick position entry  for instruments 2,3 onward.

 

Positions and values stands for movement type- rotationx,y,z and position x,y,z. For light it is not needed. Maybe shouldnt be there.

[logan4]

What they mean based on my understanding of cockpit operations

 

[MARM_AA]
Type=HUD_MODE_INDICATOR
NodeName=AALight
MovementType=LIGHT
Set[01].Position=0.0    <------ means Light OFF
Set[01].Value=0          <------ Navigaton mode
Set[02].Position=1.0    <------ Light ON
Set[02].Value=1          <------- AA mode
Set[03].Position=0.0    <------- Light OFF
Set[03].Value=2          <------- AG mode

 

So in theory should work correctly.

 

An other thing noticed, which might cause your issue.

The system names should follow each other without any system functions interrupting them. I advise you to look up any of the 3rd party cockpit.ini-s you will see how should be done.

 

 

Instrument[001]=AirspeedIndicator

Instrument[002]=MARM_AA

Instrument[003]=MARM_AG

Instrument[004]=HookLight

 

Then the individual items

[AirspeedIndicator]

Type=AIRSPEED_INDICATOR

NodeName=needle_speed

MovementType=ROTATION_Y

ValueUnit=KNOTS

Set[01].Position=0.0

Set[01].Value=0.0

 

etc

etc

 

 

You also have typing error for the aa/ag lights Type entry

 

Type=HUD_MODE_INDIDCATOR   <---- should be Type=HUD_MODE_INDICATOR

 

 

If the above list correction still not results working lights you can try thy following without the parameters part:

 

[MARM_AA]

Type=AIR_TO_AIR_MODE_INDICATOR

NodeName=AALight

MovementType=LIGHT

 

[MARM_AG]

Type=AIR_TO_GROUND_MODE_INDICATOR

NodeName=AGLight

MovementType=LIGHT

[Velo]

Much appreciate !

 

After check other aircraft cockpit and follow your clue, it is fixed.

The key is Type=WEAPON_TYPE_SELECTOR

 

It will determine the meaning of "Position" and "Value"

Position means Ture or False

and

Value means the current weapon type, 2=heat

 

also, ItemNumber=2 set the weapon type to sidewinder

As far as i test, it works.

 

Do i have any mistake here ?  I `m afraid there are something i dont kown despite it seems work apparently.

Edited February 6, 2015 by Velo

[yakarov79]

Position indicates where node will be moved after action.

In (for example radar altimeter) position will be rotation angle of needle.

Value wil be set for example  1000 for position -30 and 1500 for position -60 etc.

 

In two position switch (like master arm or weapon selector) you can set position (example) rotation_X - 30degree. it will rotate node 30 degree up/down when activated weapon.

value will be 0 off and 1 for on.

 

 example

 

[weaponStationR3]
Type=WEAPON_STATION_SELECTOR
NodeName=Switch_R-Wing-out
MovementType=ROTATION_Z
Set[01].Position=0.0
Set[01].Value=0
Set[02].Position=-30.0
Set[02].Value=1
ItemNumber=6

 

Item number (in weapons selector) is related to weapon station in main aircraft_data.ini.

So if weapon station (your example) IRM / sidewinder station is weapon station ID 2, then in cockpit ini file it will be Itemnumber=2, and for example bomb centerline station is weaponstation ID=3 then in  cockpit it will be item number=3

 

Mirage factory A-7 and F-8 are good reference to know how it works.

[Velo]

Position indicates where node will be moved after action.

In (for example radar altimeter) position will be rotation angle of needle.

Value wil be set for example  1000 for position -30 and 1500 for position -60 etc.

 

.........

 

Much appreciate for your patient explanation ! Both them are so valuable to me !

 

I used to consider the ItemNumber as a game engine preset value indicating weapon type, now i see my mistake.

I will contiue to test the light indicators and switch

 

Things getting alive !

[Nyghtfall]

Sorry for reviving that old thread, but my question is somewhat related I guess.

 

I have separated a weapons station in a bomb-only-part (StationID=1, Group=1) and a missile-only-part (StationID=2, Group=1) and my cockpit has "ARM"-lights for each station. My problem now is, that I have to use 1 "ARM"-light for both separated stations (as both still refer to the same pylon). I tried it with no luck. Is there anything I missed or that I can do about it? Cockpit is a stock one, so not available for 3D-work.

[+Crusader]

Thats the way it is.

Each mesh in the cockpit ( for a light or indicator/needle of any type) can only be used one time, not for multiple functions or tied to

multiple stations.

 

Thats what makes building modern cockpits with MFDs such a nightmare (well.. depends on the individual modders patience..), they have

hundreds of single mesh nodes for lights to cover all possibilities for the stores ...

[FastCargo]

Thats the way it is.

Each mesh in the cockpit ( for a light or indicator/needle of any type) can only be used one time, not for multiple functions or tied to

multiple stations.

 

Thats what makes building modern cockpits with MFDs such a nightmare (well.. depends on the individual modders patience..), they have

hundreds of single mesh nodes for lights to cover all possibilities for the stores ...

 

Oh heck ya...when I modded the F-15C cockpit to have a working MFD, I had to make a buttload of ini entries and meshes for all the combinations of weapons.  And that was for only an air to air bird...

 

FC

[Nyghtfall]

Ah crap then.

 

Thanks for the quick answer! :)

[+Crusader]

Sorry for reviving that old thread, but my question is somewhat related I guess.

 

I have separated a weapons station in a bomb-only-part (StationID=1, Group=1) and a missile-only-part (StationID=2, Group=1) and my cockpit has "ARM"-lights for each station. My problem now is, that I have to use 1 "ARM"-light for both separated stations (as both still refer to the same pylon). I tried it with no luck. Is there anything I missed or that I can do about it? Cockpit is a stock one, so not available for 3D-work.

Well... I've found a solution ..

 

added Sparrow capability to USN F-4's inner wing stations which also required modifications to the missile panel..

had to use a light twice + move it to another position if a specific station is in use to fill a spot where no light exists

 

The trick is to not use the MovementType=LIGHT

 

I use MovementType=Position_X (Y,Z)

And the ItemNumber=  can also be the Value =

So , example from the F-4B Sparrow mod

 

[station6Light]

Type=WEAPON_STATION_SELECTOR

NodeName=selected_L_FWD

MovementType=POSITION_Y     (moves mesh fore/aft in this case)

Set[01].Position=0.002               (moves it forward 2 mm to hide it behind the panel mesh)

Set[01].Value=5.0                        (this is station ID #5 for which the light is OFF , also valid for IDs 1 to 4)

Set[02].Position=0.00                  (light is modeled in ON position, so no move required, 0.00)

Set[02].Value=6.0                        (this is station ID 6 for which the light is ON )

Set[03].Position=0.002                 (Set 3 hides the light mesh again to turn it OFF)

Set[03].Value=7.0

Set[04].Position=0.002                 (Set 4 has it still set to OFF to keep it OFF for station IDs 7 to 16)

Set[04].Value=16.0

Set[05].Position=0.00                   (Set 5 .. ON again for Station 17)

Set[05].Value=17.0

Set[06].Position=0.002                (Set 6 .. OFF again)

Set[06].Value=18.0

 

Above setup has the light ON for stations 6 and 17 and OFF for all others

I had to set it up that way to be able to move the same mesh vertically to use it for the #17 station (new left wing AIM-7 STA), there is no light

modeled for it in the cockpit

 

The vertical move with the same mesh selected_L_FWD :

[station17LightMove]

Type=WEAPON_STATION_SELECTOR

NodeName=selected_L_FWD

MovementType=POSITION_Z

Set[01].Position=0.00

Set[01].Value=16.0

Set[02].Position=-0.031

Set[02].Value=17.0

Set[03].Position=0.00

Set[03].Value=18.0

 

so the same mesh is used for 2 stations , first "ON in place" and the 2nd time "ON and moved vertically"

 

A second method where no vertical/horizontal move is required is to set it up like this :

 

1st use of ready_L_WING_a mesh with POSITION_Y, ItemNumber=10  = Station ID 10

[station10ArmedLight]

Type=WEAPON_QUANTITY

NodeName=ready_L_WING_a

ItemNumber=10

MovementType=POSITION_Y

Set[01].Position=0.01

Set[01].Value=0.0

Set[02].Position=0.00

Set[02].Value=1.0

 

2nd use of ready_L_WING_a mesh with POSITION_Y , ItemNumber=17  = Station ID 17

[station17ArmedLight]

Type=WEAPON_QUANTITY

NodeName=ready_L_WING_a

ItemNumber=17

MovementType=POSITION_Y

Set[01].Position=0.01

Set[01].Value=0.0

Set[02].Position=0.00

Set[02].Value=1.0

 

 

 

Some pics of the modified missile panel

 

missiles RDY/present on all fuselage and inner wing stations, shows heat and radar msls no matter which is selected (limitation)

without a missile selected

 

left forward fuselage sparrow selected

shows SELECTED light ON and in original position

 

left wing sparrow selected

shows the Left FWD SELECTED light ON and re-positioned downwards to the wing msl indicator

 

left forward and wing stations empty , right forward fuselage sparrow selected

Edited July 22, 2015 by Crusader

[Falcon1364]

Hi Velo,

Thanks a lot for this helpful discussion. How do I add an external fuel tank light indicator to F-4Es light HAF F-4E phantom II? Can you please help me with that? Thanks a lot.