The Gamepad remote reads all of its data from the device data of the USB Game Pad Remote device that is right next to the USB Game Pad device.
If you open this device in Advanced > configuration >Devices, you'll see device data under Configuration like this:
by default, the configuration device data is filled with:
up USB-GAMEPAD-UP USB-GAMEPAD-UP
down USB-GAMEPAD-DOWN USB-GAMEPAD-DOWN
left USB-GAMEPAD-LEFT USB-GAMEPAD-LEFT
right USB-GAMEPAD-RIGHT USB-GAMEPAD-RIGHT
ok USB-GAMEPAD-B1 USB-GAMEPAD-B1
back USB-GAMEPAD-B9 USB-GAMEPAD-B9
back USB-GAMEPAD-B2 USB-GAMEPAD-B2
skipback USB-GAMEPAD-B5 USB-GAMEPAD-B5
skipback USB-GAMEPAD-B7 USB-GAMEPAD-B7
skipfwd USB-GAMEPAD-B6 USB-GAMEPAD-B6
skipfwd USB-GAMEPAD-B8 USB-GAMEPAD-B8
menu USB-GAMEPAD-B3 USB-GAMEPAD-B3
menu USB-GAMEPAD-B10 USB-GAMEPAD-B10
This can be changed appropriately, for now, both entries are the same, as I don't have an action for when a button is held down for a repeat action.
it corresponds literally to the entries in the RemoteMapping table:http://wiki.linuxmce.org/index.php/Infrared_Remote_Buttons_Understood_by_LinuxMCE
and the Bxx value is the button number returned by the driver.
You can install and use the jstest utility from a shell to look to see which buttons correspond to which button #s.
What is confusing me is, that the Game Player screens all have a screen type of G. Which I explicitly created for the Game Player use. The G screen type is intercepted by the USB Game Pad driver, and it causes all of the button presses except for what is mapped as Home, to be ignored by Orbiter entirely, until another screen is displayed. So the behavior you're seeing should never happen, unless your game pad is mapping some unusual events outside of the scope of a joystick.
You can test this, by removing all the Home and Start entries out of your gamepad configuration. Or just blanking out the Configuration device data entirely.