Oh okay,
first of all, as of now when having my driver installed the Wiimote is no longer compatible with Dolphin (or any other third-party program) as my driver currently blocks all other access from User-Mode applications.
The LEDs show you the current battery level (all four lit -> fully charged, just the last one -> almost depleted). So it was working. Anyhow my driver only makes the Wiimote available for the older DirectInput API, which is obsolete and only very few modern games support it (i know of GTA V). So that may be the reason Rocket League didn't picked it up. The newer now used API is called XInput for the Xbox-like Controllers.
Coping driver files (or Windows System files in general) directly is never a good idea, as you said yourself, that corrupts your system in almost every case. Drivers are not just the .sys and .dll files, but there are some more files in the driver store (.inf file telling windows what device the driver is for) and some registry keys, that need to be changed/removed as well.
When you try my driver and need any help, feel free to ask me
Am a bit curious if my driver does interfere with Input Mapper.
first of all, as of now when having my driver installed the Wiimote is no longer compatible with Dolphin (or any other third-party program) as my driver currently blocks all other access from User-Mode applications.
The LEDs show you the current battery level (all four lit -> fully charged, just the last one -> almost depleted). So it was working. Anyhow my driver only makes the Wiimote available for the older DirectInput API, which is obsolete and only very few modern games support it (i know of GTA V). So that may be the reason Rocket League didn't picked it up. The newer now used API is called XInput for the Xbox-like Controllers.
Coping driver files (or Windows System files in general) directly is never a good idea, as you said yourself, that corrupts your system in almost every case. Drivers are not just the .sys and .dll files, but there are some more files in the driver store (.inf file telling windows what device the driver is for) and some registry keys, that need to be changed/removed as well.
When you try my driver and need any help, feel free to ask me
Am a bit curious if my driver does interfere with Input Mapper.