Index in the RawGameController axis array. Index in the RawGameController button array. If DPadUp needs to be mapped from a switch position, then the DPadUp mapping should contain the values SwitchIndex and SwitchPosition ( Source is Switch). For example, if pressing DPadUp on the game controller, the mapping for DPadUp should contain the ButtonIndex value ( Source is Button). The table below lists the values that are needed to map a button.
The following sections explain the contents of each of the subkeys under the Gamepad, RacingWheel, ArcadeStick, FlightStick, and UINavigation keys. The table below lists the required and optional subkeys under UINavigation subkey: Subkeyįor more information about UI navigation controllers and the above commands, see UI navigation controller. The table below lists the required and optional subkeys under the FlightStick subkey: Subkey The table below lists the required and optional subkeys under the ArcadeStick subkey: Subkey The table below lists the required and optional subkeys under the RacingWheel subkey: Subkey If you add your game controller as a supported Gamepad, we highly recommend that you also add it as a supported UINavigationController. The table below lists the required and optional subkeys under the Gamepad subkey: Subkey Subkeys under the device root location are detailed in the following sections. Your device installer should add this data to the registry (either via setup or an INF file). Indicates that this particular device should be disabled. The table below explains the expected values under the device root location: Name HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GameInput\Devices\VVVVPPPPUUUUXXXX Mappings for a device with Vendor ID (VID) VVVV, Product ID (PID) PPPP, Usage Page UUUU, and Usage ID XXXX, will be read out from this location in the registry: By doing this, all UWP games (and any desktop games that use the WinRT API) will be able to support your game controller. All IHVs should add this data for their compatible controllers. The namespace allows independent hardware vendors (IHVs) to add data to the PC's registry, enabling their devices to appear as Gamepads, RacingWheels, ArcadeSticks, FlightSticks, and UINavigationControllers as appropriate. If it works there then you have eliminated the OS as the problem.This topic is meant for manufacturers of Windows 10-compatible game controllers, and doesn't apply to the majority of developers. Move your throttle quadrant levers and you should see the corresponding axis move on the screen. You will then see a screen where you can test all of your buttons and you should see 5 axes.
Select Game controller settings in the menu that pops up and then on the Game Controllers window highlight Saitek Pro Flight Yoke and then press the Properties button.
Look for the Saitek Pro Flight Yoke icon and right click on it.
Open up Control Panel in Windows 10 and select Devices and Printers. That PS/2 throttle quadrant is rolled into the flight yoke. Windows 10 Device Manager only shows 4 devices connected. I have a Saitek Pro Flight Yoke with the PS/2 throttle quadrant, an additional USB Pro Flight Throttle Quadrant, Rudder Pedals, and the Cessna Trim Wheel. The yoke is then plugged into your computer via one USB plug and the OS (and FSX/P3D or X-Plane) then picks up the Pro Flight Yoke as a device with 5 axis, X and Y for the yoke and Z, Rx, and Ry for the throttle quadrant. That throttle quadrant plugs into the back of the yoke via a PS/2 type plug. The Saitek Pro Flight Yoke comes with a throttle quadrant. Windows doesn't see the PS/2 type throttle quadrant as a separate device. Vorte圆81 you're making the same assumption that the OP is making.