Since then, it always worked fine, although I honestly don’t remember how it behaved in joy.cpl.
For anyone who doesn’t know, joy.cpl is the old Windows controller settings panel used to configure and test controller input. It was probably already around back in Windows XP.

It’s also one of the quickest ways to check whether a controller is being detected properly.


However, the issue with the controller layout is still there, because it apparently still isn’t being detected as an actual controller.

Originally posted by @R+5:

never had that issue with mine.

before that began to happen, were you changing settings somewhere (maybe your desktop configuration for the controller)? maybe you changed something and forgot about it until you began to notice the issue.

Nope, hadn't had to change controls for anything for a while.

never had that issue with mine.

before that began to happen, were you changing settings somewhere (maybe your desktop configuration for the controller)? maybe you changed something and forgot about it until you began to notice the issue.

with which games you often had issues with the controller?

----------------

tldr

i have been using the 2015 controller for almost a decade, and the only had two issues related to steam input:

first one, to use it i needed to use it through steam client, so i needed to launch steam to use it.


the only issues with sc-controller were related to few bugs of the program when running, rather than input. i think i never found a game that "refused to work" with steam controller.

This isn't a big deal, but I am using Godot (the steam version) and there is some weirdness with trying to setup the controller layout for this app.
See, when it opens, it has like a launcher ( a view projects page) - Then, when you select a project, the project page closes, and that project opens.
Finally, while using Godot, you can "run the game" you've made, which opens up another Window ( at this point the app has two open windows, the editor and the game)
TBH, it would be AMAZING if Steam saw this window (the game) and applied the controller layout to that.
However, it doesn't and I have no idea how I could get it to see it.


So instead, I've setup a desktop config that is pure gamepad. I can bind the left joystick & right joystick to "Joystick" style, but for some reason, "Joystick" is no longer an option for the left pad. I am specifically trying to test out ideas like, each pad controls it's own "cursor." Since I can't actually setup & test with both pad set to joystick, the only way forward is to use the left stick as one, which generally makes testing "different" than it would be if I exported the game.

I guess I am just griping here, but maybe there is a solution I am not seeing, that would help me with my issues when using Godot.
Thanks

Originally posted by @R+5:

for the casual reader, erratas:

most of the things op lists here as issues or problems, are actually misunderstandings (or worse case actual lies), depending if and how much op actually cared to read and or watch videos about how to take advantage of the controller menu, in either or both the original big picture mode, or the most recent version of the menu, which has a few limitations, but still offers most of the features and options of the original menu (which imo was nicer, and better documented, but slow).

no man, there are no missunderstandings, i was prasing the Steam controller (2015), for its easy setup and configuration, never had a problem with the "SC2015" or the steam api (it was called "SCAPI" back in the day).

for the casual reader, erratas:

most of the things op lists here as issues or problems, are actually misunderstandings (or worse case actual lies), depending if and how much op actually cared to read and or watch videos about how to take advantage of the controller menu, in either or both the original big picture mode, or the most recent version of the menu, which has a few limitations, but still offers most of the features and options of the original menu (which imo was nicer, and better documented, but slow).

the gyro works independently of changing the settings that changes the name of the buttons according to the nintendo style (where the ABXY buttons are); the gyro in most cases, needs to be set and configured manually to take advantage of it. its assumed those who buy the controller are aware they will invest time reading documentation and or following guides to learn of the features, or from direct trial when exploring the controller menu.

Originally posted by type2A:

And then I went into Steam settings - Controller and let it install the "Xbox Extended Feature Support Driver" and reboot my PC. Now the guide-view / start-select behavior in gw2 is correct as before, I don't get stuck in Mouse mode.
One added note is that when they try to look at the actual guide button chords, they get an empty window saying Steam Input is not enabled on this controller, and clicking enable does nothing. That despite that any game's controller config shows Steam Input working and configurable as normal.

Originally posted by Zisa_asiZ:

i can not configure the old one anymore, unless I want to download dubious old client files.

Not sure downloading old client files still works, but for most features, "steam controller v1 (2015)" still works really well, and you can still configure most settings. i still use mine, with very few issues*

*a issue with the middle click with the stick, becomes sometimes it becomes stuck; and an occasional issue that happens if the controller is accidentally disconnected while playing, or a memory issue forces a game to disconnect the controller (may have something to do with the driver, and how steam reconnects the controller), which is not a big issue, as long as the controller isnt physically disconnected or a game isnt running out of memory.

so buying a new steam controller v1 is still a good option, imo.

Originally posted by Zisa_asiZ:

no deluxe menus and all that.

i agree it would be better if valve also offered the option of a classic style menu, more visual, but only if it is as fast as the new one. i also liked that the original controller settings menu had better documentation and examples of what could be done with different settings.

something like "freezing" and skipping a frame?

ive been using my controller for probably close to 5+ years (probably closer to 10), and i dont think i have experience something like that. the only times ive seen the controller acting "a bit weird" was often unrelated to the controller, but something else going on with the os or steam client. most of the time, i played in linux (a bit in a ubuntu variant, then manjaro, then nobara os).


I was toying with switching to Linux but I don't think that is going to fix my issue.