I'm sorry, guys, I don't get the point here.
Is there something wrong with my tutorial (which was updated to 1.3 and the expansions lately) or are you describing something else?  :-/

For the guys who had the 1.2 version of the tutorial before, there aren't big changes, only the AP popup window (which is [Window04]) had been given a "save" gauge entry to make it work for all variants.
If you just use the 707 passenger model, you don't need to change it and therefore can leave out the 1.3 update.
If you are using the variants like Cargo, E-3 or Air Force One, you have to use the new 1.3-aware entry of course.


Mark, to avoid confusion, I suggest to "mark"  ;D your Civa integration more clearly as e. g. "Single Unit integration" or so.
Otherwise a new customer or visitor stumbles upon this thread and gets all kinds of config entries, mixing them up and also (and most of all) asking questions about it, while we don't know to which edit he's referring to.

So I might accidentally answer some question the wrong way since I don't know what thing the guy is using.

[edit]So "Civa Double INS Integration" is CoolP's solution
and "Single Unit Integration" is Markoz's solution
for example.
The "default Civa Integration" (from CS itself) offers a third variant here and it really makes a difference which one is used when some questions are asked. That's my point here.  :)[/edit]


I have another suggestion, but this needs some approval from CS of course.
We could offer the complete panel.cfg file for each model. To download and to just drop into the corresponding folder.
I've avoided this for copyright reasons, but if it get's approved, I could attach all four (=all variants covered) panel.cfg files for the guys.
They would just have to backup their original stuff first while avoiding any error source there is. I would just have to make sure that those files are always updated to the current 707 build.
So currently, you would find a "1.3 panel.cfg package for Civa Double INS Integration" there.
What do you think?

So under Mark's solution there would be such a download, under mine, and so on. Just drop and forget those files, no need to read, observe or understand anything. So the workload on both sides (customer and "support") would be reduced and the integration would be made very simple.

I've just asked CS for approval, results to come.