In this case the errors are due to our basic DirectInput init not taking the time to enumerate the available controls before trying to configure their properties.
The current plan is to switch to using SDL2 for all input in 1.16 so simply ignore these specific errors for now.
Added by danij about 10 years ago
Added by
Windows|Joystick|DirectInput|InputSystem|Client: Don't log errors regarding nonexistent joystick controls
In this case the errors are due to our basic DirectInput init not
taking the time to enumerate the available controls before trying
to configure their properties.
The current plan is to switch to using SDL2 for all input in 1.16
so simply ignore these specific errors for now.