This is totally brilliant..

Not only does the new RXP GPS500 look great in the B60:

gauge19=rxpGNS2!GPS_500_1, 50, 660, 360, 240,VC_settings

gauge20=CustomB60!GPS_Buttons, 0, 0, 1, 1

with:

In the RealityXP.GNS.ini file for the B60:

[GPS_500_1]
...
; uses Simulator GPS commands if true.
UseSimGpsCmds = true

and

[GPS_500_1.VC_Settings]
; show screen only gauge if true.
nobezel = true

 

But the GPS_Buttons gauge actually ties the 3d buttons and knobs to the GPS 

Try this as a start:

<Gauge Name="GPS 500 buttons" Version="1.0">

<!-- Trigger GPS 500 commands -->
   
<Element>
     <Select>
      <Value>

   (L:mdlZoomOutButton,bool) if{
   0 (>K:GPS_ZOOMOUT_BUTTON)
   0 (>L:mdlZoomOutButton,bool) }

   (L:mdlZoomInButton,bool) if{
   0 (>K:GPS_ZOOMIN_BUTTON)
   0 (>L:mdlZoomInButton,bool) }

   (L:mdlDTOButton,bool) if{
   0 (>K:GPS_DIRECTTO_BUTTON)
   0 (>L:mdlDTOButton,bool) }

   (L:mdlNrstButton,bool) if{
   0 (>K:GPS_NEAREST_BUTTON)
   0 (>L:mdlNrstButton,bool) }

   (L:mdlEntButton,bool) if{
   0 (>K:GPS_ENTER_BUTTON)
   0 (>L:mdlEntButton,bool) }

   (L:mdlClrButLSingle,bool) if{
   0 (>K:GPS_CLEAR_BUTTON)
   0 (>L:mdlClrButLSingle,bool) }

   (L:mdlMSGButton,bool) if{
   0 (>K:GPS_MSG_BUTTON)
   0 (>L:mdlMSGButton,bool) }

   (L:mdlBottomLeftKnob,bool) if{
   0 (>K:GPS_PAGE_KNOB_DEC)
   0 (>L:mdlBottomLeftKnob,bool) }

   (L:mdlBottomRightKnob,bool) if{
   0 (>K:GPS_PAGE_KNOB_INC)
   0 (>L:mdlBottomRightKnob,bool) }
       
      </Value>      
     </Select>
   </Element>
</Gauge>
 

 

 

 

Hi Bert,

Where do we find the GPS_Buttons gauge?

David

 

1 hour ago, Bert Pieke said:

Not only does the new RXP GPS500 look great in the B60:

Bert, can you show me a pic of this?  Trying to imagine what a 500 would look like in the Duke.

47 minutes ago, Gregg_Seipp said:

 

Bert, can you show me a pic of this?  Trying to imagine what a 500 would look like in the Duke.

The Duke comes with a GPS500 default.. this is simply a better version.

1 hour ago, DavidP said:

Hi Bert,

Where do we find the GPS_Buttons gauge?

David

I can send you my panel, if you give me your email via PM, or you can create an xml file with the text that I provided.

14 minutes ago, Bert Pieke said:

I can send you my panel, if you give me your email via PM, or you can create an xml file with the text that I provided.

Hi Bert,

I modified the Turbine Duke but the vc buttons don't function. Is the B60 different from the Turbine in that regard?

In the panel.cfg file for the Turbine there was no reference to any button gauge.

Edited August 29, 20178 yr by bills511

43 minutes ago, bills511 said:

Hi Bert,

I modified the Turbine Duke but the vc buttons don't function. Is the B60 different from the Turbine in that regard?

In the panel.cfg file for the Turbine there was no reference to any button gauge.

Same situation, I would imagine.

I have a GTN750 in the TDuke.

That button gauge does not come with the airplane, you'll need to create it, based on my example.

Maybe someone can expand on my concept..

2 hours ago, Bert Pieke said:

I can send you my panel, if you give me your email via PM, or you can create an xml file with the text that I provided.

Hi Bert

I'll have a try myself and see if I can make it work. Where does one place the file when completed?

6 hours ago, Bert Pieke said:

The Duke comes with a GPS500 default.. this is simply a better version.

Ah.  I had it confused with the G500...which is still in development.  That'll be nice to replace those G500s in the Carenado planes.

Thanks Bert, I actually have your solution working in the B60! I will install a pop up window for full functionality but your solution is great until (hopefully) a full functioning method can be found.

I just wonder how they got the GNS530 bezel in the old FSX days when RXP GPS's were selected in the configuration manager?

11 hours ago, Bert Pieke said:

Same situation, I would imagine.

I have a GTN750 in the TDuke.

That button gauge does not come with the airplane, you'll need to create it, based on my example.

Maybe someone can expand on my concept..

Thank You Bert!

I got it working.

All buttons work except the outer ring adjust knob, OBS, FPL and MENU. The CLR button works except holding down to return to the NAV page.  On the VC bezel there is a button for TERR but is not on RXP as TERR is accessed using the inner ring knob. Otherwise the buttons I use most of the time are the ones that work.

What I did:

Named XML GPS500Buttons.xml (used your XML contents).

Added Gauge25 to panel.cfg

gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1
gauge24=Config!ModelOptions, 1020, 1023, 1, 1
gauge25=Config!GPS500Buttons, 1020, 1023, 1, 1 (Not sure what the numbers do so I just used the same from the other lines.)

Looking closer at your xml lines I now see why the other buttons don't work...DUH. Sometimes I feel like a nut.

Edited August 29, 20178 yr by bills511

16 minutes ago, bills511 said:

Thank You Bert!

I got it working.

All buttons work except the outer ring adjust knob, OBS, FPL and MENU. The CLR button works except holding down to return to the NAV page.  On the VC bezel there is a button for TERR but is not on RXP as TERR is accessed using the inner ring knob. Otherwise the buttons I use most of the time are the ones that work.

 

Just keep adding the missing functions, using the same pattern. 

The variable names can be found in the RAS_gps_500.xml file, in the fs9gps.cab file.

43 minutes ago, Bert Pieke said:

Just keep adding the missing functions, using the same pattern. 

The variable names can be found in the RAS_gps_500.xml file, in the fs9gps.cab file.

Thanks Bert that's what I shall do. But first I have yard work to do.

Quick note: the bug in parsing the RAS Duke VC Panel gauge size is now corrected, and we're adding a new option in the settings panel: "Use Legacy 3rd Party Aircraft Panel (L:vars)" in case it helps with Real Air, and in fact all aircraft configured with our legacy GNS.

This setting simply exports additional L:vars once used to synchronize some 'state' between the aircraft and our legacy GNS, such as knob rotation in 3D and in our gauge, as well as GNS power - used to display/hide the 3D screen polygons for example).

We're further working on the few issues reported in the forum and we'll make an update quickly with this and more.

Awesome news, thank you!