your controller is currently in xinput mode f310 что делать
Your controller is currently in xinput mode f310 что делать
Umineko: Golden Fantasia
It’s cheap, easy to find, and easy to use! I’m sure I’m not the only person who plays this game with the F310 Gamepad. This will tell you what button number corresponds to what (more familiar) button. My goal here is to demystify this part of the Configuration Tool menu (the option when you launch the game, not the in-game options) and make the process of rebinding your controls a little easier. I will make a list for both of the controller’s modes, XInput (Xbox 360 pad simulation) and DirectInput, since the F310 is a «dual action» pad.
Both of the controller’s input modes are accepted by the game but each mode will have its unique limitations as of the current game version. Until (if) additional button support gets patched in, you will need to use an outside program of some kind to use the other buttons.
If you swtich from one mode to the other outside of the game, you will need to rebind the controls again to use the new mode or toggle back to the mode you last used; the game will not remember both. Don’t switch while the game is running or your character will simply jump in place and your inputs won’t be recognized until you switch back.
When you use XInput mode, the game limits you to buttons 1-10. That means L2 & R2 (Left and Right Triggers) as well as the Logo button will not be recognized by the game. I really don’t recommend using this mode if you can help it; DirectInput is better for this game (right now) because more buttons work.
The Logo button has no functionality in this mode.
When you use DirectInput mode, the game limits you to buttons 1-12. That means the Logo button will not be recognized by the game, which isn’t a problem since that button doesn’t work in this mode to begin with. Everything else will work.
For Umineko: Golden Fantasia, I recommend using DirectInput mode. Everything but the Logo button will work. and it’s not like you need a 13th button anyway.
Just remember that how you set your buttons affects what you press to «Accept» and «Cancel» things. Accept is always what you set «Weak Attack» to and Cancel is always what you set «Medium Attack» to.
I know it’s a hassle but I hope this information serves to lighten that hassle a tiny bit.
Your controller is currently in xinput mode f310 что делать
I have a controller problem with Trine: Enhanced Edition and Trine 2 on Linux. My Logitech Gamepad F310 (Xbox 360 controller compatible) has a strange trigger holding issue which is also present for Logitech Gamepad F510. I found some XInput and libSDL related clues. There is a workaround for the issue; using xboxdrv:
Sorry for necromancy. I confirm that this problem still persists on Ubuntu Mate 17.04 x64 as June 2017:
I have a Logitech Gamepad F310 which shows up as a generic xbox controller. It mostly works, except that the game is convinced that one of the triggers is being held down constantly, and all the right joystick axes were reversed by default.
The XInput/DirectInput controller, Logitech Gamepad F310 does show up as Logitech Gamepad F310 in XInput mode; the controls are mapped mostly correctly but triggers kept being held down and right joystick axes are reversed. Right joystick axes can be remapped correctly but trigger hold down issue remains. Interestingly enough, when F310 is set to DirectInput mode via controller’s switch, the controller shows up as Logitech Logitech Dual Action; all the controls are incorrectly mapped but can be remapped correctly and there is no trigger holding problem. Same goes with another controller, Logitech Cordless RumblePad 2 which is DirectInput only; incorrectly mapped but can be remapped correctly and there is no trigger holding problem.
That might be a libSDL related XInput problem which is caused by out of dated libSDL version: v1.3. libSDL 1.3 is an obsolete version which is discontinued. Most GNU/Linux distros use v2.0 nowadays; old distros relied on v1.2. Upgrading game’s libSDL would solve the issue.
This is my mouse BUS=002 Device=003
These number changes computer to computer.
This solved my issue! I needed to quit the game and Steam client. Then installed xboxdrv and run it with following command.
Now, F310 (in XInput mode) is detected as Microsoft X-Box 360 pad and everything is mapped correctly, plus no holding trigger problem. BUT, I shouldn’t rely on a third party tool which requires sudo command to function.