Open fewtarius opened 3 months ago
This is happening in the current client on SteamOS as well. I noticed it in the beta client branch, and switched back to the stable client because I primarily play docked and would like to have working screenshots. But then beta got promoted to stable and now that behavior is back.
It's possible that this is an intended change, because if you hold the PS button on a DualShock 4 and wait for the shortcut reference to pop up, PS+R2 is now the documented screenshot shortcut.
This is happening in the current client on SteamOS as well. I noticed it in the beta client branch, and switched back to the stable client because I primarily play docked and would like to have working screenshots. But then beta got promoted to stable and now that behavior is back.
It's possible that this is an intended change, because if you hold the PS button on a DualShock 4 and wait for the shortcut reference to pop up, PS+R2 is now the documented screenshot shortcut.
That does seem to be the case now, perhaps you're right in that it may be desired behavior.
Your system information
Please describe your issue in as much detail as possible:
Hello! I work on a variant of SteamOS called SteamFork and I noticed after updating the client today that screenshots no longer work using Steam Button + RB when using external controllers. I verified using my OLED deck, where Steam Button + RB works fine using the decks controls. I then tested using an SN30 Pro on my Steam Deck and was not able to take a screenshot using Steam + RB. I also tested in SteamFork and verified the incorrect behavior on an AYN Loki Max, an Ayaneo 2S, and an Ayaneo Flip KB using both built-in controls and the SN30 Pro.
When I tested the Ayaneo 2S, I intentionally tested taking a screenshot before updating the client using Steam + RB and that worked fine, and then again after the update in which it failed.
I did notice that after the update I am able to take a screenshot using Steam Button + Right Trigger on every device, including the OLED Steam Deck using an SN30 Pro. That was not the case before updating.
Steps for reproducing this issue: