https://bikeshed.com/ Whether the button is a 2,3 or 4-state toggle is irrelevant. From a user perspective, GTK3Vice-3.5 is malfunctioning, and users would simply submit duplicate "works-for-me" bug reports without the above information. Also, the bug was introduced between Winvice-3.2 and GTK3Vice-3.5, and is not an issue with other C64 emulators because they can be set to read only one button (e.g. Hoxs64, BixHawk, etc.).
Pressing that button adjusts how the gamepad works, changing from Profile 0, Profile 1, Profile 2, Profile 3, which can have different rules for sensitivity and deadzones. But more importantly, the average user would not be able to figure out that the profile button is causing the issue, and would be unable to use the gamepad (or think that Vice is malfunctioning, since other emulators act normally.)
It's a toggle, and Microsoft didn't expect any game to use a raw button number that high.
Joystick button continuously pressed
Necromancer soul printing stray number
I found this config to be a bit better, provided you do fullscreen borderless (the current config places the window off-center, thus you get infinite spin). The only quirk is the ESC menu gets placed at the top-left corner. The only remaining problem is that it seizes the cursor when you alt-tab to other windows. It's like I need to use "Keep cursor fixed" when it's in the background (or otherwise block background input handling).
I found this config to be a bit better, provided you do fullscreen borderless. The only quirk is the ESC menu gets placed at the top-left corner. The only remaining problem is that it seizes the cursor when you alt-tab to other windows. It's like I need to use "Keep cursor fixed" when it's in the background (or otherwise block background input handling).
That would be the 1541 demo disk, with "Printer test". In that program, WinVice-3.1 and the latest svn either segault, or have some driver component fail. There's also various tests in the printer manual as well. While those test are helpful, at least one of the problems wouldn't be detected unless one used a real-world application.