fppilot

GTN 750 in A2A Comanche VC knobs/buttons config request

Recommended Posts

Has anyone been successful getting Ryan Butterworth's "f1vc.xml " gauge to work with the GTN 750 in the A2A Comanche to get operating knobs and keys in the virtual cockpit?  I am using rxpGTN_750_2 in both the A2A C182 and Comanche 250.  In the A2A C182 the f1vc.xml gauge works fine.  I am using the same rxpGTN_750_2 gauge in the Comanche and a same-name gauge subfolder (rxpGTN) in the Comanche's panel folder with an identical f1vc.xml file.  i.e. the parameter line, line 17, is the same in both the files for the 182 and for the Comanche.  But though it works in the C182, it is not working for me in the Comanche.

Pertinent contents of my panel.cfg file and my f1vc.xml for the Comanche are in the window below.

 

Spoiler

//===========
//Here are my f1vc.xml file contents
//============

 

<Gauge Name="f1vc" Version="2.04">

<!-- Reality XP GTN Buttons Bridge -->
<!-- Bridges Reality XP GTN 750/650 Touch with f1 3D bezel -->
<!-- Credits: Reality XP, Sean Moloney and Ryan Butterworth -->

<Element>
  <Select>
    <Value>
        (L:F1GTNMOUSE,bool) 0 !=
        if{
            (L:F1GTNMOUSE,bool) 0x0001FA01 - sp0
            l0 28 / int sp1 l0 28 % sp0
            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 8 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->

      0 0 0 8      4   l1  case  4  2  l0 1  &amp;  ?  +  sp1

            l0 0 == l0 1 == or if{ l1 (>K:GPS_MENU_BUTTON) }
            l0 2 == l0 3 == or if{ l1 (>K:GPS_DIRECTTO_BUTTON) }                
            l0 4 == l0 10 == or if{ l1 8 &amp; (>K:GPS_BUTTON2) }
            l0 6 == l0 11 == or if{ l1 8 &amp; (>K:GPS_BUTTON3) }
            l0 8 == l0 9 == or if{ l1 (>K:GPS_BUTTON1) }
            l0 12 == l0 18 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_INC) }
            l0 14 == l0 19 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_DEC) }
            l0 20 == l0 26 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_INC) }
            l0 22 == l0 27 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_DEC) }
            l0 24 == l0 25 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }    
            l0 16 == l0 17 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }    
            0 (>L:F1GTNMOUSE,bool)            
        }           
    </Value>      
  </Select>
</Element>
</Gauge>

======  And from my panel.cfg file ========

//--------------------------------------------------------
[Vcockpit00]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle

gauge01=A2A_PA24!code_pa24_r, 1,1,1,1
gauge02=A2A_PA24!status1,2,2,2,2
gauge03=A2A_PA24!damage,    3,3,3,3
gauge04=accusim_xml!code_s,    4,4,4,4
gauge05=A2A_Accusim!lua,    5,5,5,5
gauge06=A2A_Accusim!AVS,    6,6,6,6
gauge07=A2A_Accusim!events,    7,7,7,7
gauge08=A2A_Accusim!random,    8,8,8,8
gauge09=A2A_Accusim!storage,    9,9,9,9
gauge10=A2A_PA24!code_pa24_m, 1,1,1,1
gauge11=gps!gps_500,    0, 0, 1065, 675
gauge12=A2A_PA24!number, 779, 502, 240, 67
gauge13=Comanche!avionics, 0, 576, 1024,447  //AVIONICS DLL
gauge14=A2A_PA24!GPS_F1_750, 1, 1, 1, 1

//NOTE: gauge14 above must stay or the panel reverts to all analog gauges


[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$gauges_lm

gauge00=Comanche_Illumination!gauges_lm, 0, 0, 1024, 1024

[Vcockpit02]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$radiostack_lm

gauge00=Comanche_Illumination!radiostack_lm, 0, 0, 1024, 1024

[VCockpit03]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0

gauge00=rxpGTN!GTN_750_2, 0,0,677,794, POP_NO_BEZEL
gauge01=rxpGTN!f1vc.xml,0,0,1,1
// NOTE: the 5th parameter with gauge00 above is working fluidly with the RealityXP.GTN.ini file setting for popup and no bezel.

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

 

Share this post


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

14 minutes ago, fppilot said:

Has anyone been successful getting Ryan Butterworth's "f1vc.xml " gauge to work with the GTN 750 in the A2A Comanche to get operating knobs and keys in the virtual cockpit?  I am using rxpGTN_750_2 in both the A2A C182 and Comanche 250.  In the A2A C182 the f1vc.xml gauge works fine.  I am using the same rxpGTN_750_2 gauge in the Comanche and a same-name gauge subfolder (rxpGTN) in the Comanche's panel folder with an identical f1vc.xml file.  i.e. the parameter line, line 17, is the same in both the files for the 182 and for the Comanche.  But though it works in the C182, it is not working for me in the Comanche.

Pertinent contents of my panel.cfg file and my f1vc.xml for the Comanche are in the window below.

 

  Reveal hidden contents

//===========
//Here are my f1vc.xml file contents
//============

 

<Gauge Name="f1vc" Version="2.04">

<!-- Reality XP GTN Buttons Bridge -->
<!-- Bridges Reality XP GTN 750/650 Touch with f1 3D bezel -->
<!-- Credits: Reality XP, Sean Moloney and Ryan Butterworth -->

<Element>
  <Select>
    <Value>
        (L:F1GTNMOUSE,bool) 0 !=
        if{
            (L:F1GTNMOUSE,bool) 0x0001FA01 - sp0
            l0 28 / int sp1 l0 28 % sp0
            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 8 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->

      0 0 0 8      4   l1  case  4  2  l0 1  &amp;  ?  +  sp1

            l0 0 == l0 1 == or if{ l1 (>K:GPS_MENU_BUTTON) }
            l0 2 == l0 3 == or if{ l1 (>K:GPS_DIRECTTO_BUTTON) }                
            l0 4 == l0 10 == or if{ l1 8 &amp; (>K:GPS_BUTTON2) }
            l0 6 == l0 11 == or if{ l1 8 &amp; (>K:GPS_BUTTON3) }
            l0 8 == l0 9 == or if{ l1 (>K:GPS_BUTTON1) }
            l0 12 == l0 18 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_INC) }
            l0 14 == l0 19 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_DEC) }
            l0 20 == l0 26 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_INC) }
            l0 22 == l0 27 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_DEC) }
            l0 24 == l0 25 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }    
            l0 16 == l0 17 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }    
            0 (>L:F1GTNMOUSE,bool)            
        }           
    </Value>      
  </Select>
</Element>
</Gauge>

======  And from my panel.cfg file ========

//--------------------------------------------------------
[Vcockpit00]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle

gauge01=A2A_PA24!code_pa24_r, 1,1,1,1
gauge02=A2A_PA24!status1,2,2,2,2
gauge03=A2A_PA24!damage,    3,3,3,3
gauge04=accusim_xml!code_s,    4,4,4,4
gauge05=A2A_Accusim!lua,    5,5,5,5
gauge06=A2A_Accusim!AVS,    6,6,6,6
gauge07=A2A_Accusim!events,    7,7,7,7
gauge08=A2A_Accusim!random,    8,8,8,8
gauge09=A2A_Accusim!storage,    9,9,9,9
gauge10=A2A_PA24!code_pa24_m, 1,1,1,1
gauge11=gps!gps_500,    0, 0, 1065, 675
gauge12=A2A_PA24!number, 779, 502, 240, 67
gauge13=Comanche!avionics, 0, 576, 1024,447  //AVIONICS DLL
gauge14=A2A_PA24!GPS_F1_750, 1, 1, 1, 1

//NOTE: gauge14 above must stay or the panel reverts to all analog gauges


[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$gauges_lm

gauge00=Comanche_Illumination!gauges_lm, 0, 0, 1024, 1024

[Vcockpit02]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$radiostack_lm

gauge00=Comanche_Illumination!radiostack_lm, 0, 0, 1024, 1024

[VCockpit03]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0

gauge00=rxpGTN!GTN_750_2, 0,0,677,794, POP_NO_BEZEL
gauge01=rxpGTN!f1vc.xml,0,0,1,1
// NOTE: the 5th parameter with gauge00 above is working fluidly with the RealityXP.GTN.ini file setting for popup and no bezel.

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

 

I've had it working in some aircrafts but unlike others I've had to double click on the buttons of the VC units to work. I mostly use the popups now... my old eyes. Haven't tried in the Comanche thou.

Share this post


Link to post
Share on other sites
2 minutes ago, BillS511 said:

I've had to double click on the buttons of the VC units to work.

Me too, so I know to try that.  In fact I have to do that for the primary GTN in my Milviz 310 Redux, a 750. But nothing I have tried is working for the secondary GTN in that same aircraft.  The secondary is a 650.

Share this post


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

Me too, so I know to try that.  In fact I have to do that for the primary GTN in my Milviz 310 Redux, a 750. But nothing I have tried is working for the secondary GTN in that same aircraft.  The secondary is a 650.

I just tried it in the Comanche using the 750. No luck. I'll try the A2A 182.

Update: Working in the 182. Dual GTN 650_2, 750_1 setup. Code 8800 in the f1vc.xml file.
I'll try the Milviz 310 dual setup.

Edited by BillS511

Share this post


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

            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 0 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 --> 

      0 0 0 8      4   l1  case  4  2  l0 1  &amp;  ?  +  sp1

This is where it works.

You must use either "8 0 8 0", or "8 8 0 0", but you've configured yours as "0 0 0 8"

The trick is that some vendors use for example 2 F1 #1 units in the same panel (750#1 + 650#1 - see MilViz panel case below), whereas others use a #1 and #2 unit. Because the f1 commands are per-device-type + per-unit#, whereas the RXP commands are per unit# only,  The purpose of the "8 8 0 0" is to tell which set of f1 commands (651, 652, 751, 752) gets mapped to which RXP GTN (any GTN #1, any GTN #2).

Please find below the paragraph explaining this (from the 'readme' included with the xml gauge file)

 

6) Configure the f1vc.xml gauge for the combination of GTN devices in the VC.

   a) open f1vc.xml with notepad.exe.
   b) edit the 4 space separated numbers at line 17 if needed.
    These 4 numbers configure how to connect the virtual cockpit GTN model (type+unit) to the RXP GTN unit number. They are set in a specific order, respectivelly to the following 3D models: 652, 651, 752, 751.
   
    Use 0 to map the corresponding device to the RXP GTN #1, use 8 to map to the RXP GTN #2. It reads like this:
           
    code = 8080
    3D model   |  652  |  651  |  752  |  751  |
    map to RXP |   8   |   0   |   8   |   0   |
               |(unit2)|(unit1)|(unit2)|(unit1)|

    Other Examples:
    
    3D panel using 651 and 652: 8 0 8 0
    3D panel using 751 and 752: 8 0 8 0
    3D panel using 751 and 651: 8 8 0 0
            

Here is the full readme:

Reality XP GTN Buttons Bridge Gauge

Bridges Reality XP GTN 750/650 Touch with f1 3D bezel
Credits: Sean Moloney and Ryan Butterworth

Installation:
=============

1) Extract the .zip archive into the aircraft panel folder. The following files are expected:

SimObjects\Airplans\[Aircraft Name]\
 panel\
 |__ rxpGTN\
 |   |__ f1vc.xml
 |
 |__ panel.cfg
 |__ readme (rxpGTN_f1vc).txt

 
2) Replace any F1 gauge with the Reality XP GTN 750/650 Touch gauges.
 
3) Open the panel.cfg with notepad.exe or any other text editor.
 
4) Find the first VCockpit window which has a rxpGTN gauge.
 
5) Add the Reality XP GTN Buttons Bridge gauge (rxpGTN!f1vc) to the next line, typically:
 
    [Vcockpit01]
    Background_color=0,0,0
    size_mm=1024,1024
    visible=1
    pixel_size=1024,1024
    texture=$Panel_1

    gauge00=rxpGTN!GTN_750_1,0,0,667,794,NO_BEZEL
    gauge01=rxpGTN!f1vc,0,0,1,1

6) Configure the f1vc.xml gauge for the combination of GTN devices in the VC.

   a) open f1vc.xml with notepad.exe.

   b) edit the 4 space separated numbers at line 17 if needed.

    These 4 numbers configure how to connect the virtual cockpit GTN model (type+unit) to the RXP GTN unit number.
    They are set in a specific order, respectivelly to the following 3D models: 652, 651, 752, 751.
   
    Use 0 to map the corresponding device to the RXP GTN #1, use 8 to map to the RXP GTN #2. It reads like this:
           
    code = 8080
    3D model   |  652  |  651  |  752  |  751  |
    map to RXP |   8   |   0   |   8   |   0   |
               |(unit2)|(unit1)|(unit2)|(unit1)|

    Other Examples:
    
    3D panel using 651 and 652: 8 0 8 0
    3D panel using 751 and 752: 8 0 8 0
    3D panel using 751 and 651: 8 8 0 0
    
7) Example with the MilViz DHC3:

this aircraft panel.cfg virtual cockpit sections are:
    
    [Vcockpit20]
    ...
    gauge00=F1GTN!GTN750VC,  0,0,677,794,UNIT1
    
    [Vcockpit21]
    ...
    gauge00=F1GTN!GTN650VC,  0,0,677,297,UNIT1    

The virtual cockpit uses the 751 and the 651 (type+unit). Therefore, the code must tell to map the 751 to RXP unit1,
and the 651 to RXP unit2. Using the colum view above, this gives:
    
    code = 8800
    3D model   |  652  |  651  |  752  |  751  |
    map to RXP |   8   |   8   |   0   |   0   |
               |(unit2)|(unit2)|(unit1)|(unit1)|

               
Change the panel.cfg virtual cockpit sections to:
 
    [Vcockpit20]
    ...
    gauge00=rxpGTN!GTN_750_1,  0,0,677,794,NO_BEZEL
    gauge01=rxpGTN!f1vc,0,0,1,1

    [Vcockpit21]
    ...
    gauge00=rxpGTN!GTN_650_2,  0,0,677,297,NO_BEZEL

    
Change f1vc.xml line 17 to:

            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 0 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->
      8 8 0 0

 

Edited by RXP

Share this post


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

Please find below the paragraph explaining this (from the 'readme' included with the xml gauge file) 

Ha! Jean-Luc. I am all on top of that. I thought so anyway. No combination is working with the Comanche. I have tried both of those  "8 0 8 0", or "8 8 8 0".  Just tried both again, neither work.  Should be simple.  Its just identifying the units in question, then its pretty binary, either an 8 or a 0. 

Switch gears from the Comanche.  Lets look at the case of the Milviz C310 Redux.  I am attempting to map:

RXP GTN 750_1
and-----
RXP GTN 650_2

With   "8   0   8  0"   I have the knobs and buttons on the 750 working fine. But cannot get them working on the 650. I have tried all combinations possible.

For what it is worth, I inserted the F1 GTN gauges by hand editing in the RXP GTN's instead.  My F1 GTN gauges are rem'd out (see Vcockpit sections below). So how then can the "f1vc.xml"  gauge replace an F1 751 or an F1 651 if neither of those two F1's are called or are seen?

I clearly have the RXP 750_1 knobs and keys working.

Here are my pertinent [Vcockpit##] sections for the Comanche.

//--------------------------------------------------------
[Vcockpit19]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$GTN750

//gauge00=F1GTN!GTN750VC,  0,0,677,794,UNIT1
gauge00=rxpGTN!GTN_750_1,  0,0,677,794,POP_NO_BEZEL
gauge01=rxpGTN!f1vc.xml,1,0,0,1

//--------------------------------------------------------
[Vcockpit20]
Background_color=0,0,0
size_mm=1024,512
visible=1
pixel_size=1024,512
texture=$GTN650
//gauge00=F1GTN!GTN650VC,  0,0,677,297,UNIT1

gauge00=rxpGTN!GTN_650_2, 0, 0,677,297,POP6_NO_BEZEL
gauge01=rxpGTN!f1vc.xml,0,0,0,1

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

Share this post


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

So how then can the "f1vc.xml"  gauge replace an F1 751 or an F1 651 if neither of those two F1's are called or are seen?

This is because what we're talking about is HARD-CODED commands in the 3D model. The aircraft vendor hard-code each of these possible device specific commands to a button or a knob.

 

You need to first find out what commands are hard-coded in the 3D model:

The best hint is to look at the panel VC by default. In your case:

//gauge00=F1GTN!GTN750VC,  0,0,677,794,UNIT1
//gauge00=F1GTN!GTN650VC,  0,0,677,297,UNIT1

So you know the 3D model uses the commands for 750#1 and for 650#1

Then, you need to tell the XML gauge to "re-route" these commands to the equivalent RXP GTN:

    3D model   |  652  |  651  |  752  |  751  |
    map to RXP |   x   |   8   |   x   |   0   |
               |(unit2)|(unit2)|(unit2)|(unit1)|

Using 8800 should work then with rxpGTN!GTN_750_1 and rxpGTN!GTN_650_2.

NB: you are trying 8880 which is wrong. Use only 2x 8 and 2x 0 in the code.

In the end, you'll find out there is only 2 codes to cover all combinations: either 8800 or 8080.

 

You may want to try reversing gauge order and make sure FltSim updates the gauge:

1) Make sure the 'bridge' get updated before any GTN in making it the the last gauge entry in the first VC section:

[Vcockpit01]
gaugeXX=rxpGTN!f1vc.xml,0,0,1,1

NB: I'm using x = 0, y = 0, w = 1, and h = 1 to make sure it is drawable, hence, FltSim will update this gauge. You are using w = 0 which probably makes FltSim skip updating it, hence the 'double click' issue.

2) Put the GTN after the f1vc.xml entry. Either the RXP GTN gauge appears in Vcockpit01, then it will be gaugeXX+1, gaugeXX+2 etc..., otherwise, it is in any other subsequent Vcockpit## section.

 

Edited by RXP
  • Like 1
  • Upvote 1

Share this post


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

gauge00=rxpGTN!GTN_650_2, 0, 0,677,297,POP6_NO_BEZEL

6? Does this match your RealityXP.GTN.ini ?

Anyway, for the Milviz 310 I have the 650, 750 working. Knobs and buttons. Double clicking still.
Dual GTN 650_2, 750_1 setup. Code 8800 in the f1vc.xml file.

Panel.cfg

Spoiler

// GTN750_650

[Window Titles]
Window00=Main Panel
Window01=Throttle
Window02=C310 Prelight
Window03=Reality XP GTN 650
Window04=Reality XP GTN 750

[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL
VIEW_FORWARD_DIR=10.000, 0.000, 0.000

//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=1680,1050
window_size_ratio=1.000  
position=7
visible=1
ident=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=296,547
window_size_ratio=1.000  
position=8
visible=0
ident=10030
window_size= 0.176, 0.514
window_pos= 0.834, 0.486
zorder=2

gauge00=C310_XMLGauges!C310_ThrottleQuad,  0,0,286,547

//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=500,243
window_size_ratio=1.000  
position=0
visible=0
ident=70
window_size= 0.400, 0.324
window_pos= 0.000, 0.040

gauge00=C310_XMLGauges!C310_Preflight,  0,0,500,243

//--------------------------------------------------------
[Window03]
size_mm=100,100
window_pos=0.000000,0.830590
window_size=0.216146,0.169410
visible=0
zorder=99
background_color=0,0,0
ident=14403

gauge00=rxpGTN!GTN_650_2, 0, 0,100,100

//--------------------------------------------------------
[Window04]
size_mm=100,100
window_pos=0.000000,0.450000
window_size=0.216146,0.382381
visible=0
zorder=99
background_color=0,0,0
ident=14401

gauge00=rxpGTN!GTN_750_1, 0, 0,100,100

//--------------------------------------------------------
[Vcockpit01]
file=C310_VC_01.bmp 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01

gauge00=MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\MV_C310R\\panel\\C310R_Sounds#25
gauge01=C310_XMLGauges!KR 87 ADF,  0,715,640,134
gauge02=C310_XMLGauges!C310_DME,  649,32,300,150
gauge03=MilVizC310!EDM700_L,  663,200,339,339
gauge04=MilVizC310!EDM700_R,  662,547,339,339
gauge05=C310_XMLGauges!C310_Logic,  693,11,1,1
gauge06=KAP140_HSI!MV_KAP140Servos,  0,0,1,1
gauge07=KAP140_HSI!MV_KAP140Display,  0,852,640,163
gauge08=Console!console_GTN750_650,  0,0,1,1
gauge09=TrueGlass!Core,0,0,1,1
gauge10=RealLight!Core,0,0,1,1
gauge11=AMSInterop!AMSInterop,0,0,1,1

//--------------------------------------------------------
[Vcockpit02]
file=C310_VC_02.bmp 
size_mm=512,512
visible=0
pixel_size=1024,512
texture=$C310_VC_02

gauge00=C310_XMLGauges!FBS_GTX330,  0,0,512,135

//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_1

texture00=RL_0, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_2

texture00=RL_1, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_3

texture00=RL_2, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_4

texture00=RL_3, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_5

texture00=RL_4, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_6

texture00=RL_5, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit09]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_7

texture00=RL_6, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit10]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_8

texture00=RL_7, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit11]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_9

texture00=RL_8, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit12]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_10

texture00=RL_9, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit13]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_11

texture00=RL_10, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit14]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_12

texture00=RL_11, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit15]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_13

texture00=RL_12, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit16]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_14

texture00=RL_13, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit17]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_15

texture00=RL_14, 0,0,1024,1024

//--------------------------------------------------------
[Vcockpit18]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$GTN750

gauge00=rxpGTN!GTN_750_1, 0, 0,677,794,NO_BEZEL
gauge01=rxpGTN!f1vc,0,0,1,1

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

gauge00=rxpGTN!GTN_650_2, 0, 0,677,297,NO_BEZEL

//--------------------------------------------------------
[Vcockpit20]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_0

texture00=TG_0, 0,0,2048,2048

//--------------------------------------------------------
[Vcockpit21]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_1

texture00=TG_1, 0,0,2048,2048


Day=255,255,255
Night=85,85,85
Luminous=140,140,140

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

 

Edited by BillS511

Share this post


Link to post
Share on other sites
11 minutes ago, BillS511 said:

[Vcockpit18]
...
gauge01=rxpGTN!f1vc,0,0,1,1

Following my advise above, this could be moved to:

[Vcockpit01]
...
gauge12=rxpGTN!f1vc,0,0,1,1

I'm certain this will work at least, eventually solve the 'double click' issue.

Mind you: the f1 system is prone to errors. It consists in relying to a variable which is set to a value, then,  it must poll this value to execute the action. Should your quickly turn the knob twice in an update cycle (which is 18hz in FltSim), the variable will be written multiple times. When comes the time for the GTN to read the variable, it will get the last written value only. Thus, if you manage to turn a knob then press it before the f1 GTN gets the chance to read the variable, only the 'press' action will work....

The Reality XP commands are event based, in other words they are fail proof. This means should you turn the knob 3 times then press it, then release it and even touch the screen at the same time, between 2 gauge update cycles, the RXP GTN receives all the  events (none are lost).... Worth the price difference isn't it?

Edited by RXP

Share this post


Link to post
Share on other sites

Bills511 and Jen-Luc,
Thanks for all the assistance.  Something else is amiss here.  First I compared Bills511 panel.cfg file line by line through the entire VC sections.  The most major difference is that I have the Milviz weather gauge installed.  So first I just copied and based his panel.cfg file into a fresh notepad screen, named it appropriately instead, and tried it.  No soap.  Still no keys or knob action from the 650 in the vc.

Next I unzipped a fresh f1vc.xml file from the download.  Looked at it and it was coded as 8  8  0  0.  So I replaced my file with the fresh .xml file.  Still no success.  The .xml file is working for the 750, clearly, because if I rem it out in panel.cfg I get no knob or key action on even the 750.  Restore the line and knob-key action comes back to the 750.

Then it hit me like a flash of lightening. One comment from Jean-Luc.

Quote

The aircraft vendor hard-code each of these possible device specific commands to a button or a knob.

You need to first find out what commands are hard-coded in the 3D model:

The best hint is to look at the panel VC by default. In your case:

//gauge00=F1GTN!GTN750VC,  0,0,677,794,UNIT1
//gauge00=F1GTN!GTN650VC,  0,0,677,297,UNIT1 

This aircraft never had an F1 GTN 650 installed. I never owned the F1 650.  I added the RXP 650 in with hand edits to the panel.cfg file.  So that may be the cause.  So what is the cure?

 

Edited by fppilot

Share this post


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

This aircraft never had an F1 GTN 650 installed.  So that may be the cause.  So what is the cure? 

Then I don't know what we are talking about LOL!

Let's get back to the basics: what it is you are starting from?

Is this a pre-configured aircraft VC with a 750 and a 650, and you are trying to swap these with the RXP GTN instead?

If pre-configured for both these models, I'd assume it also come with both these models bezels in 3D isn't it?

If yes to this last question, the aircraft certainly has a 650 model hard-coded isn't it?

Share this post


Link to post
Share on other sites
1 minute ago, RXP said:

Then I don't know what we are talking about LOL!

Let's get back to the basics: what it is you are starting from?

Is this a pre-configured aircraft VC with a 750 and a 650, and you are trying to swap these with the RXP GTN instead?

If pre-configured for both these models, I'd assume it also come with both these models bezels in 3D isn't it?

If yes to this last question, the aircraft certainly has a 650 model hard-coded isn't it?

I was editing my post as you wrote yours.  This stuff is above me.  Hard coding an add on product into an aircraft?  I am not sure what you mean by that.  The F1 GTNs were a separately purchased product and I only owned the F1 750.  Are you saying Milviz had a 650 hard coded in?  I thought all Milviz was supplying was the appropriate panel bezels.

Share this post


Link to post
Share on other sites

When you have a VC pre-configured, this implies it usually has a 3D bezel and 3D knobs and 3D buttons.

To make these buttons work, they embed hard-coded XML gauge code to execute some functions (in our case, they write a named variable for the f1 gtn to poll). The gauge## in the VC is unrelated. It just tells the panel system where-to draw a gauge, but the actual 3D buttons commands are code embedded in the 3D model.

So to sum up:

1) no 3D bezel, display a gauge as a flat rectangle with mouse rects: just add any gauge to the VCcocpit## sections and you're done.

2) 3D bezel and knobs: a gauge is the logic/display, the commands are not via mouse rects (gauge) but via 3D model code (XML). This means you have to configure the aircraft.cfg to use the model with has the 3D bezel and knobs and the code which is embedded in it.

 

So my question above: you are trying to add a 650 #2, but do you actually have the 650 #2 showing up as a 3D bezel in the VC? (meaning you've selected a 750+650 pre-configured option and the 'tool' included with the aircraft has done the necessary file update process so that your aircraft.cfg, your .mdl and your panel are pre-set and you just need to swap gauges and add the f1vc.xml gauge?

 

 

Share this post


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

Following my advise above, this could be moved to:

[Vcockpit01]
...
gauge12=rxpGTN!f1vc,0,0,1,1

Unfortunately this didn't work. Still have to double click.

Share this post


Link to post
Share on other sites

@fppilot
Are you using the following?
; uses Simulator GPS commands if true.
UseSimGpsCmds = true

It may be on for your 750 but off for the 650.

If I turned it off buttons didn't work. Turned on they worked.

Edited by BillS511
  • Like 1
  • Upvote 1

Share this post


Link to post
Share on other sites
5 minutes ago, BillS511 said:

@fppilot
Are you using the following?
; uses Simulator GPS commands if true.
UseSimGpsCmds = true

It may be on for your 750 but off for the 650.

If I turned it off buttons didn't work. Turned on they worked.

BINGO!   That solved it!  Oh my lord!  Sorry for the time consumed with this.  I'd have never thought something like that was at play!  This one will be remembered, certainly!  Where's my bottle of Scotch!

Edited by fppilot
  • Upvote 1

Share this post


Link to post
Share on other sites
1 minute ago, fppilot said:

BINGO!   That solved it!  Oh my lord!  Sorry for the time consumed with this.  I'd have never thought something like that was at play!  This one will be remembered, certainly!  Where's my bottle of Scotch!

Awesome!
Do you have to double click thou?

Share this post


Link to post
Share on other sites
4 minutes ago, BillS511 said:

Do you have to double click thou?

Yes, on the Home key. And to verify, as Jean-Luc suggested I moved the call to f1vc.xml into an elevated position as the last gauge in [Vcockpit01] and I incremented the gauge number correctly when doing so.  Just fixed the Comanche as well and same there. Double click.

BillS511, so now that I can use the knobs to tune freqs, is there a method with the knobs to xfer a frequency from standby to active?

Thanks so much for helping me hunt this down!

Share this post


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

is there a method with the knobs to xfer a frequency from standby to active?

Not sure. I touch the frequencies on the screen.

Share this post


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

Not sure. I touch the frequencies on the screen.

I'm just laughing at myself over the time spent. The challenge of getting the .xml to work. Then  it wasn't the .xml.  It was a setting.  Then I can now use the tuning knobs...... (drumroll....) and I still have to use the touchscreen to xfer the frequency!  Is that right? If so then who at Garmin thought that up? LOL!

Share this post


Link to post
Share on other sites

If I want to map a single  RXP GTN750_2

Use 0 to map the corresponding device to the RXP GTN #1, use 8 to map to the RXP GTN #2. 

So what do I identify in the table as where I put my finger to represent RXP GTN 750_1?  Is it the top line?  Or is it the bottom line in the table?  Actually, it is neither. Both lines appear to be maybes.  But neither one is. 

Here is an example.  In my A2A 182 Skylane I am using a single gauge and it is rxpGTN_750_2.  So I need an "8" somewhere in that code.  Do I put it in the fourth position (0  0  0  8)? No. To me, a non-programmer, that position appears to be for an rxpGTN_750_1.  That because that position is labeled 751 on the top, and (unit1) on the bottom.  So anything with 2 doesn't seem to fit.
 
3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               |(unit2)|(unit1)|(unit2)|(unit1)|

So here is what has had me so confused about this f1vc.xml gauge and how to code line 17.  As a consumer/user and not an .xml programmer, what got in my way  is my understanding of the RXP GPS license agreement.  Say what, you say?  Let me explain. 

With purchase of RXP GTN750 software I got two (2) instruments.  #1 being 750_1; and #2 being a 750_2. Key point here is that either of those two instances can be used as a primary gauge in a panel with two, or either can be used as a sole gauge in a single gauge panel.  Looking at the table I was seeing (unit1) as the first of my two gauges, or the primary, and (unit2) being a second gauge in a panel, or the secondary.  With that way of thinking, either 750_1 or 750_2 could be (unit1) or the primary.  But the top line (752 and 751) did not match that thinking.

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               | 650_1=0 |650_1=0 | 750_1=0 | 750_1=0 |
               | 650_2=8 |650_2=8 | 750_2=8 | 750_2=8 |

Are these correct examples?:
(1) rxpGTN_750_2 in the panel =  0   0   0   8

(1) rxpGTN_750_1 in the panel =  0   0   0   0

(2) rxpGTN_750's in the panel, 750_1 and 750_2  =  0   0   8   0  -or-  0  0  0  8    ???

(1) rxpGTN_750_1 and one rxpGTN_650_2 in the panel = 8  0  0  0

Edited by fppilot

Share this post


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

I'm just laughing at myself over the time spent. The challenge of getting the .xml to work. Then  it wasn't the .xml.  It was a setting.  Then I can now use the tuning knobs...... (drumroll....) and I still have to use the touchscreen to xfer the frequency!  Is that right? If so then who at Garmin thought that up? LOL!

I'm looking at the Garmin 750 trainer and there is a push button (lower right small knob). It switches between the com frequency and the Nav frequency.

However in the sim the VC small knob doesn't appear to have the push function just turning. The popup small knob has the push function.

 

41 minutes ago, fppilot said:

Are these correct examples?:
(1) rxpGTN_750_2 in the panel =  0   0   0   8

(1) rxpGTN_750_1 in the panel =  0   0   0   0

(2) rxpGTN_750's in the panel, 750_1 and 750_2  =  0   0   8   0  -or-  0  0  0  8    ???

(1) rxpGTN_750_1 and one rxpGTN_650_2 in the panel = 8  0  0  0

As I understand it Jean-Luc states there can only 2 - 8's and 2 - 0's. So the above would not work.

5 hours ago, RXP said:

Use only 2x 8 and 2x 0 in the code.

In the end, you'll find out there is only 2 codes to cover all combinations: either 8800 or 8080.

 

Edited by BillS511

Share this post


Link to post
Share on other sites
41 minutes ago, BillS511 said:

As I understand it Jean-Luc states there can only 2 - 8's and 2 - 0's. So the above would not work.

I checked some first before posting.  I am checking more scenarios out now.

0  0  0  0   is what works for a single GTN750_1 in the A2A Skylane 182 and the A2A Comanche
0  0  0  8   is what works for a single GTN750_2 in the same two aircraft

0  0  8  0   is working perfectly in my Turbine Duke v2 with rxpGTN_750_1 as primary and rxpGTN_750_2 as secondary, and  8  8  8  0  works as well. 
0  0  0  8   is working perfectly in the TDV2 with xpGTN_750_2 as primary and rxpGTN_750_1 as secondary, and  8  8  0  8  works as well.

0  8  0  0  is what works in my Milviz Cessna 310R Redux  for a 750_1 as primary and 650_2 as secondary, all in line with the table. I just needed to see it like this to understand it. 

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               | 650_1=0 |650_1=0 | 750_1=0 | 750_1=0 |
               | 650_2=8 |650_2=8 | 750_2=8 | 750_2=8 |

Edited by fppilot

Share this post


Link to post
Share on other sites

The table mod below makes it even clearer for me. There are only so many combinations. 

(1) 650 is one.  (2) 650s is another. When you have (2) 650s either one can be primary or secondary.  ex. I can have 650_2 as my primary and 650_1 as my secondary, or of course the other way around.  The same if you have an airplane where you can use (2) 750s.  In fact I just confirmed that with my Turbine Duke v2.  I swapped 750_1 and 750_2 back and forth as primary and secondary.  And I had to adjust the f1vc.xml file by changing from
0   0   8  0  -to-  0  0  0  8.

You can also have combinations of 750s and 650s if you own both and can fit them into an aircraft.  And if you do have one of each, one will be _1 and the other will then need to be _2.  My understanding is that you cannot use two _1s, or for that matter two _2s , even if one was a 750 and the other was a 650. 

The f1vc.xml must reflect what you are doing. So my example of   0  8  0  0 for my Milviz Cessna 310R Redux for a 750_1 as primary and a 650_2 as secondary, would need to change  if I instead decided to use 750_2 as my primary, and 650_1 as secondary.  It would change -to-  0   0   8  0

               |         | Only or |          | Only or |
     3D model  |  650 as |   1st   |  750 as  |   1st   |
               | 2nd GPS |   650   | 2nd GPS  |   750   |
    map to RXP |    #    |    #    |    #     |    #    |

                  |  650_1=0  |  650_1=0   |   750_1=0   |  750_1=0   |
    
   Value      |  650_2=8  |  650_2=8   |   750_2=8   |  750_2=8   |

 

Edited by fppilot

Share this post


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

The purpose of the "8 8 0 0" is to tell which set of f1 commands (651, 652, 751, 752) gets mapped to which RXP GTN (any GTN #1, any GTN #2).

11 hours ago, fppilot said:

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               |(unit#)|(unit#)|(unit#)|(unit#)|

Let's recap:

  • First row (3D model) is the 3D model used in the panel. It could be any of the 4 (these are 3D model embedding f1 gtn commands which are per-device-unit, thus, there are 4 sets of commands). You identify this in looking up which f1 gauges were configured in he panel.cfg
  • Middle row is the code telling how to remap from f1 3D model to RXP GTN #.
  • Last row (unit #) is the RXP GTN unit # which will receive the command. It could be any of the 2 (these are per-unit). You identify this in determining which RXP gauges you've added.

Examples:

8000 tells to remap any f1 gtn 651 command into any RXP GTN #1 (what matters: it is a #1 RXP GTN, whether a 750 or 650).
8000 tells to remap any f1 gtn 652 command into any RXP GTN #2 (what matters: it is a #2 RXP GTN, whether a 750 or 650).
0800 tells to remap any f1 gtn 651 command into any RXP GTN #2 likewise.
0800 tells to remap any f1 gtn 652 command into any RXP GTN #1 likewise.
0080 tells to remap any f1 gtn 752 command into any RXP GTN #2 likewise.

etc...

Of course, this requires enabling "Use Simulator GPS Commands" because this enables external commands to the RXP GTN (there are also keyboard shortcuts, but they are 'external' to the simulator, whereas 'commands' are internal, i.e. can be fired by any gauge / module / 3D model).

Edited by RXP

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