Pgdavis2

I tried that driver but no luck. But I determined that it does work as expected provided the touch screen is designated as the MAIN Windows monitor. Since I only have 1 touch screen this is fine. But I wonder if people have multiple touch screens does it work? Just curious....I'm all set with 1. Thanks for the responses.

I have both the GNS 530 and GTN 750 running Windows 10, P3Dv4.5 with a primary 4k and secondary small 10" touch screen for the GPS units. I can't get either GPS to accept touch screen clicks, even though the screen is calibrated and works fine in other apps. Mouse works. Tried with and without Bezel - same issue either way I'm sure there's some setting I am missing here...any ideas?

Looks like the only way is FSUIPC5. I was hoping to go native only...close but not quite there. FYI - I'm using Desktop Aviator 430 panel for P3D. Works 100% when you assign buttons with FSUIPC.

Anyone figured out how to assign the inner/outer freq dial to hardware knobs? Every other button/knob has a fairly easy mapping in the native P3D v4.5 keyboard assignments but that one

Ahh.found.it. It's called "Gps Nearest Button" in FSUIPC

I have the same personal challenge but I don't quite get the solution (to make the CDI hardware button work using FSUIPC). There is no KEY_GPS_NEAREST_BUTTON selection in FSUIPC... Can you please give me the steps to configure this? I know there are FSUIPC and RXP .ini files that may need some entries but need some handholding please :)

I just installed the 2.3.5 RC and it's working now :) Thanks again!

Thanks for your note! I'm unable to get the GPS buttons to work using FSUIPC. The Com buttons do work when mapped using FSUIPC but none of the "GPS..." commands function. When I click the Proc button in the FSUIPC setup, the button press is recognized, but checking the "Select for FS Control" and selecting "GPS Procedure Button" doesn't work. Is there some other step I'm missing?

What's the status on this bug fix? I haven't seen a new version or am I missing something?

+1

Yeah I had the same issue - they identified a bug in 2.3.4 and said they will have a fix sometime today

Prior to 2.3.4 I had my hardware buttons configured through FSUIPC5 using "Buttons+Switches". For example, my Enter button is set to the "Gps Enter Button" (Control sent when button pressed) I didn't have to do anything to the RXP.ini file and the hardware worked fine. I assumed that since they don't work anymore that I have to do something to get it to work now with 2.3.4 but I'm hearing from you that nothing changed in this regard. That makes me think there is a bug preventing FSUIPC5 to work with 2.3.4. Any suggestions?

Updated to v2.3.4 but my buttons no longer work (via FSUIPC). I see some features have changed but I am not clear how to reassign my hardware buttons Instructions on using the .ini file are not clear to me - can anyone help?

This thread answered my question: Looks like this is a known issue with P3Dv4.1 - looking forward to the RXP update!

Up until I upgraded to P3D 4.1 today I was able to use the GNS530 as my FMS replacing a Proline on the Carenado CJ AP worked beautifully in Nav and approach mode with my flight plan and procedures Now that I applied the 4.1 patch the Nav mode on Autopilot doesn't work anymore - the plane just turns North in Nav mode rather than flight to the waypoints I know there's a RXP patch coming out for 4.1 - is this issue to be expected and will the patch fix something like this?