HydraheadHunter
commented
8 months ago Up until this point, I've been running Minecraft through Steam as a non-steam game and using steam as the thirdparty interface for the controller's control settings (the way the controller was designed to be used). But, microsoft apparently changed the launcher from an .exe to a uwp game (whatever that means) sometime in the last four years since I set everything up on my old computer, and Steam's failing to launch the controller settings for the game now.
Figured I try a mod to see if it'd work. Alas it does not, for now.
isXander
Controller name The discontinued Steam Controller of ancient times that I cling to desperately because it's the only controller I've found that doesn't hurt my hands to use for more than an hour at a time.
Issue Controlify does not detect the controller through the steam controller's wireless adaptor, which is by itself fine (unsupported is unsupported), but attempting to circumnavigate the problem by plugging it into the computer using a wired usb connection the game to crash, generating this crash report: crash-2024-02-04_15.07.48-client.txt
Attempting to relaunch the game with the controller plugged in didn't immediately crash the game, but the controlify didnt recognize the controller, and unplugging it and plugging it back in caused a crash that generating no new crash report and just spit out exit code -805306369, which Mojang of Microsoft say is most often caused by the game running out of memory.
Was running a fresh install of minecraft 1.20.4 through a fresh fabric loader with just Controlify and the listed dependancies installed; OS is windows 11; java version is up to date.