Hi team

anyone knows how to enable a repeat of pushing joystick button or sending keyboard shortcut to action the "press and hold" function of the home button?

I switched over to the reality-XP GTN from F1 due to the much easier and reliable keyboard and joystick configuration options.  Only issue I have is that the Menu button 'Press and Hold' function only works when using the mouse on the screen.   I have a dedicated touchscreen unit for the GTN750 so I am using it without the bezel.  

I have tried using a keyboard shortcut mapped in the INI file and a joystick button mapped to GPS Menu button in FSUIPC (with repeat) but to no avail.   The configuration works in terms of the action bringing up the home screen, but holding the button or keyboard shortcut, does not initiate the "Press and Hold" action to go to the map.

obviously this is not a big deal.  I can just as easily go to map once in the home page.   I am just wandering what I missed and doing wrong

any ideas?

 

Regards - Ran

Hi,

Keyboard shortcuts are supporting the 'press' event only. When issuing the key press on the keyboard, the device will automatically receive a press then a release event and can't handle long presses.

For more precise press then release actions, I'd suggest you review the "GPS Commands" chapter in the RXP User's Manual (p20). This will allow you mapping any of the standard GPS Flight Simulator commands to work with the GTN with a complete control on press and release actions.

Thanks for your reply

As I mentioned before, I have tried keyboard mapping, as well as the standard GPS commands.   when using the GPS commands I have:

• enabled "Use Simulator GPS commands" in the GTN750 gauge settings
• mapped a joystick button to GPS_Menu_buttton using either FSUIPC set to repeat when held, or directly in the simulator.

and I am getting the same behavior.  Press only, no Press and Release

 

Regards - Ran

 

 

 

Please read the RXP user's manual for how to use the default commands are press, press-release, release only. It is detailed with examples.

NB: holding is not repeating.

 

Thanks for that

call me stupid, but I have read the manual, and the examples, several times.  I still cannot work out how to use a single button to apply both "Press" and "Press and hold" actions.

do I need to write an elaborate LUA script for this or is there a simple way?

Regards   - Ran

 

Edited July 16, 20205 yr by Ran

extract from the manual p20 (please look into the manual, it is using color codes to help matching commands and values):

Command Modifiers

Flight Simulator commands have a parameter which is generally only used for actions requiring a value, like the position of a flap lever. Other actions which toggle or trigger a state change usually pass the value 0. The GTN uses this existing parameter in order to modify the "KEY_GPS" (C++) or the "GPS" (XML) command action. This enhances integration between the GTN and 3D cockpit models, add-ons modules, any other XML or C gauges. The command parameter is interpreted as a bit-field where each binary digit represents a specific modifier:

•Bit #2: press and hold the button if set.
•Bit #3: release the button if set
.•Bit #4: command to GPS unit #2 if set, to GPS unit #1 if clear.

For example:

Sending the HOME key press-release event to GPS#1: GPS_MENU_BUTTON, 0
Sending the HOME key press-release event to GPS#2: GPS_MENU_BUTTON, 8= bit4 (8)
Sending the HOME key press and hold event to GPS#2: GPS_MENU_BUTTON,10= bit2 (2) +bit4 (8)
Sending the HOME key release event to GPS#2: GPS_MENU_BUTTON,12 = bit3 (4) +bit4 (8)

58 minutes ago, Ran said:

do I need to write an elaborate LUA script for this or is there a simple way?

As long as you can bind a standard Flight Simulator command (GPS_MENU_BUTTON) to a key and have the tool you're using to make this binding to not only send the command, but to also send it with a value (12 for release), the 'logic' behind all this is all documented above and there is nothing more needed.

You're looking to map a hardware key (keyboard) to a standard Flight Simulator command first and foremost. I don't know to which extent of the tool you'll use to make the binding can also be configured to send values along (FSUIPC?)

 

This can all be done in Spad.NExt....Excellent tool along with the Reality XP products.

@RXP I may be stupid, but not that stupid, so please stop pointing me to the manual which is not much help at all.

How can I map a single button to two different actions using either the direct mapping in the sim or in FSUIPC (without the need to write an LUA script)?

I have mapped the button to the GPS_Home_Button and yes the default setting sends 0 as the value, which is Press only according to the manual, right? - so how can I use the SAME button to send the Press and Hold value when holding the button (using in sim button to action mapping) ? - obviously I cannot, so just say so.

I'll look at SPAD.next

Ran

 

 

 Hi Ran,

Sending the HOME key press-release event to GPS#1: GPS_MENU_BUTTON, 0
Sending the HOME key press-release event to GPS#2: GPS_MENU_BUTTON, 8= bit4 (8)
Sending the HOME key press and hold event to GPS#2: GPS_MENU_BUTTON,10= bit2 (2) +bit4 (8)
Sending the HOME key release event to GPS#2: GPS_MENU_BUTTON,12 = bit3 (4) +bit4 (8)

 

12 hours ago, Ran said:

I have mapped the button to the GPS_Home_Button and yes the default setting sends 0 as the value, which is Press only according to the manual, right?

0 is press and release (default).

There is no "sending anything when holding the button". There is instead:

• "send press when pressing the button"
• "send release when releasing the button"
• "do not send anything while holding the button".

I believe FSUIPC support would be best answering such question about how to make their program do specific actions, or better said, how to configure FSUIPC to send an event with a value upon either pressing or releasing a button.

In addition, using google search with "site:avsim.com RXP FSUIPC HOME BUTTON" gives:

https://www.google.com/search?q=site%3Aavsim.com+RXP+FSUIPC+HOME+BUTTON

Which further leads to:

and this one (which is also pinned in our GNS Fltsim forum):

might be worth reading too!

Edited July 17, 20205 yr by RXP

Thank you @RXP

So just to get this topic back on track. 

The initial question was whether it was possible to use a keyboard or button mapping to provide both "Press" and "Press & Hold" functionality of the GTN Home button without scripting.  I now understand that the answer is "you can't".  that's all I needed to know.

I have both the RXP GNS and GTN, and have successfully mapped all buttons to matching functions either directly in the SIM and/or using FSUIPC & Mobiflight which drives the arduino board that all buttons, encoders etc are connected to.

The GTN Home button is the only button that has dual functionality, and hence my question.   Now that I know that key or button mapping does not work for both "Press" and "Press & Hold", I'll look at an Lua option such as the TripleUse.Lua script.

Thanks again - Ran 

On 7/17/2020 at 4:56 PM, Ran said:

The GTN Home button is the only button that has dual functionality, and hence my question.   Now that I know that key or button mapping does not work for both "Press" and "Press & Hold",

I'm sorry for reviving this topic but I came to realize this was not fully answered.

The key here is that there is no "press and hold" event at all! The only events you need are PRESS and RELEASE. Depending on the amount of time between the two, the GTN/GNS V2 will interpret this as a "press and release" or a "press and hold then release" mode (for the CLR or HOME buttons typically).

So what you have to do is map all your hardware buttons to send the PRESS event when pressed, and the RELEASE event when released, in other words, like I said above for GPS2 these are the values 10 and 12 respectively (for GPS1 use 2 and 4 respectively):

On 7/17/2020 at 2:07 PM, RXP said:

Sending the HOME key press and hold event to GPS#2: GPS_MENU_BUTTON,10= bit2 (2) +bit4 (8)
Sending the HOME key release event to GPS#2: GPS_MENU_BUTTON,12 = bit3 (4) +bit4 (8)

 

Edited July 26, 20214 yr by RXP