gray eagle
SOH-CM-2025
I just checked my key assignments and CTRL + W is assigned to water rudder. I wonder if Pack 1 (NAVY Planes) was originally suppose to have a drogue chute.
-
There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.
The Staff of SOH
AS F-4 Phantom
- Thread starter gray eagle
- Start date
I just checked my key assignments and CTRL + W is assigned to water rudder. I wonder if Pack 1 (NAVY Planes) was originally suppose to have a drogue chute.
harrybasset
Charter Member
Yes Pack 1 Navy Phantoms has a working (Visible) drag chute in FS9. It works from the Concorde nose C & V keys which FSX does not accept. I thought a while ago that someone had found a way round this but I've searched but can't find anything now.
gray eagle
SOH-CM-2025
Sonic Boom
Anyone try adding a sonic boom effect to AS F-4?
Anyone try adding a sonic boom effect to AS F-4?
Jafo
SOH-CM-2024
Haven't bothered yet...but should be no different to any other plane....
In the panel.cfg...
// --------------------------------------------------- SONIC BOOM
gauge26=rcb-miljet!SonicBoomControl, 0,0 // The SonicBoom gauge
gauge27=COP_Sound!dsd_xml_sound3, 0,0,,, ./gauges/rcb-miljet/COP_Sound.ini // Plays sounds
In the aircraft.cfg [lights] section ....
light.14 = 10, 14.00, 0.00, 0.00, fx_RCB_machenvlop,1 // SonicBoom effect
Numbers of lights, gauges dependent on what's sequential in your configs....
gray eagle
SOH-CM-2025
Haven't bothered yet...but should be no different to any other plane....
In the panel.cfg...
// --------------------------------------------------- SONIC BOOM
gauge26=rcb-miljet!SonicBoomControl, 0,0 // The SonicBoom gauge
gauge27=COP_Sound!dsd_xml_sound3, 0,0,,, ./gauges/rcb-miljet/COP_Sound.ini // Plays sounds
In the aircraft.cfg [lights] section ....
light.14 = 10, 14.00, 0.00, 0.00, fx_RCB_machenvlop,1 // SonicBoom effect
Numbers of lights, gauges dependent on what's sequential in your configs....
Is this from the COP3/RCBCO-30 program?
Sorry, I still cannot get the AB to disconnect from the lights (all) switch. Have intermittently gotten the AB to light off the throttle BUT you get no response by first pushing the throttles to 100% but then they come on if you then pull back to about 70%. Other times they don't light at high throttle settings and on at low. Weird. Am using Don B.'s Pack 2 panel mods. Could you post your relevant panel.cfg entries? Thing is, I have so many different entries now from other aircraft that do work, it may be that there something I need to remove rather than add to get this to work!
Jafo
SOH-CM-2024
Again...am yet to mess with the AS 4s.....tho managed to get the 3 packs with OK VCs...so that's a start....
...but with 'most' AB issues...apart from totally missing effects in the effects folder... it's down to conflicting/multiple AB gauges in the panel and/or other controllers/gauges assigned to the lights section in the aircraft.cfg.
Step one....comment out ALL lights other than those that refer to 'AB' [most commonly a '9' ] and see if they behave/work.
Step two... systematically comment out each or every 'gauge' that has those typical effect co-ords...like 1,1,1,1 or similar [obviously not big enough to be a dial or button, etc].
Bit of trial and error....they're almost always fixable....
Edit....
Had a go with the pack3....added the C9 AB effects...on the co-ords of the previous page...no dramas...
Took out ALL effect 'actuators' in the panel and added my own...it originated from an Alpha F105 ....simple toggle gauge for a logo light [9] at 90% throttle.
Works as expected.
I tend to prefer the look of 'staged' burners...so the effect changes at set throttles...eg...20/50/90 ....again all simple light switches. The only issue is it's not then suitable to have other lights of the same class activated via panel switches....turn on a 'beakon' switch and suddenly your AB effects come on...
Last edited:
Jafo
SOH-CM-2024
Yep, that's what I thought. Have a whole variety of actuator gauges in the folder that I have tried eliminating one by one. Will do likewise with the lights.
Agree prefer staged effect + think I too get lights of the same class triggering them.
The Pack 3 models work perfectly for me but this has a different set up/VC/gauges from Pack 2. Thanks for your thoughts. Back to work . .
Jafo
SOH-CM-2024
I'll do likewise with the pack2....and post what I changed to get it working [if it wasn't]...
Jafo
SOH-CM-2024
View attachment 8451
That's a pack2 F4 with a staged AB...quick and dirty...probably better with refined co-ords.
AB stage is logo-triggered '9'... burner only is strobe '2'.... co-ords as with others.
It's always easier to rem out ALL included AB triggers in the panel and add ones you are used to/know work OK....likewise with any AB effects called up in the aircraft.cfg lights.
Mine came from the AS F105D and I edited and renamed them so every plane I fiddle with gets the same ones....unless there's a model SIZE issue with the buckets....
That's a pack2 F4 with a staged AB...quick and dirty...probably better with refined co-ords.
AB stage is logo-triggered '9'... burner only is strobe '2'.... co-ords as with others.
It's always easier to rem out ALL included AB triggers in the panel and add ones you are used to/know work OK....likewise with any AB effects called up in the aircraft.cfg lights.
Mine came from the AS F105D and I edited and renamed them so every plane I fiddle with gets the same ones....unless there's a model SIZE issue with the buckets....
Well I'm still struggling here, lol. That is the same Pack 2 model I am testing in your screenie. I tried that model with the Pack 1 panel and the AB low and behold triggered off the throttle correctly. That tells me it is not the model and not my lights entries. I am not sure what you mean by your burner only is a strobe 2. Importing and A/B testing the isolated gauge trigger that works with the Pack 1 Panel, fails to work with the Pack 2 panel - or sometimes -works in reverse, e.g., goes off at full throttle and on at low or idle. DOH! 
Panel entries I am using (or abusing):
//Panel Virt2DCB//
//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=128,128
visible=0
window_size= 1.000, 1.000
pixel_size=128,128
texture=$LHupper
window_pos= 1.000, 1.000
gauge00=F4_AB!SYSTEM_Onboard, 1,1,1,1 <<<this will="" allow="" throttle="" control="" of="" afterburner.
gauge01=SpeedControl!xml2ipc, 0, 0,
gauge02=RFN_CarrierGauge!TACAN_Navigation, 0, 0, 0, 0, Nav2
gauge03=RFN_CarrierGauge!CustomCatapult, 0, 0,
gauge04=RFN_CarrierGauge!Approach_Ctrl, 0, 0, 0, 0, 0.0
gauge05=DSD_Sound_Gauge!Sound, 0, 0,
gauge06=ARS4!TrafficInfo_AI4, 1,1,1,1
gauge07=ARS4!CarrierCtl_Gulf, 1,1,1,1 //See Note
gauge08=ALPHA_F-4_Phantom!Reheat_LOGO, 0,0,20,20 // THIS IS THE ONE THAT WORKED WITH THE PACK 1 PANEL
//gauge08=PhantomGaugesDCBx!AutoburnersDCB, 0,0,10,10
[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 = 3, -6.8, -19.37, -0.58, fx_shockwave_navred ,
light.1 = 3, -6.8, 19.37, -0.58, fx_shockwave_navgre ,
light.2 = 3, -11.02, -19.30, -0.72, fx_navredc ,
light.3 = 3, -11.02, 19.30, -0.72, fx_navgrec ,
light.4 = 3, -26.77, 0, 10.05, fx_shockwave_navwhi_l_old ,
light.5 = 4, 19.684, -0.723, 2.606, fx_shockwave_vclight_l,
light.6 = 4, 14.72, 0, 2.606, fx_shockwave_vclight_l,
light.7 = 2, 9.55, 0, 4.88, fx_shockwave_beacon_rotating_red ,
light.8 = 2, -15.94, 0, 7.31, fx_shockwave_beacon_rotating_red ,
//light.9 = 2,-11.04, -19.30, -0.58, fx_shockwave_strobe ,
//light.10 = 2, -11.04, 19.30, -0.58, fx_shockwave_strobe_2 ,
light.11 = 7, -11.5,-19.2, -0.68, fx_contrail_Alpha Phantom ,
light.12 = 7, -11.5, 19.2, -0.68, fx_contrail_Alpha Phantom ,
light.13 = 9, -8.50, -2.20, -0.74, fx_F4E_C9AB //fx_burner2 ,
//light.14 = 9, -12.50, -2.20, -0.74, fx_F-15reheateffect ,
light.15 = 9, -8.50, 2.20, -0.74, fx_F4E_C9AB //fx_burner2 ,
//light.16 = 9, -12.50, 2.20, -0.74, fx_F-15reheateffect ,
//light.16 = 9, -12.50, -2.20, -0.74, fx_engine_Virtavia Phantom ,
//light.14 = 9, -8.50, -2.20, -0.74, fx_F4E_C9AB///fx_reheat_Virtavia Phantom , <<<< First set of numbers (in red) was a guesstimate
//light.17 = 9, -12.50, 2.20, -0.74, fx_engine_Virtavia Phantom ,
//light.16 = 9, -8.50, 2.20, -0.74, fx_F4E_C9AB///fx_reheat_Virtavia Phantom , <<< when light 14 looked to be OKAY, I change this line to match.
//light.13 = 9, -12.50, -2.20, -1.84, fx_dsb_tornadoflame ,
//light.14 = 9, -12.50, -2.20, -0.54, fx_tornado_aniburner ,
//light.15 = 9, -12.50, 2.20, -1.84, fx_dsb_tornadoflame ,
//light.16 = 9, -12.50, 2.20, -0.54, fx_tornado_aniburner ,
//light.17= 10, -10.0, 0.0, 0.0, fx_RCB_machenvlop,1 // SonicBoom effect
//light.18 =10, -16.4, -2.25, -3.40, fx_F4E_C9AB_N ;MOD, burner 1 nighttime flame
//light.19 =10, -16.4, 2.25, -3.40, fx_F4E_C9AB_N ;MOD, burner 2 nighttime flame
//--------------------------------------------------------
[Vcockpit02]
file=VC2-2.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$pan1
gauge00=Boeing747-400!Master Warning Light, 929,151,61,34
gauge01=Virtavia_F-4_Phantom!Airbrake, 36,304,29,29
gauge02=Virtavia_F-4_Phantom!Tailhook, 59,233,30,30
gauge03=PhantomGaugesDCBx!F4 HSI AFCS Rotary, 622,493,169,107
gauge04=SimIcons1024!GPS Icon, 368,388,25,25
gauge05=SimIcons1024!ECU Icon, 368,356,25,25
gauge06=SimIcons1024!Map Icon, 368,421,25,25
gauge07=SimIcons1024!Avionics Icon, 238,467,25,25
gauge08=SimIcons1024!ATC Icon, 238,532,25,25
gauge09=SimIcons1024!Kneeboard Icon, 238,499,25,25
gauge10=PhantomGaugesDCBx!F4 Attitude, 409,184,202,208
gauge11=PhantomGaugesDCBx!F4 HSI, 409,397,202,214
gauge12=PhantomGaugesDCBx!F4 VSI, 646,353,130,133
gauge13=PhantomGaugesDCBx!F4 Fuel Digital, 802,134,98,98
gauge14=PhantomGaugesDCBx!F4 TAS Digital, 117, 98 ,85,85
gauge15=PhantomGaugesDCBx!F4 Nozzle E1, 804,547,100,100
gauge16=PhantomGaugesDCBx!F4 Nozzle E2, 909,549,100,100
gauge17=PhantomGaugesDCBx!F4 RadAlt Insert, 88,189,150,150
gauge18=PhantomGaugesDCBx!F4 Altimeter, 628,191,156,156
gauge19=PhantomGaugesDCBx!F4 AFCS Small, 805,20,95,110
gauge20=PhantomGaugesDCBx!F4 CpBl Light Switches, 728,616,64,37
gauge21=PhantomGaugesDCBx!F4 NSL Light Switches, 621,616,93,35
gauge22=PhantomGaugesDCBx!F4 Number Plaque, 914,48,80,20
gauge23=PhantomGaugesDCBx!F4 Roll Pitch Yaw Hold, 913,84,85,45
gauge24=PhantomGaugesDCBx!F4 Radio DME 1, 424,614,165,22
gauge25=PhantomGaugesDCBx!F4 Radio DME 2, 424,638,165,22
gauge26=PhantomGaugesDCBx!F4 MachMeter Insert Lg, 251,191,150,155
gauge27=PhantomGaugesDCBx!F4 Fuel Flow E1, 805,232,101,101
gauge28=PhantomGaugesDCBx!F4 Fuel Flow E2, 913,231,101,101
gauge29=PhantomGaugesDCBx!F4 RPM E1, 804,337,101,101
gauge30=PhantomGaugesDCBx!F4 RPM E2, 913,336,101,101
gauge31=PhantomGaugesDCBx!F4 Turb Temp E1, 806,441,101,101
gauge32=PhantomGaugesDCBx!F4 Turb Temp E2, 915,440,101,101
gauge33=PhantomGaugesDCBx!F4 Afterburner Ind, 934,197,54,27
gauge34=PhantomGaugesDCBx!F4 G Meter, 271,460,100,100
gauge35=RFN_CarrierGauge!Aircraft_Carrier_Indicator, 248,346,110,112
//gauge35=PhantomGaugesDCBx!F4 RMI, 248,346,110,112
gauge36=Virtavia_F4_Extragauge!SWP_Fire1, 16,143,60,30
gauge37=Virtavia_F4_Extragauge!SWP_Fire2, 16,173,60,30
//gauge38=Phantom_X!Engine_FX, 10,10,10,10 // NOT SURE WHAT THIS DOES
//gauge39=PhantomGaugesDCBV5!F4 Afterburner Follower, 40,0,20,20
//gauge39=ALPHA_Crusader!Reheat_Auto_LOGO, 0,0,20,20
gauge38=ARS4!TrafficInfo_AI4, 1,1,1,1
gauge39=ARS4!CarrierCtl_Gulf, 1,1,1,1 //See Note
//--------------------------------------------------------</this>
Panel entries I am using (or abusing):
//Panel Virt2DCB//
//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=128,128
visible=0
window_size= 1.000, 1.000
pixel_size=128,128
texture=$LHupper
window_pos= 1.000, 1.000
gauge00=F4_AB!SYSTEM_Onboard, 1,1,1,1 <<<this will="" allow="" throttle="" control="" of="" afterburner.
gauge01=SpeedControl!xml2ipc, 0, 0,
gauge02=RFN_CarrierGauge!TACAN_Navigation, 0, 0, 0, 0, Nav2
gauge03=RFN_CarrierGauge!CustomCatapult, 0, 0,
gauge04=RFN_CarrierGauge!Approach_Ctrl, 0, 0, 0, 0, 0.0
gauge05=DSD_Sound_Gauge!Sound, 0, 0,
gauge06=ARS4!TrafficInfo_AI4, 1,1,1,1
gauge07=ARS4!CarrierCtl_Gulf, 1,1,1,1 //See Note
gauge08=ALPHA_F-4_Phantom!Reheat_LOGO, 0,0,20,20 // THIS IS THE ONE THAT WORKED WITH THE PACK 1 PANEL
//gauge08=PhantomGaugesDCBx!AutoburnersDCB, 0,0,10,10
[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 = 3, -6.8, -19.37, -0.58, fx_shockwave_navred ,
light.1 = 3, -6.8, 19.37, -0.58, fx_shockwave_navgre ,
light.2 = 3, -11.02, -19.30, -0.72, fx_navredc ,
light.3 = 3, -11.02, 19.30, -0.72, fx_navgrec ,
light.4 = 3, -26.77, 0, 10.05, fx_shockwave_navwhi_l_old ,
light.5 = 4, 19.684, -0.723, 2.606, fx_shockwave_vclight_l,
light.6 = 4, 14.72, 0, 2.606, fx_shockwave_vclight_l,
light.7 = 2, 9.55, 0, 4.88, fx_shockwave_beacon_rotating_red ,
light.8 = 2, -15.94, 0, 7.31, fx_shockwave_beacon_rotating_red ,
//light.9 = 2,-11.04, -19.30, -0.58, fx_shockwave_strobe ,
//light.10 = 2, -11.04, 19.30, -0.58, fx_shockwave_strobe_2 ,
light.11 = 7, -11.5,-19.2, -0.68, fx_contrail_Alpha Phantom ,
light.12 = 7, -11.5, 19.2, -0.68, fx_contrail_Alpha Phantom ,
light.13 = 9, -8.50, -2.20, -0.74, fx_F4E_C9AB //fx_burner2 ,
//light.14 = 9, -12.50, -2.20, -0.74, fx_F-15reheateffect ,
light.15 = 9, -8.50, 2.20, -0.74, fx_F4E_C9AB //fx_burner2 ,
//light.16 = 9, -12.50, 2.20, -0.74, fx_F-15reheateffect ,
//light.16 = 9, -12.50, -2.20, -0.74, fx_engine_Virtavia Phantom ,
//light.14 = 9, -8.50, -2.20, -0.74, fx_F4E_C9AB///fx_reheat_Virtavia Phantom , <<<< First set of numbers (in red) was a guesstimate
//light.17 = 9, -12.50, 2.20, -0.74, fx_engine_Virtavia Phantom ,
//light.16 = 9, -8.50, 2.20, -0.74, fx_F4E_C9AB///fx_reheat_Virtavia Phantom , <<< when light 14 looked to be OKAY, I change this line to match.
//light.13 = 9, -12.50, -2.20, -1.84, fx_dsb_tornadoflame ,
//light.14 = 9, -12.50, -2.20, -0.54, fx_tornado_aniburner ,
//light.15 = 9, -12.50, 2.20, -1.84, fx_dsb_tornadoflame ,
//light.16 = 9, -12.50, 2.20, -0.54, fx_tornado_aniburner ,
//light.17= 10, -10.0, 0.0, 0.0, fx_RCB_machenvlop,1 // SonicBoom effect
//light.18 =10, -16.4, -2.25, -3.40, fx_F4E_C9AB_N ;MOD, burner 1 nighttime flame
//light.19 =10, -16.4, 2.25, -3.40, fx_F4E_C9AB_N ;MOD, burner 2 nighttime flame
//--------------------------------------------------------
[Vcockpit02]
file=VC2-2.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$pan1
gauge00=Boeing747-400!Master Warning Light, 929,151,61,34
gauge01=Virtavia_F-4_Phantom!Airbrake, 36,304,29,29
gauge02=Virtavia_F-4_Phantom!Tailhook, 59,233,30,30
gauge03=PhantomGaugesDCBx!F4 HSI AFCS Rotary, 622,493,169,107
gauge04=SimIcons1024!GPS Icon, 368,388,25,25
gauge05=SimIcons1024!ECU Icon, 368,356,25,25
gauge06=SimIcons1024!Map Icon, 368,421,25,25
gauge07=SimIcons1024!Avionics Icon, 238,467,25,25
gauge08=SimIcons1024!ATC Icon, 238,532,25,25
gauge09=SimIcons1024!Kneeboard Icon, 238,499,25,25
gauge10=PhantomGaugesDCBx!F4 Attitude, 409,184,202,208
gauge11=PhantomGaugesDCBx!F4 HSI, 409,397,202,214
gauge12=PhantomGaugesDCBx!F4 VSI, 646,353,130,133
gauge13=PhantomGaugesDCBx!F4 Fuel Digital, 802,134,98,98
gauge14=PhantomGaugesDCBx!F4 TAS Digital, 117, 98 ,85,85
gauge15=PhantomGaugesDCBx!F4 Nozzle E1, 804,547,100,100
gauge16=PhantomGaugesDCBx!F4 Nozzle E2, 909,549,100,100
gauge17=PhantomGaugesDCBx!F4 RadAlt Insert, 88,189,150,150
gauge18=PhantomGaugesDCBx!F4 Altimeter, 628,191,156,156
gauge19=PhantomGaugesDCBx!F4 AFCS Small, 805,20,95,110
gauge20=PhantomGaugesDCBx!F4 CpBl Light Switches, 728,616,64,37
gauge21=PhantomGaugesDCBx!F4 NSL Light Switches, 621,616,93,35
gauge22=PhantomGaugesDCBx!F4 Number Plaque, 914,48,80,20
gauge23=PhantomGaugesDCBx!F4 Roll Pitch Yaw Hold, 913,84,85,45
gauge24=PhantomGaugesDCBx!F4 Radio DME 1, 424,614,165,22
gauge25=PhantomGaugesDCBx!F4 Radio DME 2, 424,638,165,22
gauge26=PhantomGaugesDCBx!F4 MachMeter Insert Lg, 251,191,150,155
gauge27=PhantomGaugesDCBx!F4 Fuel Flow E1, 805,232,101,101
gauge28=PhantomGaugesDCBx!F4 Fuel Flow E2, 913,231,101,101
gauge29=PhantomGaugesDCBx!F4 RPM E1, 804,337,101,101
gauge30=PhantomGaugesDCBx!F4 RPM E2, 913,336,101,101
gauge31=PhantomGaugesDCBx!F4 Turb Temp E1, 806,441,101,101
gauge32=PhantomGaugesDCBx!F4 Turb Temp E2, 915,440,101,101
gauge33=PhantomGaugesDCBx!F4 Afterburner Ind, 934,197,54,27
gauge34=PhantomGaugesDCBx!F4 G Meter, 271,460,100,100
gauge35=RFN_CarrierGauge!Aircraft_Carrier_Indicator, 248,346,110,112
//gauge35=PhantomGaugesDCBx!F4 RMI, 248,346,110,112
gauge36=Virtavia_F4_Extragauge!SWP_Fire1, 16,143,60,30
gauge37=Virtavia_F4_Extragauge!SWP_Fire2, 16,173,60,30
//gauge38=Phantom_X!Engine_FX, 10,10,10,10 // NOT SURE WHAT THIS DOES
//gauge39=PhantomGaugesDCBV5!F4 Afterburner Follower, 40,0,20,20
//gauge39=ALPHA_Crusader!Reheat_Auto_LOGO, 0,0,20,20
gauge38=ARS4!TrafficInfo_AI4, 1,1,1,1
gauge39=ARS4!CarrierCtl_Gulf, 1,1,1,1 //See Note
//--------------------------------------------------------</this>
Jafo
SOH-CM-2024
expat....
You missed the important point of getting an AB effect to work....when the one that you have with the plane doesn't.
Assume ALL entries relating to the AB/exhaust/burner in BOTH the aircraft.cfg AND the panel.cfg are wrong.
Delete them by adding // in front.
Then and ONLY then... add effects to the lights section that you know work as you like them...AND their corresponding trigger gauge/s in the panel.
Make absolutely certain NOTHING is trying to use the same light type.... what is meant by logo-light...aka 9, or [as I mentioned I used for the first-stage trigger] the strobe-light ...aka 2.
The only lights listed in the aircraft.cfg attributed to '9' [the light type, not the number of the light] must be for your afterburner effects as the AB 'trigger' gauges are [almost] invariably set to switch-toggle the logo-light.
If you have another aircraft with functioning AB effects controlled by the panel.cfg and light section [and NOT hard-coded into the model] you can swap them into this one....just as long as you comment out ALL the existing triggers and effects.
I added functional ones to the 'stock' Pack 2 set...[readme dates to 27/01/2011] ...no problem at all...
EDit...
that reheat_LOGO in the panel isn't ideal...it's better to at least grab one that's set to a percentage of throttle....like 90% ....that one's more like an on-off switch...
...and part of the 'diagnosis' would require all the effect gauges to be commented out...to be sure none of them is in conflict [they are the ones with queer coordinates...like 1,1,1,1 etc]..
You missed the important point of getting an AB effect to work....when the one that you have with the plane doesn't.
Assume ALL entries relating to the AB/exhaust/burner in BOTH the aircraft.cfg AND the panel.cfg are wrong.
Delete them by adding // in front.
Then and ONLY then... add effects to the lights section that you know work as you like them...AND their corresponding trigger gauge/s in the panel.
Make absolutely certain NOTHING is trying to use the same light type.... what is meant by logo-light...aka 9, or [as I mentioned I used for the first-stage trigger] the strobe-light ...aka 2.
The only lights listed in the aircraft.cfg attributed to '9' [the light type, not the number of the light] must be for your afterburner effects as the AB 'trigger' gauges are [almost] invariably set to switch-toggle the logo-light.
If you have another aircraft with functioning AB effects controlled by the panel.cfg and light section [and NOT hard-coded into the model] you can swap them into this one....just as long as you comment out ALL the existing triggers and effects.
I added functional ones to the 'stock' Pack 2 set...[readme dates to 27/01/2011] ...no problem at all...
EDit...
that reheat_LOGO in the panel isn't ideal...it's better to at least grab one that's set to a percentage of throttle....like 90% ....that one's more like an on-off switch...
...and part of the 'diagnosis' would require all the effect gauges to be commented out...to be sure none of them is in conflict [they are the ones with queer coordinates...like 1,1,1,1 etc]..
hschuit
SOH-CM-2024
FYI some mods which enable the dragchute with sets 1/2.
It bypasses the Concord Visor keys and add simulated chute drag:
Deploy dragchute: Press FSX Thrust Reverser key (F2)
Drop dragchute: Throttle up a bit to idle
Edit: You may want to disable the overspeed warning sound, using the AIR file concorde type forces the Vmo - Overspeed warning at 350-400 KIAS.
It bypasses the Concord Visor keys and add simulated chute drag:
Deploy dragchute: Press FSX Thrust Reverser key (F2)
Drop dragchute: Throttle up a bit to idle
Edit: You may want to disable the overspeed warning sound, using the AIR file concorde type forces the Vmo - Overspeed warning at 350-400 KIAS.
Attachments
Last edited:
Jafo
SOH-CM-2024
harrybasset
Charter Member
Thank you very much for this drag chute addition. I've installed it as the Readme and the chute deploys. I now seem to have lost the full throttle afterburner light up, has anyone else noticed this?
hschuit
SOH-CM-2024
I think your Phantom install is not happy with some of the FSX specific lines in my [TurbineEngineData] update. Try to go back to your previous aircraft.cfg [TurbineEngineData] entries, only make sure this line is included there, it is needed for the dragchute effect:
reverser_available=1