***cooolp,

I think with your latest edit, the landing gear is now not visible in external view, if you start on the ground.,

reverting back to original panel file solves the issue..

could you perhaps test this, and also copy and past the full section of your config under the gauge 27 bit,

==edit,

still no power in the +CIVA INS 2D panel

==EDIT,

ok so i think it is to do with window 06.

Like Mark on the previous page he was window 00 and window06 with the

gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701


I just put that in so my config looks like this . pressed shift and 1, and it works!!
[coolp check the first post,
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701
is not under your window00, it is only 04 and 05]


[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
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge04=../civa/INS!CduPanelIconB,   0,  652, 24, 24, 11041
gauge05=../civa/INS!AdeuPanelIconB,  0,  676, 24, 24, 11042

;CIVA
[Window06]
size_mm=420,223
background_color=0,0,0
window_pos=0.300, 0.160
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge01=../civa/ins!Cdu1,   0,  0, 200, 158
gauge02=../civa/ins!Cdu2, 200,  0, 200, 158
gauge03=../civa/INS!UpdateFlags, 150, 160, 115, 63
gauge04=../civa/INS!CduPanelIconB,      400, 0, 20, 20, 11041
gauge05=../civa/INS!NavModeDual,      270, 160, 50, 45
gauge06=../civa/INS!AdeuPanelIconB,      400, 138, 20, 20, 11042

The fps thing might happen because overlay panels and undocked 2D ones might interfere with the antialiasing setting of your graphic card. This is a general issue, not a special Civa INS one.
If you use a Nvidia card, try "override" instead of "enhance" in the AA policy. This can be done via the great Nvidia Inspector. Just google the phrase and you will find the downloads and guides. It's freeware.
ATI cards surely have AA triggers too and I have to state clearly that the Civa won't affect fps by design in any way so there surely is something else causing this.


As for the guidance stuff, you should make sure to have all switches set up correctly. INS aligned, Nav mode active, Nav mode switch (if using my modification) and the INS/Doppler switch on the 707 should be mentioned there.
The next thing will be the AP and FD setting. So there are some sources for "no guidance" of course.


I wouldn't blame Captain Sim for INS problems at all. This is an addon module and it works fine. We can't really rule out some more or less big error on your system or setup causing this, so the refund wish lacks a bit of an objective viewpoint in my eyes.
They mainly deliver a complete aircraft with the Doppler system. The INS is an addition (which works) but isn't necessary to drive the thing.
If I could read more complains about it, we might come to a point where CS would be to blame, but if the setup is done correctly, this additional gauge drives your AP, adds some useful data and doesn't affect the performance at all.
I know it can be unsatisfying to read this but, as I pointed out above, there are quite some settings to get mixed up. Maybe you're a victim of at least one of them and as long as the input stays diffuse, help will be somehow catchy.


I also wonder about your reports which can't be reproduced here. My modification can not for example cause any problem with the landing gear showing or not. I can't, because the gauges there aren't connected to such things in any way.
I hope you don't feel offended if I use the example of someone telling my that he pulled the plug of his monitor and now his fridge isn't working anymore. But that's pretty much my impression about some things there.

Let me assure you that I have tested my small Civa integration and I think some other guys did too (as they are using it or used it as a start point).
As we are all humans, problems and mistakes surely can arise but I can't see any of this in the tutorial and the only non-working reports so far were caused by faulty editing the stuff, which is a human factor too, no problem with that of course.

So maybe a short break from all 707 stuff will lead to a fresh minded approach after some days or so. 1.2 is working, with and without Civa INS.
One has to make sure that no other software with e. g. guidance control interferes it and as we all use our sim with loads of addons, this can sometimes be hard to oversee.

i use inspector, so AA is not done through any FSX setting..
Perfect. So try the "override" instead of the "enhance" flag at the antialiasing options there and test again.
As said before, the Civa INS doesn't affect the fps at all but the handling of the antialiasing of popup windows (which is a global one for FSX) surely does.

Everytime i fly in the uk, and say, do a flight plan west,

the ins engages, and the heading selector will ALWAYS fix on north..

every time i reproduce it
I have no doubt that you can reproduce this behavior, but no one else can so far. That's an indicator of a system based or user caused error and therefor not a general fault (so far).
I'm sure we can help you here, on a user basis, but we need some information about how you get the INS ready for navigation and how you operate the AP and FD on the 707.

I also suggest to use and test the Doppler system first as this is the intended way of operating the 707. Captain Sim planned and programed her to use this while the INS is an optional thing.

Alright, maybe I'm stupid,
  I can't get autopilot to work. I installed the CIVA and changed the panel.cfg over, but I can't get it to work. It just turns on and that's it. As well, how does autopilot work on this thing? I put in a VOR the other day and set it to vor and it flew my the wrong direction all together. So, can somebody please explain this to me in a way a little easier to understand than the manual? (I swear I don't even see the things the CIVA tutorial is talking about)

Thanks

Hi folks,

don´t you think that the INS drifts a little bit too fast? It´s great to have an INS that realisticaly drifts but without DME update this INS is more or less useless after 10-15 minutes. That seems to be a little too fast. I mean if you cross the pond it has to work for hours until you get a chance for a DME update.
Or maybe the INS does actually not drift so much but the index is over five within 10 minutes  
The same INS in Concorde X works much more stable.
Is there a way to adjust the drift/index  rate?

Cheers,
Marc

Welcome back, Mark. 

I have to join in to Viethson's post but I wouldn't say that it drifts too fast but faster than on the Concorde for example. I usually start my DME update at the gate (if I get reception from a DME of course), so that I don't have to care much on the initial climb until level off.

Maybe they've tweak the behavior on the Conc as she really needs the accuracy there and travels a lot fast while developing a higher need for fast updates.

I'm not so much into the actual gauges and I also haven't really measured the loss if alignment, but my subjective feeling is the same as Viethson's, the gauges in our birds are more sensible.

Maybe some rw flyer can explain what actually leads to faster loss of alignment. I could image that a straight and level flight will hold the INS in shape while all turns and climbs lead to fast misalignment.
As you turn and climb out your SID, you may therefore have the highest need for an updated INS.

Maybe Lou drove some of the former INS navigated birds then.

Otherwise a former real Concorde pilot would be welcome too as this one was INS only.