PDA

View Full Version : C9 Phantom in FSX



Jetmechanic
October 4th, 2008, 15:18
I finally got my Cloud 9 F-4 Phantom in FS9 and copyed and pasted the F-4 files for FS9 to FSX. The F-4 shows up and i can fly it but my screen automatically goes to half screen when ever I fly the F-4 or any other plane after it. Now if i select and plane but the C9 F-4 the screen is fine. Can anyone help. I see the external lights look better in FSX then in FS9. I know the Phantom is for FS9 only.

Dangerous Beans
October 4th, 2008, 16:30
Open the panel.cfg with notepad and delete the render_3d_window=1 line in the [Window00] section, that should fix it.

IanHenry
October 5th, 2008, 00:56
Hi Jet,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
Are you using SP2/ Acceleration, and how are the flight dynamics. Are there any further steps needed to complete the transfer? It would be great to see this aircraft in FSX.<o:p></o:p>
<o:p> </o:p>
Regards,<o:p></o:p>
Ian<o:p></o:p>
<o:p> </o:p>

Jetmechanic
October 6th, 2008, 02:12
Sorry guys I havent had anytime to try out the Fix for the Phantom I will have some time on tuesday evening. Gotta work. Anyway I am using SP2/ Acceleration. And the flight dynamics are pretty good I havent noticed anything different from the fs9 version. I do need to copy and paste the effect files for the After burner from FS9 to FSX and we willl see. But thanks for the HELP Dangerous Beans. I will let everyone know how it works in a few days.

Phantoms Phorever

Jetmechanic
October 8th, 2008, 04:42
I confirm Dangerous Beans says just edit the panel cfg. file and it works awesome. I need to put the effects file into the FSx folder see how it works.

Phantoms Phorever

Vigilius
October 8th, 2008, 08:30
Ok, the Phantom flies with this method but no VC and not 2D cockpit; only to take very good screenshots

Bone
October 8th, 2008, 08:38
I only use the VR cockpit so deleting the "render_3d_window=1" line didn't help. To make the black stripe go away I had to change the default view in the panel.cfg.

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

Also, most of the guages didn't work for me, so I used the Alphasim F-104 and F-5 guages, along with tweeking some coordinates.

[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024, 1024
texture=$vcmain
gauge00=ALPHA_F5!ATT, 385,470,248,247,LOW VC
gauge01=ALPHA_F104!ALT_US2, 640,480,136,135,VC
gauge02=ALPHA_F5!RALT, 112,495,117,117,VC
gauge03=ALPHA_F5!ASI, 249,483,132,133,VC
gauge04=ALPHA_F5!VSI, 680,649,98,98,VC
gauge05=ALPHA_F5!HSI, 380,728,248,210,LOW VC
gauge06=ALPHA_F5!ATT2, 644,758,138,138,VC
gauge07=ALPHA_F5!AoA, 276,637,101,101,1 VC
gauge08=ALPHA_F5!G_meter, 104,383,93,93,VC
gauge09=ALPHA_F5!fuel_gauge, 914,460,110,110,VC
gauge10=ALPHA_F5!EGT1, 802,673,93,93,1 VC
gauge11=ALPHA_F5!Nozzle_1, 807,771,93,93,1 VC
gauge12=ALPHA_F5!FF_1, 800,863,93,93,1 VC
gauge13=ALPHA_F5!N2RPMTURB1, 802,574,93,93,VC
gauge14=ALPHA_F5!EGT2, 901, 673 ,93,93,2 VC
gauge15=ALPHA_F5!Nozzle_2, 905,771,93,93,2 VC
gauge16=ALPHA_F5!FF_2, 900,863,93,93,2 VC
gauge17=ALPHA_F5!N2RPMTURB2, 900,574,93,93,VC
gauge18=ALPHA_F5!OilPress, 644,907,58,58,1 VC
gauge19=ALPHA_F5!OilPress, 715,907,58,58,2 VC
gauge20=ALPHA_F5!ILS Radar, 402,230,204,203,VC
gauge21=f4!CLICKABLE AREA, 885,476,22,22,VC
gauge22=cloud9 Phantom\f4!RADAR SWITCH, 646,367,55,,VC
gauge23=cloud9 Phantom\f4!ALT. HOLD LAMP, 643,279,34,72,VC
gauge24=cloud9 Phantom\f4!TARGET LAMP, 338,278,33,72,VC
gauge25=cloud9 Phantom\f4!RANGE LAMP, 638,233,125,18,VC
gauge26=cloud9 Phantom\f4!RADAR RETICLE SWITCH, 730,316,29,,VC
gauge27=cloud9 Phantom\f4!RANGE DIGIT, 688,289,34,16,VC
gauge28=ALPHA_F5!Compass, 812,13,201,135,VC
gauge29=cloud9 Phantom\f4!CLOCK, 11,879,131,,VC

Barvan40
October 8th, 2008, 09:19
The model looks great for screenies, but changing out the gauges makes you loose all the systems modeled for FS9 and it no longer operates anywhere close to the way it works in FS9.

It is like taking the A2A Simulations Accu-sim Expansion Pack out of the A2A Wings of Silver Boeing 377 Stratocruiser. It still flies, but it ain't even close to realistic.

Hopefully someday somebody will do a full FSX Phantom with the same realism as the C9 version.

Barry

Bone
October 8th, 2008, 09:41
The radar doesn't work the same, the canopy won't open, the ejection sequence is only half there, and you don't get the gear warning horn...however, the rest of it works and fly's really good.

There were many different versions of the phantom, resulting in many differences in the way they flew, how the systems worked, and instrumentation configs...so I just see porting the C9 phantom over to fsx as just another difference. The 1960's F-4B and the current Phantom flown by Israel have so many differences they could be classified as different types altogether.

I do agree, we need a true FSX Phantom!


http://i275.photobucket.com/albums/jj299/theBone11/2008-10-8_12-54-56-283.jpg

IanHenry
October 8th, 2008, 13:11
I’ve copied the aircraft, gauge folder and effects into FSX, but every time I select one of the Phantoms I get a crash to desktop! Has enyone got any ideas what my problem is? :isadizzy:
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p> </o:p>
Ian

rsgunner
October 8th, 2008, 14:28
I’ve copied the aircraft, gauge folder and effects into FSX, but every time I select one of the Phantoms I get a crash to desktop! Has enyone got any ideas what my problem is? :isadizzy:
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
Ian

FSX seems to not like some of the FS9 gauges. That is the same thing I experienced. Looking forward to a FSX version of an F-4 someday.

IanHenry
October 8th, 2008, 21:11
RS,
I think that would be a dream,but I think we may have a long wait!

Ian

PJMack
August 11th, 2011, 10:12
I am trying to get the Cloud 9 canopy to work in fsx. Any ideas?

Thank you:salute:

doublecool
August 12th, 2011, 03:30
cool aircraft, but has anyone got the after burner working :jump:
never been able to figure that one out

doublecool
August 16th, 2011, 15:48
Please any ones help

here is lighting config
46116
[lights]
light.0 = 3, -16.43, -19.2, -3.00, fx_navred
light.1 = 3, -16.43, 19.2, -3.00, fx_navgre
light.2 = 1, -35.30, 0.00, 7.35, fx_navwhi
light.3 = 9, -21.11, 2.40, -4.60, fx_mirageN_TORCH_FLAM
light.4 = 10, -21.11, -2.40, -4.60, fx_mirageN_TORCH_FLAM
//light.5 = 8, -22.45, 18.85, -3.00, c9F4_contrail
//light.6 = 8, -22.45,-18.85, -3.00, c9F4_contrail
//light.7 =10, 9.70, 0.00, -0.90, fx_vclight
//light.8 =10, 7.10, 0.00, 0.15, fx_vclight
light.9 = 2, 0.30, 0.00, 1.55, c9f4_strobew
light.10 = 2, 3.35, -3.35, -5.00, c9f4_strobew
light.11 = 2, 3.35, 3.35, -5.00, c9f4_strobew
light.12 = 2, -24.40, 0.00, 3.80, fx_beacon
light.13 = 7, 0.30, 0.00, 1.55, fx_navwhi
light.14 = 7, 3.35, -3.35, -4.80, fx_navwhi
light.15 = 7, 3.35, 3.35, -4.80, fx_navwhi
light.16 = 1, -24.40, 0.00, 3.80, fx_navred
light.17 = 2, -35.30, 0.00, 7.35, c9f4_strobew
light.18 = 10, -21.11, 2.40, -4.00, cs18_ab
light.19 = 11,-21.11, -2.40, -4.00, cs18_ab


USED CAPT SIM AB EFFECT... SORRY TRIED TO!

fxsttcb
August 17th, 2011, 03:41
cool aircraft, but has anyone got the after burner working :jump:
never been able to figure that one out
I don't know what kind of control gauge C9 uses, but, AFAIK, FSX itself only recognizes the following "types";
[LIGHTS]
Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi light, 7=recognition light, 8=wing light, 9=logo light

The ordering in the aircraft.cfg is:
Light.ID=Type, F/A, L/R, U/D, effect

In what you posted, "light.4 = 10, -21.11, -2.40, -4.60, fx_mirageN_TORCH_FLAM" is identified as type=10.
It is tied to the left engine afterburner effect. No such type that I'm aware of!

This is what you have(sorted and typed);
[lights]
light.0 = 3, -16.43, -19.2, -3.00, fx_navred //NAV
light.1 = 3, -16.43, 19.2, -3.00, fx_navgre //NAV
light.2 = 1, -35.30, 0.00, 7.35, fx_navwhi //Beacon
light.3 = 9, -21.11, 2.40, -4.60, fx_mirageN_TORCH_FLAM //LOGO
light.4 = 10, -21.11, -2.40, -4.60, fx_mirageN_TORCH_FLAM //UNKNOWN TYPE
light.10 = 2, 3.35, -3.35, -5.00, c9f4_strobew //Strobe
light.11 = 2, 3.35, 3.35, -5.00, c9f4_strobew //Strobe
light.12 = 2, -24.40, 0.00, 3.80, fx_beacon //Strobe
light.13 = 7, 0.30, 0.00, 1.55, fx_navwhi //Recognition
light.14 = 7, 3.35, -3.35, -4.80, fx_navwhi //Recognition
light.15 = 7, 3.35, 3.35, -4.80, fx_navwhi //Recognition
light.16 = 1, -24.40, 0.00, 3.80, fx_navred //Beacon
light.17 = 2, -35.30, 0.00, 7.35, c9f4_strobew //Strobe

I don't have the C9 Phantom, so, I don't have the original [Lights] section, or know what kind of gauge controls the burners effects.
For all I know, the control could be coded in the model.

***********************************
If you want a different control, download my Virtavia Phantom Pack 2 complete panel. Inside it is an Afterburner gauge set that works for FSX.
Both F4 Afterburner Ind.xml(Two Lights; Armed, Engaged) and F4 Afterburner Arm.xml(Toggle switch) are mouseable visible gauges. You can use either one, or, both.
They will enable AutoburnersDCB.xml(invisible, VC) which if enabled will "light" the burners individually at their 90%+ Throttle setting.
If not enabled, full military thrust is available.

With the noted aircraft.cfg settings in the read me, afterburner engagement fuel flow will skyrocket, forcing you to manage their use, or have "unlimited Fuel".

They are a controller set that uses/controls: WING, LOGO, TAXI, AND RECOGNITION lights.
Other native switches/controls that uses/control those lights may conflict.

WING(Eng 1) and LOGO(Eng 2) are "lit" any time the engine is running at over 10% RPM, and can be used for smoke or other effect that is enable anytime the engine is running.

TAXI(Eng 1) and RECOGNITION(Eng 2) are "lit" any time the throttle is set at over 90% AND Afterburner is armed.

To use my stuff, it is absolutely imperative that any other afterburner(Lights) control is removed.

You can usually find a conflicting gauge in the panel.cfg
If you want to pursue this I might be able to help...Don

FSX68
August 17th, 2011, 07:18
Another option is to use the now Freeware Virtavia F-4 (FS9)
it has all three packs. For the cockpit at least for pack2 use the
Virtavia F-4 Phantom Package 2 Complete FSX Panel

http://www.sim-outhouse.com/sohforums/local_links.php?catid=117&linkid=4486

It works for pack two as advertised but it don't work for packs 1/3. Don't know
why. The cockpit works nice. (at least for pack 2) maybe someone here
can investigate what the cockpit won't work for the other packs.


:wiggle::wiggle:

delta_lima
August 17th, 2011, 07:30
Another option is to use the now Freeware Virtavia F-4 (FS9)
it has all three packs. For the cockpit at least for pack2 use the
Virtavia F-4 Phantom Package 2 Complete FSX Panel

http://www.sim-outhouse.com/sohforums/local_links.php?catid=117&linkid=4486

It works for pack two as advertised but it don't work for packs 1/3. Don't know
why. The cockpit works nice. (at least for pack 2) maybe someone here
can investigate what the cockpit won't work for the other packs.


:wiggle::wiggle:

The reason pack 2's cockpit fixes don't apply to the other three is thus:

1) Pack 1 has it's own FSX panel fix: http://www.sim-outhouse.com/sohforums/local_links.php?action=jump&catid=117&id=3598

2) Pack 3 panel works fine as is.

dl

fxsttcb
August 17th, 2011, 11:39
Beyond that, the fact is, that all 3 Packages use different models.
They have different shapes with slightly different mapping of the textures for the VC, gauge positioning, and external visuals...Don

expat
August 18th, 2011, 01:12
I have all three - Virtavia/Alphasim, Cloud9 and IRIS and prefer by far the Virtavia F-4s, in part because I like USN/USMC birds and the visual model for the F-4B/J looks the most correct and the large number of great paints available. The mods required for porting over to FSX can be found here and are easy. I actually have all the models from Packs 1-3 in one a/c folder, using a variety of panel model/load out alternatives.

fxsttcb
August 18th, 2011, 02:01
After studying a few other plane's [Lights] sections I have found what light type "10" is!
I've found that it responds to the "Cabin Lights" Variable (A:LIGHT CABIN,bool).

Not many airliners get much attention from me, but my beloved Falcon 50 uses it.
How embarrassing! I should know it, I coded it, for Heavens sake...Don

FSX68
August 18th, 2011, 11:04
I downloaded links you all provided and installed the panel/cockpit fix and
my only problem is that both the afterburner and exterior lights come on when the "L" lights key
is pressed. To turn off the burner press "L" again and exterior lights go out. Wierd eh?
Now I did find a pack 3 panel fix (simviation) that is a horse of diffrent color. The
burners work independent of lights. With Pack 1 and two fixes burner
will come on when L key is pressed and burner comes on even in stall.

I read the readme for the Pack 2 kit and a lot of cut and paste to the
(Lights) section. Some of which look to be something to do with the burners.

Wonder if Dino's F14 burners would work?

FSX68
August 18th, 2011, 12:00
I have all three - Virtavia/Alphasim, Cloud9 and IRIS and prefer by far the Virtavia F-4s, in part because I like USN/USMC birds and the visual model for the F-4B/J looks the most correct and the large number of great paints available. The mods required for porting over to FSX can be found here and are easy. I actually have all the models from Packs 1-3 in one a/c folder, using a variety of panel model/load out alternatives.

Do you have afterburners visable only when the "L" lights key is pressed. I do for either
pack 1 or two.

expat
August 18th, 2011, 12:43
Do you have afterburners visable only when the "L" lights key is pressed

I have AB now working with full throttle - not hooked to lights or an AB button - but can't say when or how I did this. :ques:

fxsttcb
August 18th, 2011, 15:23
I read the readme for the Pack 2 kit and a lot of cut and paste to the
(Lights) section. Some of which look to be something to do with the burners.In my Pack 1 fix, it is a new Panel Folder placement and copy/paste the contents of the original.
For every Pack 1 livery that you want a VC to show properly, you have to change the panel= line in the aircraft.cfg or use the alternate installation method which doesn't preserve the original panel folder.
No [Lights] changes.

In the Pack 2 fix it is copy 3 new files and 2 Virtavia .cabs to the panel folder.
Again, no [Lights] changes.

In the Pack 2 complete panel download, for the [lights] section in the readme there is no cut/paste.
It is a complete replacement of the lights section or just the afterburners portion.
There are some other hoops to jump through and decisions to make.
That is par for a port-over upgrade from FS9 to FSX.


I have AB now working with full throttle - not hooked to lights or an AB button - but can't say when or how I did this.That Sir, is very intriguing! Other than a few planes that have the AB effect coded in the model(F/A-18, Dino's F-14D, and others I'm sure), there isn't a way without using [Lights] that I'm aware of.
The AB thrust and fuel flow functions will be there with a proper [TurbineEngineData] section, but not the visual effect.

Would you mind sending me your panel.cfg, aircraft.cfg and .air file?
Maybe I can decipher how it works for you, and share the find!...Don

FSX68
August 18th, 2011, 16:27
FSXTTCB,

When you get all this info I would like if you would share this info. I am very curious
myself. Thanks much....:wavey:

FSX68
August 18th, 2011, 16:29
That Sir, is very intriguing! Other than a few planes that have the AB effect coded in the model(F/A-18, Dino's F-14D, and others I'm sure), there isn't a way without using [Lights] that I'm aware of.
The AB thrust and fuel flow functions will be there with a proper [TurbineEngineData] section, but not the visual effect.

Would you mind sending me your panel.cfg, aircraft.cfg and .air file?
Maybe I can decipher how it works for you, and share the find!...Don


When you get all this info I would like if you do share this info. I am very curious
myself. Thanks much....:wavey:[/QUOTE]

ZsoltB
August 18th, 2011, 21:12
I do not open the canopy
Does not work parachute
Does not work covers, ribbons

I would be happy if Vertigo Studios doing it the phantom!

expat
August 19th, 2011, 01:36
As mentioned, I have all three "Packs" in one airplane folder and just counted ten different panel folders I have accumulated.

This is the one I use most currently and lights the burners through the throttles:

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Tuesday, February 01, 2005 at 08:50 FSPS Build:15838
[Window Titles]
Window00=Main Panel
Window01=GPS
Window02=Throttle Quadrant
Window03=RADIO_STACK_PANEL
Window04=HUD Dark
Window05=HUD Normal
Window06=HUD Bright
Window07=COP Control Panel
[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,GPS_PANEL,THROTTLE _PANEL,RADIO_STACK_PANEL,20,21,22
VIEW_FORWARD_ZOOM=0.500
VIEW_FORWARD_DIR=5.000, 0.000, 0.000
VIEW_FORWARD_RIGHT_ZOOM=0.500
VIEW_RIGHT_ZOOM=0.500
VIEW_REAR_RIGHT_ZOOM=0.500
VIEW_REAR_LEFT_ZOOM=0.500
VIEW_LEFT_ZOOM=0.500
VIEW_FORWARD_LEFT_ZOOM=0.500

//--------------------------------------------------------
[Window00]
file=main panel.bmp
Background_color=0,0,0
size_mm=1024
window_size_ratio=1.000
position=7
visible=1
ident=MAIN_PANEL
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=Boeing747-400!Master Warning Light, 802,429,50,31
gauge01=SimIcons1024!ECU Icon, 409,593,19,19
gauge02=SimIcons1024!GPS Icon, 409,615,19,19
gauge03=SimIcons1024!Radio Icon, 315,695,19,19
gauge04=SimIcons1024!Map Icon, 409,637,19,19
gauge05=SimIcons1024!ATC Icon, 315,673,19,19
gauge06=CONCORDE!Left-Low-Fuel, 812,463,37,12
gauge07=CONCORDE!Right-Low-Fuel, 812,480,37,12
gauge08=Virtavia_F-4_Phantom!AOA, 153,434,53,54
gauge09=Virtavia_F-4_Phantom!ALT, 598,476,110,108
gauge10=Virtavia_F-4_Phantom!ACLK, 809,282,56,58
gauge11=Virtavia_F-4_Phantom!fuel_gauge, 719,436,70,70
gauge12=Virtavia_F-4_Phantom!GFI, 328,590,72,70
gauge13=Virtavia_F-4_Phantom!VSI, 342,669,69,66
gauge14=Virtavia_F-4_Phantom!RALT, 207, 475 ,111,104
gauge15=Virtavia_F-4_Phantom!N1RPMTURB1, 724,580,68,68
gauge16=Virtavia_F-4_Phantom!N1RPMTURB2, 804,580,68,68
gauge17=Virtavia_F-4_Phantom!Airbrake, 172,549,22,22
gauge18=Virtavia_F-4_Phantom!TRI, 610,589,91,92
gauge19=Virtavia_F-4_Phantom!gear_ind, 66,670,61,31
gauge20=Virtavia_F-4_Phantom!ATT, 458,495,102,98
gauge21=Virtavia_F-4_Phantom!COMPASS, 625,25,64,60
gauge22=Virtavia_F-4_Phantom!Machmeter, 214,411,58,57
gauge23=Virtavia_F-4_Phantom!RADAR, 402,276,212,220
gauge24=Virtavia_F-4_Phantom!SHSI, 439,623,145,145
gauge25=Virtavia_F-4_Phantom!JPnozzle1, 728,735,56,56
gauge26=Virtavia_F-4_Phantom!JPnozzle2, 805,734,56,56
gauge27=Virtavia_F-4_Phantom!FuelFlow1, 729,513,56,56
gauge28=Virtavia_F-4_Phantom!FuelFlow2, 807,514,56,56
gauge29=Virtavia_F-4_Phantom!TIT1, 730,660,56,56
gauge30=Virtavia_F-4_Phantom!TIT2, 806,660,56,56
gauge31=Virtavia_F-4_Phantom!Lamp_AutopilotMaster_On, 595,423,22,22
gauge32=Virtavia_F-4_Phantom!AOA2, 253,208,69,69
//gauge33=F4GaugesXtra!F4 MachMeter Insert, 267,201,122,131
//gauge33=F4GaugesXtra!F4 MachMeter Insert, 335,487,88,95
gauge33=ALPHA_Skyray!IAS, 335,487,88,95
gauge34=Virtavia_F-4_Phantom!Flaps_Ind, 52,712,44,46
gauge35=Virtavia Phantom Set3!Altwarn, 320,135,14,15
gauge36=Virtavia Phantom Set3!AOA Indexer, 325,205,21,48
gauge37=Virtavia_F-4_Phantom!Afterburners, 783,569,28,30
gauge38=Virtavia_F-4_Phantom!Tailhook, 183,499,25,24
gauge39=Virtavia_F-4_Phantom!PanelLights, 291,388,25,25
gauge40=Virtavia Phantom Set3!AOA Indexer, 679,207,21,48
gauge40=Virtavia Phantom Set3!AOA Indexer, 679,207,21,48
gauge41=Virtavia_F4_Extragauge!Autopilot ALT, 712,391,21,21
gauge42=Virtavia_F4_Extragauge!Autopilot SPD, 737,357,21,21
gauge43=Virtavia_F4_Extragauge!Autopilot HDG, 737,390,21,21
gauge44=Virtavia_Phantom StdHUD!Brightness, 346,281,38,36
gauge45=Virtavia_F4_Extragauge!BeaconLights, 779,390,21,21
gauge46=Virtavia_F4_Extragauge!LandingLights, 809,390,21,21
gauge47=Virtavia_F4_Extragauge!NavLights, 779,357,21,21
gauge48=Virtavia_F4_Extragauge!StrobeLights, 808,356,21,21
gauge49=Boeing747-400!Autopilot Altitude Window, 613,404,55,15
gauge50=Boeing747-400!Autopilot IAS-Mach Window, 621,420,42,15
gauge51=Boeing747-400!Autopilot VS Window, 615,433,53,15
gauge52=Virtavia_F4_Extragauge!Autopilot, 712,357,21,21

//--------------------------------------------------------
[Window01]
Background_color=16,16,16
size_mm=150,250
position=8
visible=0
ident=GPS_PANEL
gauge00=gps!gps, 0,0,150,250

//--------------------------------------------------------
[Window02]
file=ECU_Backround.bmp
file_1024=ECU_Backround.bmp
size_mm=266,320
window_size_ratio=1.000
position=6
visible=0
ident=THROTTLE_PANEL
window_size= 0.281, 0.455
window_pos= 0.000, 0.450
gauge00=lear_45.thrust_levers.2, 96,18,128,142
gauge01=Virtavia_F-4_Phantom!StartJet1, 84,235,14,14
gauge02=Virtavia_F-4_Phantom!StartJet2, 125,234,14,14
gauge03=Virtavia_F-4_Phantom!Fuel Pump 1, 104,197,14,14
gauge04=Virtavia_F-4_Phantom!Fuel Pump 2, 126,197,14,14
gauge05=Virtavia_F-4_Phantom!Alternator1, 67,203,14,14
gauge06=Virtavia_F-4_Phantom!Alternator2, 83,203,14,14
gauge07=Virtavia_F-4_Phantom!Fuel1, 101,297,14,14
gauge08=Virtavia_F-4_Phantom!Fuel2, 126,297,14,14

//--------------------------------------------------------
[Window03]
file=Radio Stack.bmp
file_1024=Radio Stack.bmp
size_mm=191,245
window_size_ratio=1.000
position=0
visible=0
ident=RADIO_STACK_PANEL
window_size= 0.213, 0.350
window_pos= 0.800, 0.650
gauge00=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 6,254,132,56
gauge01=Bendix_King_Radio!Bendix-King Radio Xpndr, 6,310,134,48
gauge02=CONCORDE!Radio-Adf, 18,5,95,39
gauge03=CONCORDE!Radio-Comm1, 8,93,105,40
gauge04=CONCORDE!Radio-Lights, 2,191,82,17
gauge05=CONCORDE!Radio-Transponder, 7,50,104,39
gauge06=CONCORDE!Radio-Naviagtion-1, 90,137,53,50
gauge07=CONCORDE!Radio-Naviagtion-2, 91,187,52,51

//--------------------------------------------------------
[Window04]
Background_color=0,0,0
size_mm=1024,768
window_size_ratio=1.000
position=1
visible=0
ident=20
render_3d_window=1
gauge00=Virtavia_Phantom StdHUD!Dark, 415,170,190,220

//--------------------------------------------------------
[Window05]
Background_color=0,0,0
size_mm=1024,768
window_size_ratio=1.000
position=1
visible=0
ident=21
render_3d_window=1
gauge00=Virtavia_Phantom StdHUD!Normal, 415,170,190,220

//--------------------------------------------------------
[Window06]
Background_color=0,0,0
size_mm=1024,768
window_size_ratio=1.000
position=1
visible=0
ident=22
render_3d_window=1
gauge00=Virtavia_Phantom StdHUD!Bright, 415,170,190,220

//------------- COP Control ----------------------
[Window07]
size_mm=52,12
visible=0
window_size= 0.045,0.015
window_pos= 0.55,0.02
background_color=16,16,16
ident=10080 //DO NOT CHANGE THIS VALUE
nomenu=1
gauge00=COP3!ControlPanel, 0,0,52,12
gauge01=COP3/CarrierZones!dsd_carrier_zones,0,0
gauge02=COP3/Config!config, 0,0,,, ./gauges/COP3/Config.ini
gauge03=COP3/Sound!dsd_xml_sound3, 0,0,,, ./gauges/COP3/Sound.ini
gauge04=COP3!Arrester, 0,0
gauge05=COP3!Catapult, 0,0
gauge06=COP3/SpeedControl!xml2ipc, 0,0
gauge07=COP3!SonicBoomControl, 0,0
//--------------------------------------------------------
[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=Virtavia_F-4_Phantom!Burner_TAXI, 0,0,20,20
gauge01=Virtavia_F-4_Phantom!Contrail_REC, 0,0,20,20
\\gauge02=Virtavia_F-4_Phantom!Reheat_LOGO (file://\\gauge02=Virtavia_F-4_Phantom!Reheat_LOGO), 0,0,20,20
gauge02=Virtavia_F4_Extragauge!Virtavia_exh_smoke2 , 1,1,1,1
gauge03=Virtavia_F4_Extragauge!AfterburnerAuto, 1,1,1,1
gauge04=COP3/WindowStatus!window_status, 0,0
gauge05=COP3!WindowInit10080,0,0
//--------------------------------------------------------
[Vcockpit02]
file=PanelFix2.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$pan1
gauge00=Virtavia_F-4_Phantom!ALT, 628,184,155,157
gauge01=Virtavia_F-4_Phantom!fuel_gauge, 803,130,95,96
gauge02=Virtavia_F-4_Phantom!GFI, 254,345,98,100
gauge03=Virtavia_F-4_Phantom!VSI, 273,461,98,99
gauge04=Virtavia_F-4_Phantom!AOA, 12,127,75,79
gauge05=Virtavia_F-4_Phantom!RALT, 87,182,155,155
gauge06=Virtavia_F-4_Phantom!N1RPMTURB1, 809,339,94,94
gauge07=Virtavia_F-4_Phantom!N1RPMTURB2, 920,339,94,94
gauge08=Virtavia_F-4_Phantom!TRI, 639,346,145,140
gauge09=Virtavia_F-4_Phantom!FuelFlow1, 812,239,82,83
gauge10=Virtavia_F-4_Phantom!FuelFlow2, 920,239,82,83
gauge11=Virtavia_F-4_Phantom!JPnozzle1, 810,555,84,84
gauge12=Virtavia_F-4_Phantom!JPnozzle2, 917,555,84,84
gauge13=Virtavia_F-4_Phantom!Machmeter, 98,94,79,83
gauge14=Virtavia_F-4_Phantom!SHSI, 408, 392 ,203,201
gauge15=Virtavia_F-4_Phantom!TIT1, 815,450,79,75
gauge16=Virtavia_F-4_Phantom!TIT2, 922,450,79,75
gauge17=Virtavia_F-4_Phantom!ATT, 436,209,142,138
gauge18=ALPHA_Skyray!IAS, 267,201,122,131
//gauge18=F4GaugesXtra!F4 MachMeter Insert, 267,201,122,131
gauge19=Virtavia_F-4_Phantom!Afterburners, 892,315,35,35
gauge20=Virtavia_F4_Extragauge!Autopilot, 804,30,30,30
gauge21=Virtavia_F4_Extragauge!Autopilot SPD, 843,30,30,30
gauge22=Virtavia_F4_Extragauge!Autopilot ALT, 804,76,30,30
gauge23=Virtavia_F4_Extragauge!Autopilot HDG, 841,76,30,30
gauge24=Virtavia_F4_Extragauge!NavLights, 900,30,30,30
gauge25=Virtavia_F4_Extragauge!StrobeLights, 942,30,30,30
gauge26=Virtavia_F4_Extragauge!BeaconLights, 900,76,30,30
gauge27=Virtavia_F4_Extragauge!LandingLights, 942,76,30,30
gauge28=CONCORDE!Front-Low-Fuel, 938,175,44,15
gauge29=CONCORDE!Right-Low-Fuel, 938,196,44,15
gauge30=Boeing747-400!Master Warning Light, 921,131,61,34
gauge31=Virtavia_F-4_Phantom!Airbrake, 40,300,29,29
gauge32=Virtavia_F-4_Phantom!Tailhook, 59,233,30,30
gauge33=Virtavia_F-4_Phantom!PanelLights, 192,57,31,31

//--------------------------------------------------------
[Vcockpit03]
file=radarfix2.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$pan3
gauge00=Virtavia_F-4_Phantom!RADAR, 316,498,457,478
gauge01=Boeing747-400!Autopilot Altitude Window, 789,777,96,30
gauge02=Boeing747-400!Autopilot IAS-Mach Window, 803,809,78,27
gauge03=Boeing747-400!Autopilot VS Window, 783,842,104,27
gauge04=Virtavia_F-4_Phantom!AOA2, 28,288,140,135
gauge05=Virtavia Phantom Set3!AOA Indexer, 169,308,39,91
gauge06=Virtavia Phantom Set3!AOA Indexer, 911,308,39,91
gauge07=Virtavia-f4_altwarn_0001, 172,163,30,28

//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$pan4
gauge00=Virtavia_F-4_Phantom!Alternator1, 25,31,30,30
gauge01=Virtavia_F-4_Phantom!Alternator2, 66,30,30,30
gauge02=Virtavia_F-4_Phantom!Fuel Pump 1, 109,30,30,30
gauge03=Virtavia_F-4_Phantom!Fuel Pump 2, 153,30,30,30
gauge04=Virtavia_F-4_Phantom!StartJet1, 59,88,40,40
gauge05=Virtavia_F-4_Phantom!StartJet2, 128,88,40,40
gauge06=Virtavia_F-4_Phantom!Fuel1, 83,196,30,30
gauge07=Virtavia_F-4_Phantom!Fuel2, 136,196,30,30

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$pan5
gauge00=Virtavia_F-4_Phantom!Flaps_Ind, 211,295,90,81
gauge01=Virtavia_F-4_Phantom!gear_ind, 305,195,141,83

//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$pan6
gauge00=Virtavia_F-4_Phantom!COMPASS, 7,4,245,240

//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$pan7
gauge00=CONCORDE!Radio-Adf, 51,12,227,81
gauge01=CONCORDE!Radio-Transponder, 33,101,235,93
gauge02=CONCORDE!Radio-Comm1, 34,200,232,90
gauge03=CONCORDE!Radio-Naviagtion-1, 216,297,117,106
gauge04=CONCORDE!Radio-Naviagtion-2, 218,406,116,106
gauge05=CONCORDE!Radio-Lights, 24,414,185,33

//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$pan9
gauge00=Virtavia_Phantom StdHUD!Max, 23,4,449,350

//--------------------------------------------------------
[Vcockpit09]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$pan2
gauge00=Virtavia_F-4_Phantom!ACLK, -13,-23,268,271

[Color]
Day=255,255,255
Night=25,10,5
Luminous=202,220,147
[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=4000


The air.cfg lights section:


[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 = 1, 9.55, 0, 4.88, fx_shockwave_beacon_rotating_red ,
light.8 = 1, -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, -12.50, -2.20, -0.74, fx_burner2 ,
light.14 = 9, -12.50, -2.20, -0.74, fx_F-15reheateffect ,
light.15 = 9, -12.50, 2.20, -0.74, fx_burner2 ,
light.16 = 9, -12.50, 2.20, -0.74, fx_F-15reheateffect ,

fxsttcb
August 19th, 2011, 03:30
This is the one I use most currently and lights the burners through the throttles:

[Vcockpit01]
.....
gauge03=Virtavia_F4_Extragauge!AfterburnerAuto, 1,1,1,1
.....
[lights]
.....
light.13 = 9, -12.50, -2.20, -0.74, fx_burner2 ,
light.14 = 9, -12.50, -2.20, -0.74, fx_F-15reheateffect ,
light.15 = 9, -12.50, 2.20, -0.74, fx_burner2 ,
light.16 = 9, -12.50, 2.20, -0.74, fx_F-15reheateffect ,
Thank you!
'tis as I suspected. [Vcockpit01] Gauge03 is throttle sensitive and turns on the Logo Light(type 9) at 90%.
It has a looping function that turns the logo light off if the throttle is less than 90% and that light is turned on with "L" or another switch. That is the type of function that is missing from my coding. The drawback to that gauge is it engages both 'burners with engine 1 controlling both engine's effects.
I use the light switches, so, I never worried if the AB come on with "L". I knew it would, but, it didn't matter to me! I will fix that for the rest of you!

The real thing has physical switching to engage the igniters and give the fuel augmentation necessary. With the AB switching off, the throttle will go to full military power without igniting the 'burners.
Along with individual AB engagement for the engines, that is the scenario I'm trying to accomplish with the switch/indicator.

I delved deeper into my notes and found my own warning not to use light type "10"(Cabin Lights). I reserved that, so, users can also use the Doug Dawson / Rob Barendregt Sonic Boom visual effect.



I do not open the canopy
Does not work parachute
Does not work covers, ribbons
I would be happy if Vertigo Studios doing it the phantom!Unfortunately, as far as I can tell the Coud9's FS9 coding doesn't work for those functions in FSX. When my Virtavia Phantom stuff is finished and bugs are at least minimized, I'll tackle the cloud9 FSX issues and see if it can be fixed.

I am trying to be patient while waiting for the A2A AccuSim Phantom II to hit the shelves.
If the rest of their AccuSimmed planes are an indication, the A2A Phantom II will be awesome.

Thanks for the feedback folks! It is much appreciated...Don

doublecool
August 21st, 2011, 09:51
Wow good thread :applause:

been off line do to provider modem issue... thanks for the responses :salute:

funny how the AB effect in the cloud 9 is such a pain... looking forward to the fix

kdl
August 22nd, 2011, 00:49
Hi expat,

in your panel.cfg listed above I found
[Vcockpit02]
file=PanelFix2.bmp
[Vcockpit03]
file=radarfix2.bmp

Where can I get these two .bmp-files?

expat
August 22nd, 2011, 04:36
Hopefully attached. Not sure of their origin (not me!).

kdl
August 22nd, 2011, 07:26
Thanks, will try if your [panel] suggestion works for me.