That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN.  When the AC was made they only incorporated the the F1 Version and since the 3D Model has the F1 Bezel built into the 3D model you can't replace the Bezel. 

If you don't care about using the Buttons and Knobs in the VC for the 750 and you only use the Pop Out Panels then you do not need it.

28 minutes ago, LesOReilly said:

That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN.  When the AC was made they only incorporated the the F1 Version and since the 3D Model has the F1 Bezel built into the 3D model you can't replace the Bezel. 

If you don't care about using the Buttons and Knobs in the VC for the 750 and you only use the Pop Out Panels then you do not need it.

Les, I do care about using the Buttons and Knobs in the VC for the 750!! Actually that is all I care about delving in here.

You says: "That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN"  -

Why not specify what exactly "That" is? That actually leaves me guessing only what you meant by "That". Not that I don't have my guesses, but could you make it a little less guessing-necessary.

Thank you.

 

Edited July 26, 20205 yr by Dirk98

On 2/7/2020 at 8:58 PM, Bert Pieke said:

For the Legacy, I simply use this routine:

<Gauge Name="GTN 750 buttons" Version="1.0">

<!-- Trigger GTN 750 commands -->
   
<Element>
     <Select>
      <Value>

  (L:F1GTNMOUSE, number)  129539 ==  if{
  1 (>K:GPS_DIRECTTO_BUTTON)
  0 (>L:F1GTNMOUSE, number) }

 (L:F1GTNMOUSE, number)  129537 ==  if{
  1 (>K:GPS_MENU_BUTTON)
  0 (>L:F1GTNMOUSE, number) }
          
      </Value>      
     </Select>
   </Element>
</Gauge>

 

Where, Bert? Which file?

Thank you.

21 minutes ago, Dirk98 said:

Where, Bert? Which file?

Thank you.

Suggest adding an F1VC gauge to the panel, as explained above.. that should work for most airplanes.

@Dirk98 Can you please refrain from posting on several different discussions when there is one already created just for your initial question? Thank you.

@Dirk98 It seems complex at first but it is not. It boils down simply to these few steps:

1. Replace gauges in the panel with RXP gauges using GUI Panel Assistant.
   
   with pictures of the assistant:
   
   https://www.avsim.com/forums/topic/525126-configuring-panel-step-by-step-on-the-carenado-cheyenne-iii/?tab=comments#comment-3748068
    
2. Create a file named f1vc.xml which content you'd copy/paste from the aforementioned forums into notepad.exe
   
   with step-by-step instructions:
   
   https://www.avsim.com/forums/topic/570294-f1vcxml-3d-cockpit-knobs-and-keys-tips-and-tricks/page/5/?tab=comments#comment-4256700
    
3. Copy this file f1vc.xml you've just saved to your drive into a folder you'd name rxpGTN in the simulator Gauges folder.

I'd suggest the following:

1. Try these first without trying to understand it all. Just do it as it is explained.
2. enjoy.

Edited July 27, 20205 yr by RXP

You Wrote the Following:

2 hours ago, Dirk98 said:

What is exactly F1VC gauge? Is it just f1vc.xml file?

Thanks.

 

Immediately after "that" post I replied to the thread with the following....

2 hours ago, LesOReilly said:

That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN.  When the AC was made they only incorporated the the F1 Version and since the 3D Model has the F1 Bezel built into the 3D model you can't replace the Bezel. 

If you don't care about using the Buttons and Knobs in the VC for the 750 and you only use the Pop Out Panels then you do not need it.

You Then wrote this as a reply:

2 hours ago, Dirk98 said:

Les, I do care about using the Buttons and Knobs in the VC for the 750!! Actually that is all I care about delving in here.

You says: "That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN"  -

Why not specify what exactly "That" is? That actually leaves me guessing only what you meant by "That". Not that I don't have my guesses, but could you make it a little less guessing-necessary.

Thank you.

 

There is nothing unclear about what "That" is......Nothing......You are the only one asking questions in this thread.  So we are only replying to your question.....

What is exactly F1VC gauge? ----->>> That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN.

In Flight Sim gauges are written in XML.  Now they can also be built up into CAB files and if you unpack them then you can edit them and then re-pack them.

Did you at least download the file from the Link  -- from the video that shows you how to do it as well?

 

1 hour ago, LesOReilly said:

There is nothing unclear about what "That" is......Nothing.....

Let's not let this &^%%$$#%%^ pandemic get to us, ok? This is a member here with almost four thousand posts and a significant number of :"liked" posts.  I am not a programmer. Not any more.  Back in the early days of IBM PC's I learned to write in computer Basic language by adapting TRS-80 Basic programs to the somewhat different IBM PC Basic, primarily to create a line editor type word processor because after spending $3,000 at the time, 1981, I did not have $695 to spend for Easywriter, the only word processor first available.  Later I learned to write structured databases in dBase2 database , and learned to make customized mods to the Wordstar word processing program with hex edits.  Later I got sophisticated with structuring databases and reports in Microsoft Access, including a large database for a virtual airline.  I have not attempted anything like that since perhaps 1997.  Over 20 years ago.

.xml bewilders me.  I understand that our simulators make heavy use of .xml code.  And I have used some modifications, mostly from Bert, to mostly Carenado aircraft models to overcome instances where Carenado's coding of their default GPS gauges blocked or hindered best use of RXP gauges.  Two examples are the small .xml files that Bert provided to overcome Carenado's 3D knobs interference with RXP knobs for GNS models, and Bert's small .xml file that overcomes the way that the instrument reflections in some Carenado models block out the mouse cursor action for RXP gauges, but not for their own default gauges, or why they were implemented as "gauges".  

In both instances I just followed Bert's instructions to position his .xml file in a subfolder to the aircraft's panel folder, and to then add a reference to that subfolder and file in the aircraft's panel.cfg file as an added gauge.  I only understood to follow his instructions.  I did not understand, or even attempt to understand the structure of his respective .xml files or why they were referenced as gauges.

f1vc.xml in this case is different. It requires configuring one line in the f1vc.xml to specify just which instance(s) of RXP gauges are desired in the aircraft's panel.  To accomplish that requires more understanding.  Please allow time for another user to absorb all of it.  Better to move one step at a time instead of all at once.

I first attempted to address f1vc.xml instructions with a text editor, based on what I read about the four separated numbers in that one line.  Did not work.  Found out I really needed to download and use an .XML file editor.  Then I was attempting to configure a pair of RXP GTN gauges in an aircraft, and following very clear instructions on what to change in those four characters, in one simple line, in the .xml file. What was provided not only did not work, but totally confounded me.  I spent the better part of two very frustrating days trying "what-if's" with those four characters or variables before I discovered an unmentioned combination that finally worked. That was for an RXP GTN 750_1 as a primary GTN, and a RXP GTN 650_2 as the secondary gauge in the Milviz Cessna Redux 310.

Please do not assume that every fellow user here shares the same knowledge or experience of .xml. Or understands that an .xml file is referenced in a panel.cfg file as a gauge.  To those of us not savy on that it can be quite confusing at first, and confusing in some instances even later.

Edited July 27, 20205 yr by fppilot

13 hours ago, LesOReilly said:

You Wrote the Following:

 

Immediately after "that" post I replied to the thread with the following....

You Then wrote this as a reply:

There is nothing unclear about what "That" is......Nothing......You are the only one asking questions in this thread.  So we are only replying to your question.....

What is exactly F1VC gauge? ----->>> That is an "invisible" gauge...think controller...That will translate the F1 GTN 750 Click Spots to send commands to the RXP GTN.

In Flight Sim gauges are written in XML.  Now they can also be built up into CAB files and if you unpack them then you can edit them and then re-pack them.

Did you at least download the file from the Link  -- from the video that shows you how to do it as well?

 

Les, you could have quoted a part of my post you referred to, but you know better what to do anyway, it's me who is learning here. Yes, I did download that file and finally have managed to successfully retrofit FSW LearJet35A with it. Now it's time to delve into some mdl edits trying to eliminate double-clickers.

Much obliged to everybody who posted in this "Trying to configuring"  thread ))

Cheers, 

On 2/7/2020 at 10:38 AM, Bert Pieke said:

I have found that some airplanes converted from F1 to RXP GTN have a problem with recognizing the Direct-To and Home buttons when clicked, even when one of the nifty translation programs for the buttons/knobs is used.  A double-click often works, but a single click does not.

After trying various things, I have now gone to the Interior Model files and trough trial and error found that making some simple edits fixes the situation.

The standard code for the Direct-To button looks like this:

Direct-To Key       

(M:Event) 'LeftSingle'  scmp 0 == if{ 0x0001FA03 (>L:F1GTNMOUSE, bool) ....

(M:Event) 'LeftRelease'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...       

(M:Event) 'Leave'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...      

(M:Event) 'LeftDrag'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...   

If you rename the last three F1GTNs to F2GTN.. then the single click works like a charm

I am sure that FXGTN would work just as well..

Same for the Home key!

 

Bert, do I get it right by "last three" you mean to edit these :

(M:Event) 'LeftRelease'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...       

(M:Event) 'Leave'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...      

(M:Event) 'LeftDrag'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ... 

And leave alone this one:

(M:Event) 'LeftSingle'  scmp 0 == if{ 0x0001FA03 (>L:F1GTNMOUSE, bool) ....

Thanks.

Edited July 27, 20205 yr by Dirk98

15 minutes ago, Dirk98 said:

Bert, do I get it right by "last three" you mean to edit these :

(M:Event) 'LeftRelease'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...       

(M:Event) 'Leave'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ...      

(M:Event) 'LeftDrag'  scmp 0 == if{ 0x0001FA04 (>L:F1GTNMOUSE, bool) ... 

And leave alone this one:

(M:Event) 'LeftSingle'  scmp 0 == if{ 0x0001FA03 (>L:F1GTNMOUSE, bool) ....

Thanks.

The "Drag" command is the problem as best as I can tell, start by just editing it.

The "Leave" command I do not really know.. up to you..

The "Release" command can be left alone...

1 hour ago, Bert Pieke said:

The "Drag" command is the problem as best as I can tell, start by just editing it.

The "Leave" command I do not really know.. up to you..

The "Release" command can be left alone...

Do you remember which plane you were working on with the above?

I'm going through Learjet_35A_interior.MDL, unfortunately, "LeftDrag" is in no instance associated with F1GTNMOUSE.

PS: I've found 'LefDrag' it had some symbols inside that did not allow to search it. 

Edited July 27, 20205 yr by Dirk98

58 minutes ago, Dirk98 said:

Do you remember which plane you were working on with the above?

I'm going through Learjet_35A_interior.MDL, unfortunately, "LeftDrag" is in no instance associated with F1GTNMOUSE.

PS: I've found 'LefDrag' it had some symbols inside that did not allow to search it. 

If you have the RXP unit selected in the Lear, FSW has provided RXP support, and you would not find F1GTN in the model..

However, I do find:

(M:Event) 'LeftDrag'    sc........mp 0 == if{ 4 (>K:GPS_MENU_BUTTON)  ........ 0 (>L:RXP_GTN_HME_BUTN_1, number) }.

and similar..

One easy way of fixing this, is to change "0 ==" to some other number, like "7 =="

So, if the buttons in the Lear only work with double click and not single click, you should be able to fix them this way..

Edit:

I also find:

(M:Event) 'LeftD........rag'  scmp 0 == if{ 0x0001FA58 (>L:F........1GTNMOUSE, bool)........0 (>L:F1GTN6........50U2_DTOKEY, number) }.. 

so there may be F1GTN code regardless..

Lastly, there may be GTN650 and GTN750 sections.. so be patient..

It all depends on what problem you are trying to solve.. 🙂

Edited July 27, 20205 yr by Bert Pieke

2 minutes ago, Bert Pieke said:

If you have the RXP unit selected in the Lear, FSW has provided RXP support, and you would not find F1GTN in the model..

I'm embarrased now. I installed LearJet yesterday, configured x2F1GTNs (don't ask me why!) with its configurator, then replaced those by 2xRXP GTN750 manually via Add-Ons\Reality XP GTN menu and so on following all the kind suggestions found here.. The funny part it all worked, until I opened the mdl file and saw your post...

Anyway reinstalled Lear, configured 2xGTNRXP properly and all buttons work just in one click! So this is my story about how I fixed Lear (but can't fix stupid! lol).

However I've learnt a lot, time to take on Legacy 2 and A2A's C182.

Thank you.

 

2 hours ago, Dirk98 said:

Anyway reinstalled Lear, configured 2xGTNRXP properly and all buttons work just in one click! So this is my story about how I fixed Lear (but can't fix stupid! lol).

 

We have all done things like that.....  Please don't ask me how many times...