Pop Up?

[Indy511 686]

Hi Frank,

I know what you mean. Those darn windows are in the way.

Prepar3Dv4 panel configuration file SDK

[Window06]
Background_color=255,255,255
size_mm=520,378
window_size_ratio=1.000 
position=0
visible=0
ident=794
window_size= 0.270, 0.330
window_pos= 0.730, 0.670
zorder=15

gauge00=rxpGNS2!GNS_530_1,  0,0,520,378
gauge01=CCTC!Toggle_GPS,  90,30,350,260

Position perimeter in windows sections.

Specifies the relative position of a panel window to the main window. A number from 0 to 8 (as shown below) designates the position of the panel window. If nothing is specified, 7 is the default, otherwise, one of:

0 = upper-left corner
1 = upper-middle side
2 = upper-right corner
3 = middle-left side
4 = middle
5 = middle-right side
6 = lower-left corner
7 = lower-middle side
8 = lower-right corner

[Indy511 686]

9 minutes ago, RXP said:

Hi Frank,

The system is flexible in that you can assign a group of setting for a particular instance.

In this case, you'd need a section for the VC gauges, and 1 section for the popup gauges.

Your panel.cfg file then resemble this:

[window##]
ident = GPS_PANEL
gauge00= rxpGNS2!GNS_530_1 , x, y, w, h, MY_POPUP_COMBO
gauge01= rxpGNS2!GNS_430_2 , x, y, w, h, MY_POPUP_COMBO

[VCocpit##]
gauge00= rxpGNS2!GNS_530_1 , x, y, w, h, MY_VC_COMBO
gauge01= rxpGNS2!GNS_430_2 , x, y, w, h, MY_VC_COMBO

You RealityXP.GNS.ini file will have these sections:

[GNS_530_1.MY_POPUP_COMBO]
popleft= GPS_PANEL

[GNS_430_2.MY_POPUP_COMBO]
popleft= GPS_PANEL

[GNS_530_1.MY_VC_COMBO]
popleft= GPS_PANEL

[GNS_430_2.MY_VC_COMBO]
popleft= GPS_PANEL

This way, you can toggle the popup window from any screen (430 or 530, VC or popup).

In addition, each gauge can be individually tailored to specific settings since you've created a section for each.

Of course, if you don't need any customization, you can reuse the 'DEFAULT' section instead. This way, just use the default popleft= and this will apply to all instances of the gauge (VC or popup window).

Alternatively, if you need customization not dependant on VC or popup, you can just use MY_POPUP_COMBO as the 5th param of the VC gauges, and remove the 2 'MY_VC_COMBO' sections from the ini file!

 

The basics are simple:

1) Each gauge (GNS_530_1) can have 1 or more instance in the panel.cfg.

2) All instances are the same gauge (logic), just different representation (size).

3) Settings in the section with the gauge name apply to the gauge (to all instances).

4) Settings in the section with the 5th param apply only to the instance using the same 5th param.

5) If no 5th param specified, the 'DEFAULT' section applies to the instance (as if you'd manually add DEFAULT as the 5th param)

6) The 5th param 'NO_BEZEL' doesn't require a section (as of v2.3.5), It sets the instance nobezel=true.

 

 

Thank you Jean-Luc!

[fppilot 4,355]

1 hour ago, RXP said:

Hi Frank,

The system is flexible in that you can assign a group of setting for a particular instance.

In this case, you'd need a section for the VC gauges, and 1 section for the popup gauges.

Your panel.cfg file then resemble this:

[window##]
ident = GPS_PANEL
gauge00= rxpGNS2!GNS_530_1 , x, y, w, h, MY_POPUP_COMBO
gauge01= rxpGNS2!GNS_430_2 , x, y, w, h, MY_POPUP_COMBO

Obviously knew the fifth parameter applied to the VC gauge but had no idea a fifth parameter would apply to a [window##] gauge. Thanks!

[Indy511 686]

OK after figuring this out there are the 2 perimeters; position=, and window_pos=. The easiest way to position popup is using position=

0 = upper-left corner
1 = upper-middle side
2 = upper-right corner
3 = middle-left side
4 = middle
5 = middle-right side
6 = lower-left corner
7 = lower-middle side
8 = lower-right corner

However window_pos= must be commented out // or deleted for the above method to work. It appears having window_pos= present overrides any position= setting.

window_pos= allows a more precise positioning for instance having 2 gps units one above the other.

 window_pos= 0.000, 0.000 positions popup to top left corner.

[Window06]
Background_color=255,255,255
size_mm=520,378
window_size_ratio=1.000
position=6
visible=0
ident=794
window_size= 0.270, 0.330
//window_pos= 0.730, 0.670
zorder=15

gauge00=rxpGNS2!GNS_530_1,  0,0,520,378
gauge01=CCTC!Toggle_GPS,  90,30,350,260

http://

 

 

 

[fppilot 4,355]

4 minutes ago, fppilot said:

Obviously knew the fifth parameter applied to the VC gauge but had no idea a fifth parameter would apply to a [window##] gauge. Thanks!

Also just saw and had not realized that the ident= variable could be a setting name. Thought it had to be a number.

[RXP 2,338]

18 minutes ago, fppilot said:

ident= variable could be a setting name. Thought it had to be a number.

It can only be a name in a list of pre-defined names. The 'bible' for all this is the SDK:

https://www.prepar3d.com/SDKv4/sdk/panels_and_user_interface/panels/panel_configuration_files.html

see the entry for 'ident'

[tttocs 301]

A lot of good information here.  Many thanks to all, but especially to Bill and Frank.  Got the 337 working well, though I've cook-booked things a bit.  Will have to take some time to fully understand all of the pieces so that I can apply what I've learned to other planes.

I did not use no-bezel, as I can't figure out how to do that from the config tool, but no matter for now.  All is working as it should and I'll figure the rest out as I go along.

Thanks to all,

Scott

[fppilot 4,355]

Has anyone had success getting a popup from the VC in the Carenado Centurion C210?  I have tried all the methods in this thread and am not finding success.  I can open a 2D popup with my [Window07] using shift-8 or the yoke button I have configured, but I cannot get a 2D popup with my mouse cursor.  It never even changes shape.  Once I have my [window07] popup open, I am successful closing it with the mouse.

 

 

[fppilot 4,355]

20 minutes ago, fppilot said:

Has anyone had success getting a popup from the VC in the Carenado Centurion C210?  I have tried all the methods in this thread and am not finding success.  I can open a 2D popup with my [Window07] using shift-8 or the yoke button I have configured, but I cannot get a 2D popup with my mouse cursor.  It never even changes shape.  Once I have my [window07] popup open, I am successful closing it with the mouse.

Solved it! Window Reflections needed to be clicked off in the shift-3 Controls Window.   When window reflections are off everything I had been trying all began to work.  If anyone needs an .XML file to set the C210 default for Window Reflections to "off", let me know. I found a 2011 link to a topic here where Bert P. provided one.   I now have it in place,

[Indy511 686]

1 hour ago, fppilot said:

Solved it! Window Reflections needed to be clicked off in the shift-3 Controls Window.   When window reflections are off everything I had been trying all began to work.  If anyone needs an .XML file to set the C210 default for Window Reflections to "off", let me know. I found a 2011 link to a topic here where Bert P. provided one.   I now have it in place,

Are you using the dual unit 530/430 setup? The 210 didn't include a popup for the 430 so I created one. Also, I didn't have the issue of reflections interference.

Spoiler

//*********************************************************
// CARENADO CT210M Centurion II FSX
// Copyright © Carenado 2011 - All Rights Reserved
//*********************************************************

[Window Titles]
Window00=Reality XP GNS 530
Window01=Manual
Window02=Control Windows
Window03=INFO
Window04=Reality XP GNS 430

//--------------------------------------------------------
[Window00]
Background_color=255,255,255
size_mm=520,378
window_size_ratio=1.000 
position=0
visible=0
ident=794
window_size= 0.255, 0.340
window_pos= 0.000, 0.459
zorder=15

gauge00=rxpGNS2!GNS_530_1,  0,0,520,378
gauge01=CCTC!Toggle_GPS,  87,28,348,260

//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=1000,1000
window_size_ratio=1.000 
position=0
visible=0
ident=793
window_size= 0.440, 0.773
window_pos= 0.520, 0.040
zorder=0

gauge00=T210MManual!manual,  0,0,1000,1000

//--------------------------------------------------------
[Window02]
Background_color=0,0,0
size_mm=581,153
window_size_ratio=1.000 
position=0
visible=0
ident=796
window_size= 0.321, 0.150
window_pos= 0.020, 0.170
zorder=5

gauge00=CCTC!Control_windows,  0,0,581,153

//--------------------------------------------------------
[Window03]
file=info.bmp
size_mm=345,157
window_size_ratio=1.000 
position=0
visible=1
ident=142
window_size= 0.161, 0.116
window_pos= 0.020, 0.040

//--------------------------------------------------------
[Window04]
Background_color=0,0,0
size_mm=100,100
position=0
visible=0
ident=10010
window_size= 0.255, 0.199
window_pos= 0.000, 0.801
zorder=99

gauge00=rxpGNS2!GNS_430_1,  0,0,100,100
gauge01=C90KA!ToggleCAR430,  12,35,73,31

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$C530_GPS

gauge00=rxpGNS2!GNS_530_1,  0,0,256,184
gauge01=rxpGNS2!GNS_430_1,  0,185,169,71
gauge02=CCTC!Toggle_GPS,  21,0,208,10
gauge03=C90KA!ToggleCAR430,  16,186,137,11

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0
size_mm=512,512
visible=1
pixel_size=1024,1024
texture=$RadiosC114

gauge00=RadioC210!RadioAudio,  0,0,297,57
gauge01=RadioC210!Radio_KR87_ADF,  0,321,300,75
gauge02=DigTrans!transponder,  0,166,297,74
gauge03=APBK!Autopilot,  0,242,297,78
gauge04=DME!DME_screen,  302,212,210,82
gauge05=CCTC!Temp,  334,338,150,150
gauge06=CCTC!Oxygen,  3,398,115,114
gauge07=CCTC!Gear_light_red,  124,463,40,40
gauge08=CCTC!Gear_light_green,  124,419,40,40
gauge09=CCTC!Panel_annunciator,  301,114,207,93
gauge10=CCTC!Test_Light,  181,461,40,40
gauge11=CCTC!ELT_Light,  181,416,40,40
gauge12=CCTC2!ALTqnh,  490,0,20,20

Day=255,255,255
Night=255,255,255
Luminous=201,64,64

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=3500

 

[fppilot 4,355]

42 minutes ago, bills511 said:

Are you using the dual unit 530/430 setup? The 210 didn't include a popup for the 430 so I created one. Also, I didn't have the issue of reflections interference.

Yes. I have a 530/430 array.  On the reflections check Shift-3 and see if the selection is turned off.  If so you likely have a subfolder named "controls" to your C210 "panel" folder with a small .xml file in it and an added gauge calling it in one of your [vcockpit##] sections.  If you have that folder, file, and related panel.cfg entry then the reflections are off as the default when you load the C210.

[fppilot 4,355]

FYI Back to the C337. I noted today that it too has the window reflections automatically set to on. So I tried the same technique with it but failed. I removed the reflections and tried the RXPv2 .ini and .cfg settings that have worked with other aircraft and could not get any clickspot at all on my 520 v2 in the VC. So I reverted to the settings found earlier in this topic, which provides at least a small clickspot.

[Indy511 686]

46 minutes ago, fppilot said:

Yes. I have a 530/430 array.  On the reflections check Shift-3 and see if the selection is turned off.  If so you likely have a subfolder named "controls" to your C210 "panel" folder with a small .xml file in it and an added gauge calling it in one of your [vcockpit##] sections.  If you have that folder, file, and related panel.cfg entry then the reflections are off as the default when you load the C210.

Very odd. I just double checked and having reflections on or off didn't make any difference. I used the original Carenado panel setup and my RXP setup. No difference. Also I don't have the controls folder either. I'm using P3Dv4.1 if that means anything. I did have the reflections issue back when I had FSX.

[fppilot 4,355]

From: RealityXP.GNS.ini

|----------------------------------

[GNS_430_2.TOGGLE_430]
popleft = 15531

[GNS_530_1.TOGGLE_530]
popleft = 15531

[GNS_430_2.UNPOP_430]
popleft = 15531

[GNS_530_1.UNPOP_530]
popleft = 15531
 

=====================================================

From panel.cfg:

//--------------------------------------------------------

[Window07]
size mm=400, 480
window_pos=0.79000,0.48000
window_size=0.20507,0.49275
visible=1

zorder=99
ident=15531
gauge00=rxpGNS2!GNS_530_1,0,0,100,62, TOGGLE_530    
gauge01=rxpGNS2!GNS_430_2,0,62,100,38, TOGGLE_430 

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$C530_GPS

gauge00=rxpGNS2!GNS_530_1  ,0,  0,256,184, UNPOP_530
gauge01=rxpGNS2!GNS_430_2  ,0,185,169, 71, UNPOP_430
gauge02=Controls!IR_Off, 0,0,1,1

=========================== 

The contents of the xml file IR_Off.xml:

<?xml version="1.0"?>

-<Gauge Version="1.0" Name="IR_off">

<!-- No instrument Reflections -->

       <Element>

                 <Select>

                                    <Value> (L:InitIR,bool) ! if{ 1 (>L:WINDOWSTINTBOOL2,bool) 1 (>L:InitIR,bool)} </Value>

                </Select>

           </Element>

</Gauge>

[tttocs 301]

7 hours ago, fppilot said:

Solved it! Window Reflections needed to be clicked off in the shift-3 Controls Window.   When window reflections are off everything I had been trying all began to work.

No surprise there Frank.  In FSX with the legacy 530/430 I never could get popups on the 210 to work without turning off reflections.  There are a few other Carenado products that behave similarly.  Just another one of those Carenado-isms I guess.  I've installed the 210 in v4 but haven't started playing with it yet.

Meanwhile, I've been using the 337 as my test subject for my new P3D setup as it's a plane I like and is relatively easy to fly so that I can focus on setup issues.  Did my first complete P3D v4 flight from KSTS to KRDD tonight (Orbx NorCal and both airports) and I'm very pleased with the combination of v4 and my new hardware.  Not a single glitch, hiccup or stutter.  The next challenge relative to the v2 530 came when I tried to do the GPS (LPV) approach into KRDD.  No joy on glideslope display, unfortunately.  Horizontal guidance was fine, but the GS display never came alive on the HSI.  Any thoughts?

Scott