January 3, 20206 yr I've been trying to install the RXP GNS 530 software to map to the hardware buttons. I've read a few posts online that there have been issues doing this with Win10 since it already has win+{key} functions mapped to Window programs. After noticing that the default install instructions have failed regarding the button mapping, I've tried remapping the buttons in FSUIPC.ini to use 'shift' instead of 'win', plus changed the win+F13-F15 shortcuts to be shift+3-5 since my keyboard doesn't have the F13-F16 keys. Nothing has worked, and has rendered my GNS 530 hardware buttons useless. Has anyone successfully mapped the RXP GNS 530 buttons to work with the hardware? I'm at my wits end after spending the day trying to figure this out... Is my only working option to downgrade to Windows 7?? Edited January 3, 20206 yr by hobbes replaced 'alt' with 'shift'
January 4, 20206 yr Author I've also tried the following, and still no luck: Disabled Windows Hot Key Shortcuts, and reverted to default install commands (using 'win +', instead of custom 'shift +'). Type gpedit in the Search and then click Edit group policy. (This will open Local Group Policy Editor). Navigate to User Configuration > Administrative Templates > Windows Components > File Explorer. In the right-side pane, look for Turn off Windows + X hotkeys and double click on it. Check Enabled and click OK. Restart the computer to make the settings take effect. Disabled UAC and ran P3D as administrator. Also added [KEYBOARD] RXP ini settings into the aircraft RealityXP.GNS.INI file (trying everything here that I can think of). Still no luck. @RXP I've sent you a PM, maybe there's something you know that I haven't tried yet? Edited January 4, 20206 yr by hobbes
January 4, 20206 yr Author For context, I'm running P3D v4.4.16, and RXP Garmin GNS 530. RXP.INI and/or RXPGNS.INI did not exist in C:\ProgramData\Reality XP\Common\Settings, so I created the Settings sub-folder, and added both INI's (since the install instructions mention both filenames), and added keyboard mapping to there. [KEYBOARD] 530_CONTRAST_INC=win+y 530_CONTRAST_DEC=win+z 530_CONTRAST_RESET= 530_POW=win+s 530_COMFLIP=win+q 530_NAVFLIP=win+w 530_CDI=win+F9 530_OBS=win+v 530_MSG=win+F13 530_FPL=win+a 530_PROC=win+F2 530_NAV=win+c 530_DTO=win+F3 530_MNU=win+F4 530_CLR=win+F5 530_ENT=win+F14 530_RANGE_INC=win+h 530_RANGE_DEC=win+i 530_LKNOBO_L=win+j 530_LKNOBO_R=win+k 530_LKNOBI_L=win+F6 530_LKNOBI_R=win+F7 530_LKNOBPUSH=win+n 530_RKNOBO_L=win+o 530_RKNOBO_R=win+F8 530_RKNOBI_L=win+F10 530_RKNOBI_R=win+F12 530_RKNOBPUSH=win+F11 530_EXPORTFPL= 530_SWAPRADIOS=win+F15 FSUIPC5.INI (P3 being GNS 530) (buttons 1-6 omitted in paste as they are for different hardware) [Buttons] PollInterval=25 ButtonRepeat=20,10 7=P3,12,K81,40 -{Key press: win+Q}- 8=P3,0,K83,40 -{Key press: win+S}- 9=P3,1,K83,40 -{Key press: win+S}- 10=P3,13,K87,40 -{Key press: win+W}- 11=P3,2,K89,40 -{Key press: win+Y}- 12=P3,3,K90,40 -{Key press: win+Z}- 13=P3,7,K75,40 -{Key press: win+K}- 14=P3,6,K74,40 -{Key press: win+J}- 15=P3,5,K118,40 -{Key press: win+F7}- 16=P3,4,K117,40 -{Key press: win+F6}- 17=P3,14,K78,40 -{Key press: win+N}- 18=P3,16,K120,40 -{Key press: win+F9}- 19=P3,17,K86,40 -{Key press: win+V}- 20=P3,18,K124,40 -{Key press: win+F13}- 21=P3,19,K65,40 -{Key press: win+A}- 22=P3,20,K67,40 -{Key press: win+C}- 23=P3,21,K113,40 -{Key press: win+F2}- 24=P3,10,K119,40 -{Key press: win+F8}- 25=P3,11,K79,40 -{Key press: win+O}- 26=P3,8,K123,40 -{Key press: win+F12}- 27=P3,9,K121,40 -{Key press: win+F10}- 28=P3,15,K122,40 -{Key press: win+F11}- 29=R3,27,K72,40 -{Key press: win+H}- 30=R3,26,K73,40 -{Key press: win+I}- 31=P3,25,K114,40 -{Key press: win+F3}- 32=P3,24,K115,40 -{Key press: win+F4}- 33=R3,23,K116,40 -{Key press: win+F5}- 34=P3,22,K125,40 -{Key press: win+F14}- 35=P3,29,K126,40 -{Key press: win+F15}- Cessna (non-A2A) panel.cfg gauge00=rxpGNS2!GNS_530_1,-29,-12,155,150 I have cleared all command shortcuts from P3D control options, and am strictly using a registered copy of FSUIPC5. Edited January 4, 20206 yr by hobbes more config context
January 4, 20206 yr Author UPDATE: So thankful for @DavidP's write up found here: This solved my issues, and would be nice if emuteq.com updated their documentation with this post.
Archived
This topic is now archived and is closed to further replies.