And I repeat: there was
no change whatsoever in the joystick code or anything even remotely related between this week and last week's releases. Plus, the joystick code for 1.26.17 is
exactly the same as for 1.26.16.
This is not a viewer bug and the log you attached shows that the joystick code is properly initialized:
Check your driver configuration, or your anti-virus, and verify that they are not blocking the new viewer binary...