Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also make sure it is actually set as the default game controller, by going to Control Panel > Devices and Printers > USB Joystick (or whatever lists as game controller device name there), right click game controller > Game Controller Settings > Advanced (listed here is a default controller, it might say [NONE], but in that list should be the one u currently have connected, select that and click OK.
Then see if it now works within a game; if not then u need an emulator, like Xpadder or X360CE
K, I tried that, but still no dice. Which one is better, Xpadder, or X360CE? (Sorry, I'm a bit of a newb when it comes to this, lol!)
Yea, you just have to copy/paste the .dll files, so it's not too much trouble, but I am going to check those out, lol!
K, YOU buy me one, and I'll use it... >_>
As for an emulator, I never personally tried X-Padder, that is merely suggestion based on word of mouth from others who've had success with that.
As for X360CE, this I have actually used. I've used it with a few various/generic controllers that otherwise wouldn't work or had native support. Two of which were Interact Axis Pad USB and original Xbox controller (via USB adapter off an Ebay store) and both I had used for many years before 360 console was even on the market and also while 360 was still fairly new. While that was all back in my days of using WinXP, I know X360CE still works the same under Vista/Win7/Win8.
However some may find it a little odd as far as how it works; it is not a piece of software u simply install. You are basically given SDK files with a Config file, which you place within a game's root folder (whatever root folder a game .exe is located in) and basically extract the files there. Then connect your controller, let Windows auto install whatever generic driver it uses for that by default, then go to Devices and Printers, right click that controller and click on Game Controller Settings. Then click Advanced and ensure the controller name is selected, as this will be how u choose a default controller (should anything else show up in there). You can click the Properties box and that will allow you to double check that the controller's buttons and axis' work as-is.
Now the point of X360CE is to force 360 emulation for a connected controller within a game of which u've extracted those files to. So basically u will have to extract those X360CE files to each root folder for each of your games where it doesn't work in-game without such files. If a certain button or series of buttons on the controller do not allign with what they would be in-game if u had an actual 360 controller connected, that is what the config file is for, which allows you to re-map the keys properly for said game. Again this will differ among controllers, as usually ones that have a Playstation styled layout, the core (A, B, Y, X) are usually reversed or will be wrong in most situations. That shouldn't be of any real concern though as long as the buttons actually do work in-game, however it can be confusing if a game provides on-screen instruction for which buttons to press and such; this is when re-mapping via the x360ce config file may be needed.
Thanks! I'm still trying new stuff, and seeing what works best, and this explains a lot. :D
(And I DO plan on getting a wired 360 controller, I'm just lacking any money to spend right now, and the good ones are around $30-40, lol!) :P