![]() Switching between the two inputs doesn't work either. The LT/RT sticks act as camera controls, the start button is the shooting button, the right analog stick doesn't work, etc. The inputs are utterly messed up and with no way to configure them manually. Binary Domain: This one is the biggest headache by far. ![]() Having to keep an additional controller turned on in order to use another controller is silly though.Ģ. ![]() ![]() Strangely, I've found that if I turn on a paired 360 controller (which would be read as Controller 2), my Logitech controller then works properly with the game. Dead Rising 2: Off The Record: The controller will not work with this game at all. Problem is that not every PC game reads it like a 360 controller, which causes all sorts of weird issues. The D-Pad is better, it grips better, and it has a toggle for switching between Xinput and Direct Input. As a PC controller, I find it much better than using an official 360 controller (which I also have, wireless receiver included). Now, launch the game again and your controller should work fine.I use a Logitech F710 Wireless Gamepad for gaming on the PC. Make sure to have your game closed before doing this. The most successful fix is to create an empty file called joypad.txt in your $HOME/Documents/Electrontic Arts/Dead Space (yes, there is another "t" in Electronic) and $HOME/Documents/ Electronic Arts/Dead Space folders. Yeah, there's an issue with constant spinning of the camera after the initial intro movie. oh no! What's with all this spinning? Make it stop!. If everything worked as expected the game should be able to see the controller but. That is good, it means the game will use the xinput1_3.dll that we supplied. You may see the error about the config file that I talked about earlier. Set it to native.Ĭlick Apply and then OK and you should be done. Wine Configuration and go to the Libraries tab, enter xinput1_3 in the box as shown in the screen shot below and then click the Add button. Xinput1_3.dll file that the program shows in the bottom right corner? We'll add and override in winecfg for it. We need one more thing because applications that try to find xinput devices will still not be able to. Just check that the buttons work as they should before changing anything if you used my. (Note: You may not need to mess with the setting at all. It might also complain that the ini file does not have the right version. The program might complain that it found no ini file and will offer to create one. Once you have checked that everything works right, hit the save button. It will probably get some right and some wrong. It will try to guess, as best it can the button and joytick axis mappings. This will run and prompt you to do some stuff. Run Command button in the bottle manager (make sure the correct bottle is selected) go to the folder where you have unpacked the zips and run x360ce.exe. NET 4.0 to the bottle where your game is installed ini file that has worked with my Xbox 360 (wired) controller on Manjaro and Ubuntu here: The first zip contains the libs that actually do the translating and the latter is a program that allows you to configure your gamepad (map buttons, joystick axes, d-pad buttons, etc. Here's what to download and how to use it (at least, what worked for me): The workaround is to use a wrapper that "translates" xinput to dinput. So what's the problem and how can we solve it? Well, the xbox360 controller is an xinput device but wine has implemented support for dinput. I'm using an xbox360 controller and it is recognized out of the box in Ubuntu 12.04. The steps in here should apply to any controller as long as your (linux) system has a driver for it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |