Where can I find a list of the L:vars mentioned in this cryptic entry in the RealityXP.GNS.ini file:

; use legacy GNS WAAS 3rd party aircraft panel variables (L:Vars).
UseLegacyVars = false

I'm needing to set up the modeldef.xml file so that customers can use their mouse to control the units in the VC and I don't see a list of them anywhere...

24 hours and no response...

You could take the approach that some of us have taken, by triggerering the default GPS vars and setting UseLegacyVars = true

Example from our RealAir Duke adaptation:

   (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) }

etc

 

   (L:530_CDI,Bool) if{
   0 (>K:GPS_NEAREST_BUTTON)
   0 (>L:530_CDI,Bool) }

for the CDI button

Edited March 24, 20188 yr by Bert Pieke

Bert, I did manage to get the GNS530 working via the "UseLegacyVars = true" for everything except the Power knob, the C/V push on the small knob, and the CDI button. For some reason the internal code of the GNS530 is overriding the default CDI command.  While the C/V push actually does work, it won't move the highlight bar from Com to Nav, so it's a question of guess work and/or good memory to know to which function the knob(s) are currently assigned.

Unfortunately, there are no "default XML commands" for a secondary GPS, so I'm unable to map those buttons and knobs via modeldef.xml scripting... :(

The only viable method absent actual L:vars to control the GNS430_2 directly is to use a "gauge overlay" where the buttons and knobs are mapped to the RXP gauge projected in the sim. This is ugly and truly destroys the illusion and experience.

Edited March 24, 20188 yr by RXP

Hi Bill,

Let me try to help you, and others, with this.

First, there is no need to send anyone any pre-made modeldef.xml! In short: no need to reinvent the wheel: just configure your modeldef to send the standard Flight Simulator GPS commands, configure the RXP GNS V2 ini file to "Use Simulator GPS Commands", and  your are done!

Configuring VC modeldef.xml for the Reality XP GNS V2 and the Reality XP GTN is super easy:

1. Open the product user's manual.
2. Custom Gps Commands p14
3. Command Modifiers p15

Do you want to also control GPS #2?

Refer to the User's Manual p15, 'Command Modifiers', to select where-to the command gets sent: either GPS #1 or GPS #2

Do you want to also support press and hold, then release? 

Refer to the User's Manual p15, 'Command Modifiers', to select press and release, press and hold, release.

 

Besides, on the same p15 of the User's Manual, you'll also get the answer to the 'Legacy Third Party Aircraft Panel Variables' question.

In addition, you might want to also explore User's Manual chapter Third Party Vendor Settings, p11.

In your use case, setting the following at least with this, will help you prevent your customers from deselecting the option in the GUI Settings Panel so that you'll reduce the likeliness of technical support for this:

locked = UseSimGpsCmds

NB: you can add as many coma separated settings to the 'locked' setting.

 

5 hours ago, RXP said:

Besides, on the same p15 of the User's Manual, you'll also get the answer to the 'Legacy Third Party Aircraft Panel Variables' question.

Jean-Luc, thank you for the reply. I am still puzzled however, since in your PDF file you mention only C type commands: KEY_xxx but do not mention the XML equivalents...

For example:

KEY_GPS_MSG_BUTTON is the C command.

(>K:GPS_MSG_BUTTON) is the XML equivalent.

Putting that together with your explanation of "Command Modifiers" gave me the idea to try using the XML equivalents along with an 'injected' decimal number. This works and is much clearer to dimwits like myself:

	<PartInfo>
	<Name>RXP_GPS2_ENTER_BUTTON</Name>
	<MouseRect>
	<Cursor>Hand</Cursor>
	<TooltipText>ENTER</TooltipText>
	<MouseFlags>LeftSingle+LeftRelease+DownRepeat</MouseFlags>
	<CallbackCode>
	(M:Event) 'LeftSingle' scmp 0 == if{ 10 (>K:GPS_ENTER_BUTTON) }
	(M:Event) 'LeftRelease' scmp 0 == if{ 12 (>K:GPS_ENTER_BUTTON) }
	</CallbackCode>
	</MouseRect>
	</PartInfo>

However, that still leaves a few problems. There is no equivalent command to the C/V push on the small left knob. Trying to use the CDI button with the XML equivalent of (>K:TOGGLE_GPS_DRIVES_NAV1) doesn't work. I can see the CDI needle quiver briefly, but the GPS remains in the VLOC mode, and will not switch to GPS mode.

I cannot get the power knob to work (because there is no XML equivalent, but I'm not too concerned about that.

Thank you for your kind assistance. I'll make sure to send you a link to the C310R Redux installer once its been finalized.

Read above (or in the manual..)

CDI button:

0 (>K:GPS_NEAREST_BUTTON)

Yes, that is not a typo.

45 minutes ago, Bert Pieke said:

Read above (or in the manual..)

Dang Bert! My eyes just glazed over when reading that...

It is strange, but I suppose that J-L had to hijack that (unused) command so that he could control the two GPS units separately, unlike the default toggle event that is global in scope.

So, ignoring the power knob, the only thing that's not working is whatever event is used to control the "C/V PUSH" (com/nav tuning selector).

Thanks!

The commands you are looking for are also listed:

KEY_GPS_BUTTON1          GNS COM/NAV toggle

As for the power and volume knobs:

KEY_GPS_POWER_BUTTON     GNS POWER/VOL Knob.
KEY_GPS_ACTIVATE_BUTTON  GNS NAV VOL Knob.

For these last 2, Command Modifiers Exceptions p15 explains further how to control them:

The following commands support "press-release" events only:
 KEY_GPS_POWER_BUTTON, KEY_GPS_ACTIVATE_BUTTON
To command knob rotation, use the 'press and hold’ modifier (value 2) as 'TURN LEFT’ (CCW) and the 'release’ modifier (value 4) as 'TURN RIGHT’ (CW): 

13 hours ago, n4gix said:

Jean-Luc, thank you for the reply. I am still puzzled however, since in your PDF file you mention only C type commands: KEY_xxx but do not mention the XML equivalents...

 

Only C++ events are listed because it is supposed to be developer grade knowledge, easy to figure out. If not, the SDK has it all for you though:

http://www.prepar3d.com/SDKv2/LearningCenter/utilities/variables/event_ids.html#Aircraft Avionics IDs

 

13 hours ago, n4gix said:

Putting that together with your explanation of "Command Modifiers" gave me the idea to try using the XML equivalents along with an 'injected' decimal number. This works and is much clearer to dimwits like myself:

This not only works, but it is much better than any other system where you write a L:var with an 'event' value, and let the GNS code read the event value asynchronously, because there is no lost event at all possible: every push, every release, gets acted on immediately by the Reality XP GNS V2!

In addition, should you make your aircraft with the default FS GPS in a 3D bezel as standard equipment, 95% of the modeldef.xml code is already done because it uses the same commands!

There is really no reason not to add the Reality XP GNS V2 option in any aircraft!

Edited March 25, 20188 yr by RXP

28 minutes ago, RXP said:

The commands you are looking for are also listed:

KEY_GPS_BUTTON1          GNS COM/NAV toggle

As for the power and volume knobs:

KEY_GPS_POWER_BUTTON     GNS POWER/VOL Knob.
KEY_GPS_ACTIVATE_BUTTON  GNS NAV VOL Knob.

The first and third KEY_events listed above are not mentioned in any of the FSX or P3D SDKs as valid commands. Which is honestly another point of confusion. If they aren't in the SDK, how is anyone supposed to know?

I've tried 8 (>K:GPS_BUTTON1) and it doesn't seem to do anything at all...

Well, I finally got the 530_1/430_2 version working.

Now however, I'm trying to set up the 430_1/430_2 version...

Only to discover that none of the buttons & knobs on 430_1 are working! Shouldn't this work using the same commands as the GNS530_1 ???

I've now spent four days on RXP and I'm still not done...

Edited March 25, 20188 yr by RXP

There are listed in the gauge.h file.

You've guessed right to convert to the equivalent XML event name in dropping the KEY_ prefix. 

As for the GPS_BUTTON1, I'll review this tomorrow. It is possible we've introduced a bug lately. What is the RXP GNS V2 version you've installed? We've also released a new update yesterday (v2.3.11)