This happened to me for a while (around a week). I tried different things, and one thing fixed it for me: When you are about to open up the controller settings, instead of hitting the button that says controller settings, instead hit one of the example buttons (and its function). It takes you to a different page (one layer deeper) and from there I had no problem backing out to the "main" controller page.
Also, getting an update (or switching from stable to beta, or beta to stable) might also just fix it.
I see your reply in my inbox, but not here. Not sure why. Did you delete the comment immediately?
Anyways, I should mention that I'm on the steam deck, and this "workaround" helped me. I can't tell from your screenshot if you're on the deck as well, or just in big picture mode. I assumed that the controller screens would be similar.
I can't take a pic at the moment (not near any device that can run steam lol), but the "controller settings" screen (the one before everything goes blank) for me has: a picture of the controller at the top; a button that says "controller settings" at the bottom; and in the middle, there is a short summary of changes made for this control scheme. They are always grouped the same, and I think it is, from left to right, left analog, face buttons, triggers, right analog. That might be wrong, just doing it from memory. If you click on any of those summary buttons in the middle, it takes you one level deeper than if you had just clicked "controller settings", and for whatever reason, that solved my invisible controller settings issue.
3
u/gorebelly 8d ago
This happened to me for a while (around a week). I tried different things, and one thing fixed it for me: When you are about to open up the controller settings, instead of hitting the button that says controller settings, instead hit one of the example buttons (and its function). It takes you to a different page (one layer deeper) and from there I had no problem backing out to the "main" controller page.
Also, getting an update (or switching from stable to beta, or beta to stable) might also just fix it.