isXander / isXander/Controlify

[Controller Request] <Steam Controller>

Open
#238 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting 2.0 check controller-compat
Dominant language
Java
Stars
341
Forks
97
Avg merge
1h
Merged PRs (30d)
1

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked crash report and reproduce the wired Steam Controller behavior on Minecraft 1.20.4 with Fabric, Controlify, and its listed dependencies on Windows 11. Compare launch and reconnect behavior; done means the controller no longer crashes the game and its wired support status is established.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.