Thanks for the quick response Pete.
Yes, the USB keypad produces Num1, Num2, etc responses with numlock on according to FSUIPC but for some reason they don't work directly (e.g. without programming in FSUIPC). This is also the same in FS9 - a separate USB numpad does NOT work directly - you have to assign keypress via FSUIPC to get it to work. For both FSX & FS9 they do work correctly on the main keyboard without using FSUIPC but I am trying to remove the need for a keyboad on the flight sim (I control basic keyboard functions via another PC using VNC to remote in). The only reason I need the keyboard is for the ATC menu.
When the ATC window is open, nothing happens but if you close the window, press any of the buttons & then open the window again the function is actioned. The only problem is you have to do this each time for each function needed.
You are correct regarding using buttons. I have a CH Yoke & Throttle & if I assign any buttons on these as ATC Menu options they work fine with the window open.
I really wanted to use the USB keypad as it is a good size & feel for the ATC menu controls & can be integrated more easily into my cockpit.
You are correct regarding the ATC window affecting controls on the keyboard numpad - it looks like it is an FS bug with the ATC window.
I did notice something strange....... with the FSX ATC window, there is what looks like a ATC response window at the top of the ATC window which scrolls for seeing ATC responses. If the numlock is off & the window is open, numbers seem to control this scrolling part of the window - e.g. numpad 9 scrolls the response up & numpad 3 scrolls them down. I'm guessing this is the buggy part.
Regards
Geordieboy.