Sorry about that, here's a corrected version. Just replace the parenthesis with brackets. // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com// Built Wednesday, October 06, 2004 at 09:41 FSPS Build:14852(Window Titles)Window00=Introduction PanelWindow01=Captain's PanelWindow02=First Officer's PanelWindow03=Windscreen WiperFixed Window30=Forward RightFixed Window31=RightFixed Window32=Flight Engineer Panel (SHIFT+Keypad 3)Fixed Window33=RearFixed Window34=Rear LeftFixed Window35=LeftFixed Window36=Forward LeftFixed Window37=UpFixed Window38=Lower Panels(VIEWS)VIEW_FORWARD_WINDOWS=0,15,20,190VIEW_FORWARD_DIR=4.000, 0.000, 0.000VIEW_FORWARD_RIGHT_WINDOWS=30VIEW_RIGHT_WINDOWS=31VIEW_REAR_RIGHT_WINDOWS=32VIEW_REAR_RIGHT_DIR=2.000, 0.000, 90.000VIEW_REAR_WINDOWS=33VIEW_REAR_ZOOM=1.500VIEW_REAR_LEFT_WINDOWS=34VIEW_REAR_LEFT_ZOOM=1.500VIEW_LEFT_WINDOWS=35VIEW_FORWARD_LEFT_WINDOWS=36VIEW_UP_WINDOWS=37VIEW_DOWN_WINDOWS=38//--------------------------------------------------------(Window00)file=introscreen.bmp size_mm=1024window_size_ratio=1.000 position=7visible=1ident=0window_size= 1.000, 0.450window_pos= 0.000, 0.550gauge00=707server!intro, 70,10,884//--------------------------------------------------------(Window01)file=Captain.bmp size_mm=1024window_size_ratio=1.000 position=0visible=1ident=15window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707nightlights!captain, 0,330,370gauge01=707omi, 7,520,25gauge02=707basics!airspeed1, 51,475,80gauge03=707gyros!coord1, 51,579,80gauge04=707basics!mach1, 51,677,80gauge05=707basics!warn1, 256,388,126gauge06=707gyros!adi1, 160,423,130gauge07=707gyros!hsi1, 159,599,136,155gauge08=707basics!alt1, 317,475,80gauge09=707gyros!rmi, 310,574,94gauge10=707basics!dme, 318,681,77gauge11=707basics!vsi1, 420,477,80gauge12=707basics!clock1, 421,577,80gauge13=707basics!ralt, 420,677,80,81gauge14=707centre!fdswitch, 522, 384 ,83gauge15=707centre!tas, 523,429,80,81gauge16=707centre!attitude, 525,525,78,80gauge17=707centre!oilleft, 536,622,74gauge18=707centre!fire, 611,282,371gauge19=707centre!engine1, 623,392,66,330gauge20=707centre!engine2, 689,392,66,330gauge21=707centre!engine3, 755,392,66,330gauge22=707centre!engine4, 821,392,66,330gauge23=707centre!config, 897,359,51,73gauge24=707centre!flaps, 894,469,53gauge25=707centre!oilright, 894,646,57gauge26=707gear, 959,348,64gauge27=707server!compass, 782,68,60gauge28=707server!xlight, 604,0,420gauge29=707centre!switches1, 465,6,135gauge30=../Civa/INS!Config, 0,0,0//--------------------------------------------------------(Window02)file=First-Officer.bmp size_mm=1024window_size_ratio=1.000 position=0visible=0ident=20window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707nightlights!firstofficer, 0,330,440gauge01=707server!compass, 193,68,60gauge02=707server!xlight, 15,0,420gauge03=707omi2, 990,520,25gauge04=707centre!fdswitch2, 7,386,83gauge05=707centre!tas, 7,429,80,81gauge06=707centre!attitude, 9,525,78,80gauge07=707centre!oilleft, 20,622,74gauge08=707centre!fire2, 95,282,371gauge09=707centre!engine1, 107,392,66,330gauge10=707centre!engine2, 173,392,66,330gauge11=707centre!engine3, 239,392,66,330gauge12=707centre!engine4, 305,392,66,330gauge13=707centre!config, 381,359,51,73gauge14=707centre!flaps, 379, 469 ,53gauge15=707centre!oilright, 378,646,57gauge16=707gear2, 443,348,64gauge17=707basics!tat, 522,478,80gauge18=707basics!surfaces, 522,576,80gauge19=707basics!ralt, 522,678,80,81gauge20=707basics!airspeed2, 625,475,80gauge21=707gyros!coord2, 625,579,80gauge22=707basics!mach2, 625,677,80gauge23=707basics!warn2, 641,391,209gauge24=707gyros!adi2, 734,424,130gauge25=707gyros!hsi2, 732,599,136,155gauge26=707basics!alt2, 890,474,80gauge27=707basics!vsi2, 891,576,80gauge28=707basics!clock2, 892,678,80gauge29=707centre!switches1, 452,6,135//--------------------------------------------------------(Window03)Background_color=0,0,0 size_mm=1024,470position=7visible=1ident=190render_3d_window=1window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707wiper, 0,0,20//--------------------------------------------------------(Fixed Window30)file=FORWARD_RIGHT.bmp position=7visible=0ident=30nomenu=1window_size= 1.000, 1.000window_pos= 0.000, 0.000//--------------------------------------------------------(Fixed Window31)file=RIGHT.bmp position=7visible=0ident=31nomenu=1window_size= 1.000, 1.000window_pos= 0.000, 0.000//--------------------------------------------------------(Fixed Window32)file=REAR_RIGHT.bmp size_mm=1024position=7visible=0ident=32nomenu=0window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707FlightEng!engines, 730,436,264gauge01=707FlightEng!fuelleftmain, 410,537,66gauge02=707FlightEng!fuelcentre, 483,477,66gauge03=707FlightEng!fuelrightmain, 558,537,66gauge04=707FlightEng!fuelleftaux, 338,592,66gauge05=707FlightEng!fuelrightaux, 633,592,66gauge06=707FlightEng!fuellefttip, 338,700,66gauge07=707FlightEng!fuelrighttip, 633,700,66gauge08=707FlightEng!fueltotal, 429,700,66gauge09=707FlightEng!fuelpumps, 326,378,382gauge10=707FlightEng!electrics, 325,0,457gauge11=707FlightEng!turbocomp1, 797,37,66gauge12=707FlightEng!turbocomp2, 871,37,66gauge13=707FlightEng!turbocomp3, 945,37,66gauge14=707FlightEng!differential, 885, 281 ,80gauge15=707FlightEng!cabinalt, 795,281,80gauge16=707FlightEng!acswitches, 787,102,225gauge17=707centre!switches3, 805,728,145//--------------------------------------------------------(Fixed Window33)file=REAR.bmp position=7visible=0ident=33render_3d_window=1nomenu=1window_size= 1.000, 1.000window_pos= 0.000, 0.000//--------------------------------------------------------(Fixed Window34)file=REAR_LEFT.bmp position=7visible=0ident=34nomenu=1window_size= 1.000, 1.000window_pos= 0.000, 0.000//--------------------------------------------------------(Fixed Window35)file=LEFT.bmp position=7visible=0ident=35nomenu=1window_size= 1.000, 1.000window_pos= 0.000, 0.000//--------------------------------------------------------(Fixed Window36)file=FORWARD_LEFT.bmp position=7visible=0ident=36nomenu=1window_size= 1.000, 1.000window_pos= 0.000, 0.000//--------------------------------------------------------(Fixed Window37)file=UP.bmp size_mm=1024position=7visible=0ident=37render_3d_window=1nomenu=0window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707server!compass, 477,655,60,42gauge01=707server!xlight, 297,587,420,40gauge02=707server!starters, 314,98,379,81gauge03=707server!leftlights, 101,97,214,292gauge04=707server!emergency, 446,258,123,255gauge05=707server!rightlights, 700,99,217,311gauge06=707server!pitot, 736,427,137,87gauge07=707server!maplight1, 48,437,31,29gauge08=707server!maplight2, 935,436,33,32gauge09=707server!wiperswitch, 474,515,258,64gauge10=707server!wingantiice, 281,513,196,66gauge11=707server!engineantiice, 159,513,128,106gauge12=707centre!switches2, 437,76,145,20gauge13=../Civa/Ins!Msu1, 401,191,198,58gauge14=../civa/INS!NavModeSingle, 613, 182 ,47,72gauge15=../civa/INS!UpdateFlags, 315,182,79,71//--------------------------------------------------------(Fixed Window38)file=downview.bmp size_mm=1024position=7visible=0ident=38nomenu=0window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707nightlights!lower, 0,0,261,260gauge01=../Civa/Ins!CDU1, 580,4,186,194gauge02=707centre!throttles, 338,199,348,379gauge03=707server!autopilot, 336,576,350,180(Color)Day=235,235,235Night=10,10,10Luminous=10,10,10(Default View)X=0Y=0SIZE_X=8191SIZE_Y=4000You could also just cut and paste the lines which refer to the CIVA gauges and their locations into the original file.Again, sorry about the brackets, just forgot to change them when I posted the file originally.Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

All I did was add one small pop up window with the AP controls. It appears in the lower right corner, and doesn't cover anything critical. It definitely makes controling the a/c easier! :)Window04=AP Popup.....//--------------------------------------------------------[Window04]Background_color=0,0,0 size_mm=351,180window_size_ratio=1.000 position=0visible=0ident=140window_size= 0.400, 0.280window_pos= 0.600, 0.710gauge00=707server!autopilot, 0,0,350,179I finally figured out a way to get my FSNav to fly the "flightplan" by using "Mode 2" (toggled off speed hold and alt control). It works a treat! :)

Works great Bill! Any ideas please how to toggle the autopilot panel without having to go to the top menu? I tried with one of the RKG buttons (a variety of multipurpose buttons in one gauge file) but I don't know how to configure a button to make it do what I want. Even after looking at the gauge properties in CFG Panel Editor and setting its ident to the same number in the window section it didn't work. Then I saw that each group of buttons had the same ident number so that doesn't seem any good. All I managed to get it to do was to toggle the horizon height.

Ed, I'm sure I set it up OK, but the radio panel to the left of the ins new gauge no longer works or shows any digits, as if it is only a bitmap remaining. Any ideas please? Could it be because it is a part of the removed old ins gauge? Would it be better to leave it in as long as it would be covered over by the new one, and operating the new gauge doesn't affect the old one underneath, assuming it will be underneath?

I'd like to get it to fly an FS9 flightplan (or one inported to FS9)for odd flights. I'm guessing that adding a NAV/GPS switch to the panel will do it. If it works I'll post some ideas how to install one if it's any use to anyone.

Charlie, those radios are part of the default INS gauge.As far as accessing the throttle quad, you can either use the mouse hotspot OR press 5 in the numeric keypad (with NUM LOCK on).You can, of course, move the simicons to the lower edge of the panel quite easily... but there's a copy of 'em "painted on" the panel background.From what I can see, there is a distinction without a difference between how the subpanels on this a/c are accessed and "unrealistic popup panels." :)Has anyone else noticed that the HSI CRS indicator is precisely 18

Here is how I added an autopilot popup on the main window - when toggled on, it will cover the lower part of the engine gauges, but these are also available on the FO pilot's panel (I think.) The toggle was added to the right of the row of hot spot toggles. The gauge used for this is from another plane (see below.) Works like a charm for me. Just add the lines below to the appropriate section with [Window04] being an addition for the new AP popup. [Window Titles]Window04=Autopilot[Window01]gauge30=DA20-C1_SW!AP, 443,5,20,20, 400[Window04]Background_color=0,0,0 size_mm=350,180window_size_ratio=1.00ident=400 window_size= 0.342, 0.234window_pos= 0.600, 0.766visible=0ident=400gauge00=707server!Autopilot, -2,-2,350,180 That toggle (gauge30) is from:Diamond DA20-C1 Evolution Panel, Sound & Aircraft PackageIncluding Interactive VC with Gauges. for FS2004 COFVER 1.9 - Apr 25, 2004====================================================Copyright 2004 by Premier Aircraft Designhttp://www.flightsimnetwork.com/premaircraftLook for it under the "KATANA" button.BTW, another good plane, but not quite as fast as the 707!I left the original AP on the pedestal alone and did not notice any problems. You could comment out the line for that gauge if you want, although I have not tested that.

Hi Bill,'Charlie, those radios are part of the default INS gauge.'Thanks, that's what I thought. I think I'll try adding the original gauge back in and see how it goes.'As far as accessing the throttle quad, you can either use themouse hotspot OR press 5 in the numeric keypad (with NUM LOCKon).'I also found that pressing SHIFT + 5 worked. How do I find the mouse hotspot? I didn't think there would be one for the new autopilot window?'From what I can see, there is a distinction without adifference between how the subpanels on this a/c are accessedand "unrealistic popup panels." :)'Agreed!'Has anyone else noticed that the HSI CRS indicator isprecisely 18

>>I finally figured out a way to get my FSNav to fly the>"flightplan" by using "Mode 2" (toggled off speed hold and alt>control). It works a treat! :)I found you can use Mode 1 in FSNAV as long as the aircraft is designated as not having an autothrottle (checkbox in the aircfadt parameters box - set up a new one if you don't have one for the 707) AND you don't engage the altitude hold control on the AP. FSNAV will control heading and adjust the altitude using the AP pitch controls. You control the speed which will need lots of attention.

>'As far as accessing the throttle quad, you can either use>the>mouse hotspot OR press 5 in the numeric keypad (with NUM LOCK>on).'>>I also found that pressing the SHIFT + 5 worked. How do I find the>mouse hotspot? I didn't think there would be one for the new>autopilot window?Numpad SHIFT-5 will "lock" the view (which is the DOWN VIEW, btw)No, I was speaking of the existing throttle quad window.For the one I added with just the AP controls, use Shift-6I noticed the VOR calibration issue during a flight from Chicago to San Francisco. All the way along, the durn thing was off by 18

Beginning to feel like Emeril this morning...Anyway, I tried replacing the original INS gauge file and then adding the reference to the CIVA CDU as the last gauge in the panel and when the power is off the orginal gauge bleeds through. Once you power on the CIVA gauge, it looks fine and it seems to work although there could be a problem with two INS gauges in one panel. Will do a test flight later and see what happens.But the radios do work again.....My "down" (or console) now looks like this:(Fixed Window38)file=downview.bmp size_mm=1024position=7visible=0ident=38nomenu=0window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=707nightlights!lower, 0,0,261,260gauge01=707server!ins, 261,0,500gauge02=707centre!throttles, 338,199,348,379gauge03=707server!autopilot, 336,576,350gauge04=../Civa/Ins!CDU1, 580,4,186,194Parenthesis replaced by brackets, of course. I think that the CIVA gauge entry does have to be later in the file than the orginal in order to load the CIVA on top.Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

>Beginning to feel like Emeril this morning...>Parenthesis replaced by brackets, of course. I think that the>CIVA gauge entry does have to be later in the file than the>orginal in order to load the CIVA on top.When you are in "text mode" in this forum, you can use [brackets] with no problems. That is the purpose of the "text mode" (or "code mode" if you prefer).As far as draw order is concerned, you could also simply use an undocumented panel.cfg entry:draw_order00=gauge04, gauge17, gauge05, gauge06, gauge28This entry will force the panel system to display listed gauges LAST... :)

Hi Bill and Ed, Maybe the answer to the bleedthrough would be to make a new window for the CIVA guage and place it exactly over the top, making it visible on startup? That way, the original could be accessed too by turning the window off, for whatever reason. I'll have a go at this later tonight unless someone else would like to have a go. Bill, I too found that the plane seems unbelievably overpowered but only when the airspeed is high. It seems to pick up between 200-250Kts. It's like a ram effect. It can climb at up to 6000FPM and gets to altitude in a much shorter time than I think would be feasible. Also I had no problem getting it to 45000 ft and still plenty left. It cruises at Mach 9 at around 65-70N1 even at high altitude. I think it is something in the airfile as I think I remember it reacted the same with another panel I tried before we got the original working. No idea at this stage if I could do anything with it although I'd like to think so as I have messed around with airfiles before, but in any case I have yet no idea how the 707 is supposed to perform. Maybe I could find out from some charts I have and compare the readings with other planes that are more known to me. I could also check out other existing 707 airfiles and compare. Maybe I could concoct a hybrid.

Tell you where I am at this point. I simply deleted the default INS gauge and put the CIVA in its place. I then just added a transponder and ADF radio from another aircraft. Not quite as neat, but it works.Sure am glad I have FS Panel Studio, though.....Now about that Radar Gauge.......Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

Here's what I ended up with. Everything works.Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpghttp://forums.avsim.net/user_files/93621.jpg