Controller troubleshooting: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Controllers come in 2 types *class-compliant ones - that don't need any kind of driver/software - you just plug them in and that's it (true plug&play) *the ones that require d...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Drivers & first use/install == | |||
Controllers come in 2 types | Controllers come in 2 types | ||
*class-compliant ones - that don't need any kind of driver/software - you just plug them in and that's it (true plug&play) | *class-compliant ones - that don't need any kind of driver/software - you just plug them in and that's it (true plug&play) | ||
Revision as of 03:17, 14 April 2013
Drivers & first use/install
Controllers come in 2 types
- class-compliant ones - that don't need any kind of driver/software - you just plug them in and that's it (true plug&play)
- the ones that require drivers or other software to work ok
If a controller comes with drivers (either on a CD or downloadable from the manufacturer website) always install them before connecting the controller to the computer. This is true especially on Windows machines. If you first hook-up the controller before installing the driver then Windows will pre-install a default driver that it finds from Windows Update servers. This driver might work ok or it might not. Also, the controller name might be reported differently than it would've been with it's original driver installed. Because it's name will change than there is a chance that the script inside FutureDecks might not recognize the controller correctly.