We recently updated all our projects to patch out the recent big exploit. In doing so, we noticed that none of our newer builds are able to carry items by holding a button on the steamdeck. To be clear, this button is supposed to mimic mouse press.
This problem only appears on steamdecks for our windows builds being emulated on there. We reverted the editor to test to 6000.0.44f1 and found the issue was not present on those builds. We are in the process of testing a number of older input system packages to see if anything can be learned from those.
Hi, I’m also affected by this issue. Would love to hear if you have any progress on this.
Reverting to input system 1.14.0 did not work. Neither did updating to version 1.15.0
For now, we will be building on 44f1 again and using the binary patcher to fix the exploit.
Having similar issues. I know another developer who said they are getting mouse drag/drop issues on Proton/Steam Deck after updating to Unity 6000.0.58f2 where IsPressed seems to get reset when you start moving the mouse.
I just decided to upgrade from 6000.0.51f1 to 6000.0.60f1 and confirmed I am getting that same issue now. I tried unsuccessfully to find anything relevant in the InputSystem version change from 1.4.0 to 1.4.2, so I suspect it is a deeper issue.
I can’t figure out any workaround, so for now I think I need to roll back to Unity 6000.0.51f1 and use the binary patcher as part of my build process until this issue is fixed.
Hello there!
I’ve tried to take a look into our backlog and confirmed bugs regarding this issue and it appears to be not reported yet.
Considering that the user “Skoddle” noted that the issue reproduces on 60f1 also, it’s a 100% confirmation that the issue is not caused by the CVE Fix.
So if possible, please report this issue via the Unity Editor Bug Reporter Tool and make sure to provide the following information:
- Minimal (If possible) Project where the issue could be manually tested
- Exact reproduction steps:
1. Open Project
2. Build and Run
3. Do “This” action in the Player
4. Observe “Result”
For additional information regarding bug reports you can refer to this page:
Edit: Wanted to follow up regarding what “BaptisteCyberneticWalrus” said. Currently the best option is to do as they mentioned, downgrade to a known working version (For example using the one that was previously used for your projects) and using the Patcher on the built players.
Hi there,
My colleague has posted a bug report for the issue earlier. We got in touch with our Unity rep to also confirm and report this issue. I can only assume its being processed in the background at this time.
We have also observed this issue after upgrading. Including reports from players running Proton on Linux with Mouse and Keyboard (ie, not on a Steamdeck).
We went from 6000.0.49f1 to 6000.0.58f2
The input package went from 1.14.0 to 1.14.2
It seems like this issue was introduced sometime between 6000.0.52f1 and 6000.0.58f2. It might not have been introduced in 58f2, but 58f2 is the minimum version I am forced to update to for the security fix. For now I have reverted back to 51f1 and applying the security fix manually.
Since I don’t have a linux development machine (I encounter this issue on Steam Deck after deploying a build), I am not able to easily create and test a ‘minimal project’. So a big thankyou to BaptisteCyberneticWalrus and your colleague for posting a bug report!
Hi GediminasR,
The case number for our report is CASE IN-121283, in case you want to look into it and link it to this forum thread.
And as a general warning, reverting back to 44f1 corrupted our HDRP package, but a library reimport ended up straightening that out. be careful when downgrading kids!
Hey BaptisteCyberneticWalrus
Yep found the ticket in our reports list, I’ll ping a colleague with a Steam Deck or a Linux machine at the least, hopefully they’ll be able to take a look.
anthony_sloth - huh that kinda tracks, I mean Steam Deck OS is Linux based, then it just means the issue is specific to Linux machines/OS’es
Skoddle - your finding really helps, now we won’t need to test from 0f1 up to 58f2 to find the regression point 
so thank you for that
P.S: If anyone else encounters this issue, make sure to downgrade to a working version where you don’t encounter the issue and use the Patcher instead!
Currently suffering from this issue on 6.2.10. (For Proton IE Steam Deck builds).
It’s a really bad one, for my game it basically breaks the core UX for steam deck players…
I hope y’all flagged this one as high priority and are working on a fix ASAP.
Lke many people, I went ahead and upgraded to the latest 6.2 version following the security warning.
And now, I’m forced to either wait for this fix in a new 6.2 patch, or revert until this problem is resolved.
Not a great feeling. 
I’m sure that a lot of other devs are affected by this issue as well.
We are still looking into it but it might be on the proton’s side. They actually had a recent fix on that: Into the Dead: Our Darkest Days (2239710) · Issue #9160 · ValveSoftware/Proton · GitHub
Hey all, we have some news. We have confirmed that the new Proton experimental resolves this issue.
Courtesy of our QA tester who wrote this up for us:
- Select [your game] in your library,
- Click on the settings (The cog icon to the right of the “Play” button),
- Click on “Properties”,
- Click on “Compatibility”,
- Select the “Force the use of a specific Steam Play compatibility tool” checkbox,
- Select “Proton Experimental” from the drop down list of options,
- Play [your game] on your Steam Deck!