![flatout 2 key code flatout 2 key code](https://www.game-key-compare.com/images/487a900d1ff0/flatout-cover.jpg)
Logitech wheels can be configured via the oversteer tool from the oversteer AUR package. # ffcfstress -d /dev/input/event15 position center force Input device ID: bus 0x3 vendor 0x46d product 0xc293 version 0x100
FLATOUT 2 KEY CODE DRIVER
$ evtest /dev/input/event15 Input driver version is 1.0.0 evtest then shows the events coming from the wheel: When using evtest for testing, instead of the js0 as device handler eventX is needed, which in this case is event15 for a Formula Force GP wheel. In case that only events should be displayed, -event can be added as flag.
FLATOUT 2 KEY CODE FULL
Whenever the input is changed, jstest will print the full state of the device. $ jstest /dev/input/js0 Driver version is 2.1.0. To test the wheel with jstest simply call it with the device handler (in this case with a G29 wheel and js0): A graphical version of jstest is available in the AUR as jstest-gtk-git AUR.
![flatout 2 key code flatout 2 key code](https://www.allkeyshop.com/blog/wp-content/uploads/allkeyshopFlatOut2.jpg)
An alternative is evtest which can be installed via the evtest package. One common tool is jstest which can be installed via the joyutils or the linuxconsole package from the community repository. Please memorize the Handlers, here event15 and js0, as these will be necessary to call the tools for testing and configuring the wheel.įor testing the wheel there are multiple tools that can be accessed via the command-line.
FLATOUT 2 KEY CODE INSTALL
If you do not see your Logitech listed as an input device, you need to install usb_modeswitch package. WingMan Formula Force GP Checking input device $ cat /proc/bus/input/devices I: Bus=0003 Vendor=046d Product=c293 Version=0100 # dmesg usb 5-2: new low speed USB device using uhci_hcd and address 6 $ lsusb Bus 005 Device 006: ID 046d:c293 Logitech, Inc. When the wheel is plugged in, the following commands can be used to identify the wheel: