The problem seems to be that the panel configuration app isn't pointing to the panel config xml file in the various planes' panel folders,
and changing the values there. Let me show you what I mean.
Let's take the Citabria as an example. If you go into the Citabria's Panel folder, you'll see a sub-folder called "Config". Inside that is an
xml file called "Panel Config". Right click on that and select "Edit" (if you're not comfortable editing these files, you should do a backup
first). Inside, you'll see strings of the following sort (I'll choose the "show autopilot" as an example):
<Element>
<Select>
<Value>(G:Var1) 0 == if{ 0 (>L:Scout Autopilot Visible,bool) }</Value>
</Select>
The "0" in the middle of the string after "if{ " means that that device (in this case the autopilot) will not show in the Citabria's panel. If
you change that "0" to a "1", so the string now reads :
<Element>
<Select>
<Value>(G:Var1) 0 == if{ 1 (>L:Scout Autopilot Visible,bool) }</Value>
</Select>j
..the autopilot will now show in the Citabria's panel. And so on with all the other instruments listed in the various strings. You just
have to figure out which strings should be on ("1") to show the device, and which strings should be off ("0") so the device won't
show, for any particular configuration (not everything listed can show at the same time). And you need to do this for each of the
various aircraft in the package (Citabria, Decathalon, Scout, etc.).
Of course if you still have FSX installed, you can configure the panels for the various planes there, and then just copy over the relevant
"Panel Config" xml files.
The real solution would be if someone fluent in xml-ese could point the panel configuration app in P3Dv4 to the "Panel Config" xml file
in the planes' Panel folders and get the values to change, but that's beyond me.
I hope that helps.
-RobM
