Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on Talk:Final Fantasy XIII

This is a permanent link to the first version of this post. You can view later versions on the post history page.

Point taken. TBH I'm not 100% sure how to put it into easy to understand layman terms - I'll try my best to explain it here, maybe this is too technical and not "issue-driven" enough, but I'll give it a shot. Typically there are 2 drivers for XInput controllers: a XInput driver and a HID driver.

For example, a wired Xbox 360 controller will having the following in Device Manager in Windows 8:

1) Human Interface Device->HID-compliant game controller: This handles Kernel level HID calls and associated APIs including RawInput (and the depreciated DirectInput which wraps around RawInput).

2) Xbox 360 Peripherals->Xbox 360 Controller for Windows: This handles XInput calls.

Each driver has its own options/preferences. With XInput controllers a HID driver isn't required, and even for those with one it can be disabled or even uninstalled and still have it functional for apps using XInput. This leads to the issue at hand where one driver or the other gets disabled, removed, or in rare cases never installed to begin with.

If someone did understand the above, the challenge is to put in layman terms, like "Make sure you have a HID driver for your controller installed and enabled".