Okay, thanks, Mark and CoolP. By the way, I don't know if this was resolved earlier, but the INS won't turn on. I set it to Standby and nothing happens.

Yeah, the double INS worked.

By the way, in order to save the INS state, you need to decouple it from the autopilot, but it won't let me--the switch just pops back into position. What's causing this?

CoolP wrote on Jul 11^th, 2012 at 9:12pm:
I dded it to the single INS as a workaround too, and it work's fine.

@boeing247

In the single INS panel.cfg (the one that was originally named CIVA-panel.cfg), change this:

[Window00]
file=bg.bmp
background_color=0,0,0
size_mm=1024,768
window_size_ratio=1.00   
position=7
visible=1
ident=MAIN_PANEL
render_3d_window=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=Captain_Sim.x707.sys!main, 0,0, 2,2
gauge01=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge02=Captain_Sim.x707.tools!icons, 0,532,24,120
gauge03=Captain_Sim.x707.gpws!main, 0,0,1,1
;CIVA
gauge04=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge05=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge06=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge07=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge08=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042

to this:

[Window00]
file=bg.bmp
background_color=0,0,0
size_mm=1024,768
window_size_ratio=1.00   
position=7
visible=1
ident=MAIN_PANEL
render_3d_window=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=Captain_Sim.x707.sys!main, 0,0, 2,2
gauge01=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge02=Captain_Sim.x707.tools!icons, 0,532,24,120
gauge03=Captain_Sim.x707.gpws!main, 0,0,1,1
;CIVA
gauge04=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge06=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge07=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042

And add the gauge00=Captain_Sim.x707.sys!main, 0,0, 2,2 to the bottom of [VCockpit01] like this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701

It should initialize as soon as the 707 loads into FSX (when your Default cockpit view is set to 3-D virtual cockpit in FSX).

Mark

When you say to add the last line to the bottom of Vcockpit1 it does not make sense.  It says gauge 00 and the last line in Vcockpit1 is highlighted in bold.  Am I suppose to replace that line and add to it?

jetman40 wrote on Jul 19^th, 2012 at 6:08pm:

Sorry. My bad. I should have written:

And add the gauge27=Captain_Sim.x707.sys!main, 0,0, 2,2 to the bottom of [VCockpit01] like this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701

The gauges must be consecutive numbers (gauge00, gauge01, gauge02 etc. up to gauge27). By adding another gauge00 it would prevent both gauges from working.

Quote:

The reason might be that the CS INS rendition actually does work, right out of the box.  

I have to ask if you have installed the Civa INS gauge. That's a separate installer, not coming with the 707. People sometimes forget that step and I'm not sure on how to interpret the statements of yours. That's why I'm asking, just in case.

So if you make sure to install the extra Civa gauge and if you are using the separate panel.cfg which was delivered by CS (CIVA_panel.cfg, which has to be renamed to be active), the only remaining special item might be this one. One has to open the 2D simicons panel once.
www.captainsim.org/yabb2/YaBB.pl?num=1285100008/256#256

To work around that, you can tweak your cfg like Mark has shown or use the twin INS mod. And that's actually how we got here.  

jetman40 wrote on Jul 21^st, 2012 at 4:59pm:

If the problem persists, I suggest posting a screenshot of that situation. It helps helping. 

Spot on.   Just run it as admin and point it to your FSX folder. Then try again with loading the 707 in FSX, but make sure to enable that special panel.cfg file for the Civa operation.

CIVA_panel.cfg in \SimObjects\Airplanes\CS_B707-300\panel has to be renamed to panel.cfg. Make a backup of the old file, just in case.

For tweaking the installation, refer to Mark's tips on moving the one gauge entry. Or take a look at the twin INS installation. But the first step will surely be to check if the basic stuff is working, so you are right on track with the Civa installer. 

I don't know if that has anything to do with the Civa INS, Ron. I doubt it. But are you already using that uiautomationcore.dll fix? Without it, Win7 PCs may run into a CTD with FSX and accessing the menus.