OnCourse Software

Hi Dave

As someone who, now retired, but after a career in commercial software development and project management of software development projects. I know when software is not working. In MSFS ALTkey + n switches to the custom camera n. FSUIPC7.4.x does not seem to recognise the combination ALT+n. Instead all it sends to PF3 is n (n=0-9) which triggers the hotkey n. Making a flight impossible if you have custom cameras.

Regards

FSUIPC does infact recognise the Alt key so you could actually use it for a PF3 hotkey if you wished, although it's not really recommended.

I'm not by my MSFS flight sim rig so can't check what you're reporting but will do so later. If what you're saying is indeed correct then I will raise the issue with John Dowson as there's nothing I can do within PF3... FSUIPC simple tells me a hotkey has been used and I then sac to see which one. Personally, if it happens when I try it I would probably just change those keys within MSFS.

Update:

Okay, I've just tried this and there's no problem on my system. I don't actually use any custom cameras in MSFS so what I did was reassigned Alt+0 to Cockpit Zoom and checked that it did infact zoom. Then I started PF3 and once connected tried using Alt+1 several times to see if it would initiate PF3 calling for clearance but it didn't.

I'm using the latest version of FSUIPC but notice you are not... not sure if that will make any difference but certainly worth trying. If you still get the same problem then I would suggest you add LogButtonsKeys=Yes to the FSUIPC7 INI file, start MSFS and select FlyNow when ready. Then connect PF3 and recreate the problem a few times. Then disconnect PF3 and close MSFS. ZIP and attach the FSUIPC log file so we can see what is happening and we'll take it from there. If need be I'll contact John Dowson.

Thank you