To my knowledge, Steam Input's cloud is not functioning as intended, with what I hope to be an oversight.
Most people who have used Steam Input are under the impression this is how it works:
You create a binding
That binding is local only to your machine unless you specifically tell Steam to upload it to the cloud.
Unfortunately in practice, that's not how it works, and the Deck has brought this issue to light.
ALL of your inputs you have ever created, even if you never saved them, are backed up to steam cloud, they're all stored in your steamapps/common/Steam Controller Configs/userid/config/ They will repopulate themselves on a fresh system, I tested with my deck, I created a binding, did not upload it to steam cloud, wiped the whole deck, and it was still there on next reboot. There is NO way to actually delete a Steam input binding. This even applies to ones you manually uploaded into the cloud and deleted, trust me, they're still there.
The only thing that export as private binding button does is allow you to pick between a few saved ones on the same game, and apply them to other games (Though applying your saved bindings to other games is missing from the deck/BPM 3 ui)
All of this is happening because Steam uses autocloud for the controller bindings directory, which has now caused the issue of being unable to remove our files. Why even give us a save to cloud button if its gonna be saved no matter what we do? I suppose this is requesting an option to let us delete our controller configs.
To my knowledge, Steam Input's cloud is not functioning as intended, with what I hope to be an oversight.
Most people who have used Steam Input are under the impression this is how it works:
You create a binding
That binding is local only to your machine unless you specifically tell Steam to upload it to the cloud.
Unfortunately in practice, that's not how it works, and the Deck has brought this issue to light.
ALL of your inputs you have ever created, even if you never saved them, are backed up to steam cloud, they're all stored in your steamapps/common/Steam Controller Configs/userid/config/ They will repopulate themselves on a fresh system, I tested with my deck, I created a binding, did not upload it to steam cloud, wiped the whole deck, and it was still there on next reboot. There is NO way to actually delete a Steam input binding. This even applies to ones you manually uploaded into the cloud and deleted, trust me, they're still there.
The only thing that export as private binding button does is allow you to pick between a few saved ones on the same game, and apply them to other games (Though applying your saved bindings to other games is missing from the deck/BPM 3 ui)
All of this is happening because Steam uses autocloud for the controller bindings directory, which has now caused the issue of being unable to remove our files. Why even give us a save to cloud button if its gonna be saved no matter what we do? I suppose this is requesting an option to let us delete our controller configs.