The five, separated
Grouped because the reports are, not because a shared cause has been established — nobody has shown that any two of these are the same bug. Work out which one you have before trying anything, because none of the advice circulating for one of them addresses the others.
- Wrong button glyphs. Prompts show a different controller’s buttons from the one connected. This is the only one of the five a developer has named as being looked at, and no fix, build number or date has been published.
- Switch Pro Controller face buttons swapped on Layout C. One reporter, no replies, no developer response, and nobody has said whether another layout avoids it.
- DualShock 4 rumble does nothing. One report, no reply, not reproduced by a second player in the thread.
- Button configuration resets to Type B. A saved layout reverting on its own. Same corner of the thread as the DualShock 4 report, and recorded beside it because the reports are adjacent rather than because they share a cause.
- Inputs registering late or not at all. Parries, dodges and heals dropped or delayed — the largest cluster of the five, corroborated by several players, and the only one the developer has demonstrably read: Sam [developer] reposted one report into the pinned megathread.
The last one may not be a controller fault at all
Worth separating from the other four, because it is the one most likely to be misdiagnosed. The dropped-input reports tie the symptom to animation lock — after aiming, skills, Blade Arts and assassinations — and one player’s reading is that healing simply will not start while you are downed, staggered, attacking or being hit. If that is right, some of what is being reported as a controller problem is the combat system refusing input by design, and no amount of rebinding or replugging will change it. Nothing published settles which it is, and the two would need separating before either could be fixed. It is filed under controllers here because that is what people call it when they search.
What actually works right now
Nothing, and that is the honest state rather than a gap in this page. No workaround has been posted for any of the five. Nobody has reported a settings change, a frame-rate cap, a launch option or a driver version that affects any of them. The developer has acknowledged one — the glyphs — and published nothing a player can do in the meantime. If you find something that works, the tracker page has a report form and this page will carry it.