tttocs

Pop Up?

Recommended Posts

OK, here's my dumb question of the day.  With the old V1 430/530 I used to be able to click on the screen in the panel and get a popup display.  I've installed the new 530 in the Carenado 337 (with no issues whatsoever), but I can't figure out how to get a popup when needed.

Scott

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi Scott,

Not a dumb question. I also have the 337 and have discovered clicking on screen is indeed not working. I think when Carenado updated the 337 for P3Dv4 somehow it disappeared. However looking in the panel.cfg file there are entries for the toggle command. On the plus side all the buttons on the bezel work.

Also the Collins radios don't work either.

Bert Pieke provided a fix here.

https://www.avsim.com/forums/topic/517134-p3dv4-version-with-gtn-option/

Share this post


Link to post
Share on other sites

Bill, thanks for the link.  As I noted in that thread, they also managed to re-introduce the fuel pump switch bug from the original release.  Good grief.

I do note that Shift+1 does produce a popup of the GPS.  It's got some corrupted graphics at the top of the bezel, but it is usable.

Scott

Share this post


Link to post
Share on other sites

Hi Scott, can you please post a screenshot of the 'corrupted' graphics?

Share this post


Link to post
Share on other sites
9 minutes ago, RXP said:

Hi Scott, can you please post a screenshot of the 'corrupted' graphics?

Sure thing.  I won't be at my flight sim computer until this evening (US - Mountain time) but I'll get a screen grab then.  Thanks!

 

Scott

Share this post


Link to post
Share on other sites

Hi, a picture is worth a thousand words! It looks like there is another GNS gauge atop. From the look of it I suspect the kind of gauge which serves the purpose of triggering a popup window (which is not needed with our GNS V2 since we take care of this in the GNS V2 itself).

You might want to review (and share here for others) the content of this particular window section from your panel.cfg file to confirm.

Share this post


Link to post
Share on other sites

Humm! The 337 is the aircraft where I have had the greatest success with clicking on the 530v2 in the VC and getting a pop up; and then being able to click on the 2D pop up to close it back to the VC.  Will say that my clickspot on the 530v2 in the VC is at the bottom center of the gauge at that small circular hole below the MSG and FPL buttons. The click area to close the 2D pop up is about anywhere in the 2D popup 530's screen area.

As you might guess from the Window07 text, I configured the 530_v2 in the 337 by editing my previous panel.cfg file.

//--------------------------------------------------------
[Window07]
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=rxpGNS!GNS530,  0,0,520,378
gauge00=rxpGNS2!GNS_530_1,  0,0,520,378
gauge01=CCTC!Toggle_GPS,  87,28,348,260
 

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$C530_GPS_N

//gauge00=rxpGNS!GNS530,0,  0,256,184
gauge00=rxpGNS2!GNS_530_1  ,0,  0,256,184
gauge01=CCTTS!Toggle_GPS,  87,28,348,260

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

I have this added to the RealityXP.GNS.ini but it should have no influence since I have not called upon it in the panel.cfg file and the ident= variable doesn't even match.

[GNS_530_1.TOGGLE_RXP]
popleft = 15531

 

 

  • Upvote 2

Share this post


Link to post
Share on other sites
2 hours ago, RXP said:

Hi, a picture is worth a thousand words! It looks like there is another GNS gauge atop. From the look of it I suspect the kind of gauge which serves the purpose of triggering a popup window (which is not needed with our GNS V2 since we take care of this in the GNS V2 itself).

Perhaps I'm not understanding how the new tools work.  All I'm doing is replacing the existing Carenado GNS with the RXP gauge using the RXP tool.  This seems to work well in replacing the panel GPS (but with no click to pop up).  I'm doing nothing else.

As soon as I get time, I'll start digging into the panel.cfg to see if I can make sense of what's being done.

1 hour ago, fppilot said:

Humm! The 337 is the aircraft where I have had the greatest success with clicking on the 530v2 in the VC and getting a pop up; and then being able to click on the 2D pop up to close it back to the VC.  Will say that my clickspot on the 530v2 in the VC is at the bottom center of the gauge at that small circular hole below the MSG and FPL buttons. The click area to close the 2D pop up is about anywhere in the 2D popup 530's screen area.

As you might guess from the Window07 text, I configured the 530_v2 in the 337 by editing my previous panel.cfg file.

Frank, are you running the Carenado utility first or just the RXP tool? 

Scott

Share this post


Link to post
Share on other sites
1 hour ago, tttocs said:

Perhaps I'm not understanding how the new tools work.  All I'm doing is replacing the existing Carenado GNS with the RXP gauge using the RXP tool.  This seems to work well in replacing the panel GPS (but with no click to pop up).  I'm doing nothing else.

As soon as I get time, I'll start digging into the panel.cfg to see if I can make sense of what's being done.

Frank, are you running the Carenado utility first or just the RXP tool? 

Scott

Hi Scott,

Frank got it working. Click spot to popup by adding an extra window.

1. Run Carenado utility RXP530C337.exe first.

2. Go to Addons menu to setup aircraft for the GNS. Don't use the bezel option.

http://zk62kP3.jpg

 

3. Close sim, open panel.cfg, add the following window from Frank's above. My window number is [Window06]. Add Window# at top to Window titles. My entry: Window06=RXP GNS530v2

Add:

[Window07]
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=rxpGNS!GNS530,  0,0,520,378
gauge00=rxpGNS2!GNS_530_1,  0,0,520,378
gauge01=CCTC!Toggle_GPS,  87,28,348,260

 

Edit from Frank's above. Except I resized and positioned the click spot area for GNS popup. It is back on the top border of the bezel as usual. Red line below. Click in popup screen to close.

[Vcockpit02]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$C530_GPS_N

gauge00=rxpGNS2!GNS_530_1, 0, 0,256,184
//gauge00=GPS_530_3D_337!GPS_530,  0,0,256,186
//gauge01=CARC337!ToggleCAR530,    64,0,384, 32
gauge01=CCTTS!Toggle_GPS,  0,0,260,20

 

I didn't add the following to RealityXP.GNS.ini. Works without this.

[GNS_530_1.TOGGLE_RXP]
popleft = 15531

My panel.cfg. Also includes Collins radio fix.

Spoiler

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Wednesday, November 01, 2017 at 01:10 FSPS Build:20340

[Window Titles]
Window00=GNS530XP
Window01=Manual
Window02=WINDOW MANAGER
Window03=INFO
Window04=ENGINE SETUP
Window05=KNOB INFO
Window06=RXP GNS530v2

//--------------------------------------------------------
[Window00]
Background_color=8,8,8
size_mm=524,378
position=7
visible=0
ident=0
window_size= 0.310, 0.370
window_pos= 0.650, 0.060
no_luminous=1
zorder=7

gauge00=rxpGNS2!GNS_530_1,  0,0,520,378
gauge01=CCTTS!Toggle_GPS,  85,28,353,264


//--------------------------------------------------------
[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=C337Manual!manual,  0,0,1000,1000


//--------------------------------------------------------
[Window02]
Background_color=0,0,0
size_mm=500,237
position=0
visible=0
ident=796
window_size= 0.237, 0.200
window_pos= 0.020, 0.150
zorder=5

gauge00=CARC337!Control_windows,  0,0,500,237


//--------------------------------------------------------
[Window03]
file=info.bmp
size_mm=555,142
window_size_ratio=1.000 
position=0
visible=1
ident=10030
window_size= 0.264, 0.120
window_pos= 0.020, 0.030

gauge00=CARC337!Toggle10030,  0,0,25,25


//--------------------------------------------------------
[Window04]
Background_color=0,0,0
size_mm=600,490
position=3
visible=0
ident=10020
nomenu=1
window_size= 0.344, 0.500
window_pos= 0.000, 0.000

gauge00=GAUGEC337!StartWindowsAircraft,  0,0,600,490
gauge01=CARC337!Toggle10020,  0,0,0


//--------------------------------------------------------
[Window05]
Background_color=0,0,0
size_mm=600,490
position=5
visible=0
ident=10050
nomenu=1
window_size= 0.344, 0.500
window_pos= 0.000, 0.000

gauge00=GAUGEC337!StartWindows,  0,0,600,490


//--------------------------------------------------------
[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,  87,28,348,260


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

gauge00=RadioC337XML!Radio_AudioCollins,  0,0,292,65
gauge01=RadioC337XML!Radio_Collins_NAV_COM,  0,180,291,115
gauge02=RadioC337XML!RadioTransVC,  0,370,300,74
gauge03=CCTTS!DME_screen,  0,68,268,108
gauge04=GAUGEC337!Radio_KR87_ADF,  0,294,300,75
gauge05=CCTTS!GEM6,  297,0,214,211


//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$C530_GPS_N

gauge00=rxpGNS2!GNS_530_1,  0,0,256,184
gauge01=CCTTS!Toggle_GPS,  0,0,260,20


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

gauge00=RadioC337!RadioTrans,  0,370,300,74
gauge01=CC337!ALTqnh,  370,0,20,20
gauge02=GAUGEC337!Gauge_UPDATE_DIG,  0,0,1,1
gauge03=CarSound_C337!CarSound,  0,0,1,1


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

gauge00=CCTTS!Toggle_GPS,  87,28,348,260

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

 

 

 

  • Upvote 2

Share this post


Link to post
Share on other sites

OK, that helps.  I started by NOT running the Carenado utility.  Doing so first and then using the no-bezel option makes sense.  Will try this way later today and take a look at the additional changes Frank and you suggest.  I feel a bit like a rookie starting over with this stuff.

Thanks much to both of you!

Scott

Share this post


Link to post
Share on other sites
12 hours ago, tttocs said:

Frank, are you running the Carenado utility first or just the RXP tool? 

Scott and others,

My legacy RXP .ini file for the 337 is dated in 2011 and I honestly after that much time do not recall. If I ran an RXP tool then it was the v1, now called legacy  tool.

Share this post


Link to post
Share on other sites
50 minutes ago, fppilot said:

My legacy RXP .ini file for the 337 is dated in 2011 and I honestly after that much time do not recall. If I ran an RXP tool then it was the v1, now called legacy  tool.

For the legacy 337 and 530 I don't recall doing anything other than running the Carenado tool.  I was actually wondering if your ran the tool first for V2, but Bill cleared that point up for me.

Thanks,

Scott

Share this post


Link to post
Share on other sites

I do not have this issue of popups figured out at all.  I have become successful in using the RXPv2 process of Ident= and popleft= to get a 2D popup from the VC gauge. But I have found little success in closing the popups back to the VC.  Seems the success I have found is because in their aircraft Caranado has included ToggleGPS.xml files in their .CAB gauge files.  And I do not fully understand the variables that follow the ToggleGPS calls.  So that becomes trial and error on my part.

What happens with simply using the RXPv2 method of Ident= and popleft is that it provides a click area on the VC gauge, but to close the 2D popup requires again clicking on the same click area on the VC gauge.  That presents an issue with the way I position my popups.  Below is an example from my Milviz Baron B55.  The upper photo shows the RXPv2 gauges in the VC. The lower photo shows that the 2D popup (array of two gauges together) blocks mouse pointer access to the VC gauges.  So I must either drag the 2D array out of the way, or change VC view up or down until I can see the VC RXP's, or configure a yoke button to toggle my appropriate panel.cfg [window##] on and off.

Anyone know how to configure a clickspot on the 2D popup gauge array in this case?

http://b55_RXPv2_2-XL.jpg

Share this post


Link to post
Share on other sites

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.

 

 

  • Upvote 1

Share this post


Link to post
Share on other sites

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

  • Upvote 1

Share this post


Link to post
Share on other sites
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!

Share this post


Link to post
Share on other sites
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!

Share this post


Link to post
Share on other sites

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://C9hrIK1.jpg?1

 

 

 

  • Upvote 2

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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

  • Upvote 1

Share this post


Link to post
Share on other sites

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.

 

 

Share this post


Link to post
Share on other sites
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,

  • Upvote 1

Share this post


Link to post
Share on other sites
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

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now