We do often include affiliate links to earn us some pennies. See more here.

Update: a fix for this is now available in Proton Experimental, so switch to that for now.


Curiously, it seems Proton 7 and Proton Experimental are having problems with Unity games recently but there's a possible temporary workaround for you. This is the same across Linux desktop and Steam Deck, as it's a problem somewhere with Proton.

Recently, while trying to capture footage from the Steam Deck for the GamingOnLinux YouTube channel I came up against a problem. Certain Unity games wouldn't load, and instead would present me with a Unity error screen with a loading bar and then just quit. There was a bug report open from others also seeing a similar issue. Proton 6.3-8 would work but for some games, that had other issues that Proton 7 solved.

After some fiddling, I eventually found out that unplugging my Logitech Wireless Receiver suddenly made the games work. I tested this repeatedly, and yup — simply having that plugged in caused the problem. Even if a game is fully loaded and working, simply plugging it in would cause an instant crash. Others on the bug report have now confirmed it too, and it seems even some wired USB devices (from other vendors) are also seeing the same problem.

For now, switching to Proton 6.3-8 or unplugging devices will get Unity games to work again on Linux and Steam Deck. If you need a quick guide to swap Proton versions on Steam Deck, here's how to do it:

YouTube Thumbnail
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Accept Cookies & Show   Direct Link
Article taken from GamingOnLinux.com.
16 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
8 comments

Pikolo Mar 31, 2022
I wonder if that's a Wine regression, or something Proton changed
mindedie Mar 31, 2022
Quoting: PikoloI wonder if that's a Wine regression, or something Proton changed

Or Unity engine (or some 3rd party middleware) going where it should not be and crashing because wine/proton do not take this in a count. Could be totally not malicious bug or just innocent sniffing around...
Mohandevir Mar 31, 2022
I wasn't hallucinating when I posted the issues I witnessed with Proton 7.0-1, some time ago, in another post. Is it a problem about how Proton 7.0-1 handles inputs from usb devices?


Last edited by Mohandevir on 31 March 2022 at 12:38 pm UTC
rcrit Mar 31, 2022
View PC info
  • Supporter Plus
Wine 7.0 changed the joystick/gamepad input to use USB HID so it may be a bug related to that. Wine 6 used a different mechanism for joystick/gamepad support.
CanadianBlueBeer Mar 31, 2022
Well, unplugging is a no go. Keyboard, headset, webcam all USB.

latest GEproton works though.

(got that one trying to get Planet Crafter working)
fagnerln Mar 31, 2022
Funnily using proton was always a workaround to me because native games doesn't recognize my x360 controller and nowadays they don't have sound on my fedora 35 (maybe pipewire bug?).

I played two unity games yesterday and both ran ok
Liam Dawe Mar 31, 2022
A fix for this is now being tested.
Liam Dawe Mar 31, 2022
Update: a fix for this is now available in Proton Experimental, so switch to that for now.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.