F-4E_79_Pave_Spike cockpit

[pvince]

12 hours ago, ravenclaw_007 said:

if you like to try be my guest , i have played with the entries and i did not get the result i wanted , i even changed the zero possition from the needle 

 

one thing i found out is that the minus value gets the needle moving to the right and a positive value gets it moving to the left , you cant change that

[LOS_Indicator]
Type=ROLL_INDICATOR
NodeName=Needle_LOS
MovementType=ROTATION_Y
ValueUnit=DEG
Set[01].Position=-100.0
Set[01].Value=-100.0
Set[02].Position=0.0
Set[02].Value=0.0
Set[03].Position=160.0
Set[03].Value=160.0

 

the minus value has to be called first than the zero position and than the positive value , if you reverse it the needle will not move anymore within the limits

 

i also rotated the pivot point of the needle by 180° , no change 

I would try:

[LOS_Indicator]
Type=ROLL_INDICATOR
NodeName=Needle_LOS
MovementType=ROTATION_Y
ValueUnit=DEG
Set[01].Position=+160.0
Set[01].Value=-160.0
Set[02].Position=0.0
Set[02].Value=0.0
Set[03].Position=-100.0
Set[03].Value=+100.0

my best guess, or, if not:

[LOS_Indicator]
Type=ROLL_INDICATOR
NodeName=Needle_LOS
MovementType=ROTATION_Y
ValueUnit=DEG
Set[01].Position=+100.0
Set[01].Value=-100.0
Set[02].Position=0.0
Set[02].Value=0.0
Set[03].Position=-160.0
Set[03].Value= 160.0

 

[+daddyairplanes]

this is beautiful as always but i got one question esp on the _84 and _86 pits: are you gonna scuff up and dirty them up once you have the ini's humming the way you want?

miltary gear (even the jets) gets dirty, and old stuff stays dirty. and by 1986 the Phantom was the old man on the USAF block, especially the ones still on active duty

its the second or third thought for each pic after "wow" or "thats wicked" in my head; "it soooo clean!"

edit: it is wicked enough i almost forgot my mandatory request for the block 10 two holer 

Edited April 18 by daddyairplanes

[+ravenclaw_007]

4 hours ago, pvince said:

I would try:

it is not working , i send you a mail with the old F-4E_79_PaveSpike and the new cockpit so you can try it for your self

[pvince]

With that it works for me:

[LOS_Indicator]
Type=ROLL_INDICATOR
NodeName=Needle_LOS
MovementType=ROTATION_Y
ValueUnit=DEG
Set[01].Position= 160.0
Set[01].Value=-160.0
Set[02].Position=0.0
Set[02].Value=0.0
Set[03].Position=-100.0
Set[03].Value= 100.0

no other change in your file.

Or I misunderstood the problem to solve.

F-4E_79_PaveSpike_COCKPIT.INI

[+ravenclaw_007]

24 minutes ago, pvince said:

With that it works for me:

no other change in your file.

Or I misunderstood the problem to solve.

Thank You 

yap it works , sometimes it is better to get some help

i solved the Shoot light as well they are now only on with air to air weapons

Thank You again

[pvince]

New version with another change, Animation 8 called 2 times, it works but not good. I have optimized. I left the changes visible, to be cleaned in final version.

F-4E_79_PaveSpike_COCKPIT.INI

Edited April 18 by pvince

[+ravenclaw_007]

just added a little extra to the HSI , there are now 2 lights the NAV and ILS lights , NAV light is on during normal flight if you going to land the ILS light go´s on and the NAV light go´s off

on the NAV function selection panel the BEARING/DISTANCE selector knob and the MODE selector knob is on the NAV COMP position , at landing the MODE selector knob is switching form NAV COMP to VOR/ILS

 

the F-4E_79_PaveSpike cockpit has now 229 functions/lights/animations , the original F-4E_78 TW cockpit has 100 , will see if i can add something more

let me know if you like the NAV - ILS idea or if i should remove it

i try to get as much as possible in that cockpit to work some how

[+ravenclaw_007]

need some help

i´m working on the F-4E ARN-101 cockpits , the late ARN-101 cockpits have this Auxiliary Digital  Display Indicator , i try to get it working for the ETE GS mode the GS is working and showing the ground speed in knots. , the ETE ( Estimated Time Enroute ) is showing the time from waypoint to waypoint but it is not showing it correctly , 1 minute should have 60 seconds and not 100 seconds , any idea how i can fix this  ??? or do i have to get used to 100 seconds per minute ???

[ETE_Display]
Type=RANGE_INDICATOR
CounterNodeFormat=ETE_Dig%d
MovementType=DIGITAL_DISPLAY
ValueUnit=MINUTES
Scale=0.1

[GS_Display]
Type=GROUND_SPEED_INDICATOR
CounterNodeFormat=GS_dig%d
MovementType=DIGITAL_DISPLAY
ValueUnit=KNOTS

 

4 minutes 92 seconds to waypoint  with a ground speed of 349 knots

 

any ideas or help is more than welcome , it would be so cool if i get this working correctly

 

Edited April 24 by ravenclaw_007

[Lex2Limit]

Can it' bei the Schale, maybe? 0.1

Have you tried 0.06 ?

[+daddyairplanes]

or mils to minutes?  0.1 mil = 0.3375 min

i know it shouldnt be counting in mils, but its an idea

[+ravenclaw_007]

36 minutes ago, Lex2Limit said:

Can it' bei the Schale, maybe? 0.1

Have you tried 0.06 ?

i try 0.6 but no change 

an other thing is that what is shown on that display is not really minutes , it is a converted value that counts down faster if you fly with higher speed  and it counts down defenetly faster than a minute

i guess that RANGE_INDICATOR was set for NM or KM but not for a time value 

i try to use it with NM but i´m not very happy with it because it is not showing a 0 in front of the dot  , so if you go below 1NM you get a readout like .89 and not 0.89 what looks quite strange

Edited April 24 by ravenclaw_007

[+ravenclaw_007]

14 minutes ago, daddyairplanes said:

or mils to minutes?  0.1 mil = 0.3375 min

i know it shouldnt be counting in mils, but its an idea

no change between Minutes and Mils , i think i let it like it is until i get a better idea , this game has it´s limits and it looks like i´m constantly hitting them

[pvince]

I confirm, range_indicator returns distance, not time. There is nothing I know in SF2 for time to destination. 

[+ravenclaw_007]

10 minutes ago, pvince said:

I confirm, range_indicator returns distance, not time. There is nothing I know in SF2 for time to destination. 

in the moment it is showing something , it is not NM and not KM , dont know what the display is actually showing 

i think the game is converting it to something else that comes closer to minutes even though it is still to fast for minutes

[pvince]

'ValueUnit=MINUTES' is not a valid entry. It is ignored and default unit is used, which is meters for this function.

Valid entries:

1. ValueUnit=KM
2. ValueUnit=NM

Scale= is a valid entry for a multiplier.

In your case, you default to meters, then the multiplier, but only the least significant digits shown, the last 3 at the right, that could create the confusion.

Anyway it is the distance to next waypoint, not time. For a given speed, you can get the right estimated time using "scale=" (at the value of 1/speed) but it is a constant, it will work only for that speed, therefore not really useful.

In such a case, knowing it is impossible to be accurate due to SF2 limitations, I show the distance, better than nothing.

(EDIT: funny but true, ValueUnit=FT is also valid for range_indicator  )

Edited April 25 by pvince

[+ravenclaw_007]

20 minutes ago, pvince said:

'ValueUnit=MINUTES' is not a valid entry. It is ignored and default unit is used, which is meters for this function.

Valid entries:

1. ValueUnit=KM
2. ValueUnit=NM

Scale= is a valid entry for a multiplier.

In your case, you default to meters, then the multiplier, but only the least significant digits shown, the last 3 at the right, that could create the confusion.

Anyway it is the distance to next waypoint, not time. For a given speed, you can get the right estimated time using "scale=" (at the value of 1/speed) but it is a constant, it will work only for that speed, therefore not really useful.

In such a case, knowing it is impossible to be accurate due to SF2 limitations, I show the distance, better than nothing.

if i change it to NM the 0 in front of the dot is not showing it shows only .89 and not 0.89 , is there a way to fix it ???

[pvince]

Not directly with "MovementType=DIGITAL_DISPLAY", but maybe some workaround, to be investigated. I can take that at the same time than avionics70, when I'll be back.

Edited April 25 by pvince
MovementType=DIGITAL_DISPLAY

[+ravenclaw_007]

i just run in to the next wall , i´m already quite dizzy because of constantly running into the SF2 wall of limits 

this time it is the ROLL_INDICATOR again , it looks like that this function was never intendet to work with lights , i need it for the new radar altimeter in the late F-4E_86_ARN-101 cockpit , this radar altimeter has a R/T flag / light to indicate malfunction or if you out of the limits for the radar altimeter , the limits are up to 45° pitch and up to 65° bank 

so i made 3 lights one for the pich an 2 for the roll , the pitch works fine and the right roll light works as well but i dont get the light for the left bank to work , if i mkae an entry with negative values the light is always on if i try to work with values above 180° the light is always on , so for the moment i just have the lights working for pitch and right bank

[RT_Light_Pitch]
Type=PITCH_INDICATOR
NodeName=RT_Light_ON
MovementType=LIGHT
ValueUnit=DEG
Set[01].Position=0.0
Set[01].Value=44.9
Set[02].Position=1.0
Set[02].Value=45.0

[RT_Light_BANK_Right]
Type=ROLL_INDICATOR
NodeName=RT_Light_Right
MovementType=LIGHT
ValueUnit=DEG
Set[01].Position=0.0
Set[01].Value=64.9
Set[02].Position=1.0
Set[02].Value=65.0

[RT_Light_BANK_Left]
Type=ROLL_INDICATOR
NodeName=RT_Light_Left
MovementType=LIGHT
ValueUnit=DEG
Set[01].Position=0.0
Set[01].Value=0.0
Set[02].Position=0.0
Set[02].Value=0.0

 

if itry to work with negative values the light stays on 

[RT_Light_BANK_Left]
Type=ROLL_INDICATOR
NodeName=RT_Light_Left
MovementType=LIGHT
ValueUnit=DEG
Set[01].Position=0.0
Set[01].Value=-64.9
Set[02].Position=1.0
Set[02].Value=-65.0

 

LO light works between 0 an 500 ft

 

above 5000 ft  the needle stays hidden behind the cover

 

65° bank to the right , RT light go´s on 

 

45° pitch , RT light go´s on , digital counter go´s up to 50000 ft

Edited April 25 by ravenclaw_007

[pvince]

Should be:

[RT_Light_BANK_Left]
Type=ROLL_INDICATOR
NodeName=RT_Light_Left
MovementType=LIGHT
ValueUnit=DEG
Set[01].Position=1.0
Set[01].Value=-65.1
Set[02].Position=0.0
Set[02].Value=-65.0

 

Edited April 25 by pvince
Position corrected

[pvince]

And for symmetry :

[RT_Light_BANK_Right]
Type=ROLL_INDICATOR
NodeName=RT_Light_Right
MovementType=LIGHT
ValueUnit=DEG
Set[01].Position=0.0
Set[01].Value=65.0
Set[02].Position=1.0
Set[02].Value=65.1

 

[+ravenclaw_007]

yes it is working 

thank you so much , one problem gone