Proton: Among Us (945360)

[Baguettedood]

Compatibility Report

• Name of the game with compatibility issues: Among Us
• Steam AppID of the game: 945360
  
  
  

  Click for System information

System Information

• GPU: RX 580
• Driver/LLVM version: Mesa 20.1.7 / LLVM 10.0.1
• Kernel version: 5.8.5-tkg-pds
• Link to full system information report as Gist
• Proton version: 5.0-9

steam-945360.log
Player.log

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Common Issues

Issue 1: Keyboard input sometimes fails to work

workaround/solution: Use GloriousEggroll's proton-ge-custom, avoid alt+tabbing or switching focus while the game starts up.

For those running the itch.io version via regular Wine: Try using wine-staging or another version of Wine with the rawinput patches. Lutris also supports running non-Steam Wine games with Proton.

I'm personally unable to replicate this as of Proton 5.13 but others seem to still have the issue.

Click for outdated details

Older Solution: Use Proton 5.13. Others still seem to experience this issue with Proton 5.13 however. Results may vary.

Game works mostly fine when in mouse-only mode, but keyboard input very rarely works. Seems to happen consistently on Proton 5.0 but harder to replicate on 4.11 (may need more confirmation on whether or not this is just a fluke), but I so far haven't been able to replicate it at all on Proton-5.9-GE-6-ST as suggested here. Other Proton versions with wine-staging's rawinput patches might also resolve the issue.

Workaround: Consider using GloriousEggroll's proton-ge-custom, avoid alt+tabbing or switching focus while the game starts up.

Reproduction

1. Launch Among Us with Proton 5.0
2. Open Settings
3. Set "Controls" in the "General" section to "Mouse+Keyboard"
4. Launch a freeplay game on any map
5. Keyboard input may or may not work here
6. Alt+tab out of the game and back in
7. Keyboard input definitely shouldn't work here.

Alternative reproduction method: Launch the game, alt+tab a bunch until it starts up, and the keyboard input might stop working. Switching workspaces instead of alt+tabbing can also trigger it.

The Player.log in the game's AppData directory suggests the keyboard problems stems from Wine/Proton's interaction with Unity's new Raw Input system (RI.Hid):

(Filename:  Line: 731)

<RI.Hid> Failed to start reading input report:
Access denied.

(Filename:  Line: 731)

<RI.Hid> Failed to start reading input report:
Access denied.

(Filename:  Line: 731)

<RI.Hid> Failed to start reading input report:
Access denied.

(Filename:  Line: 731)

<RI.Hid> Failed to start reading input report:
Access denied.

(Filename:  Line: 731)

<RI.Hid> Failed to start reading input report:
Access denied.

(Filename:  Line: 731)

<RI.Hid> Failed to start reading input report:
Access denied.

Might become an issue as newer Unity games start using this input system.

Issue 2: "Game doesn't launch after clicking play!" / "It says 'preparing to launch' for 30 seconds but then doesn't open!"

You probably are lacking Vulkan drivers for your system. You can use OpenGL instead of Vulkan (at a performance cost) by setting your launch options to PROTON_USE_WINED3D=1 %command%.

Click for details

If you think your GPU should support Vulkan, check that you actually have Vulkan drivers installed. Search for instructions on how to install Vulkan for your distro + GPU.

If, for some reason, you want to forcibly reproduce this issue on your system that has working Vulkan, you can set your launch options to VK_ICD_FILENAMES="" %command%. Only do this if you want your game to crash.

Ultimately this symptom isn't actually an issue with Wine/Proton but rather a hardware/driver issue, but I've posted it here since it's fairly common.

Issue 3: Unable to type using non-English keyboard layouts

Still being researched, look to the comments for newer information. I'm using a US keyboard so I can't be much help here.

Additional Issues (If you're having problems, read these too):

1. If you're having trouble connecting to online games, the servers are probably overloaded. Select another server with the globe button in the game's "Online" menu, or try again later. Some seem to have luck switching to another server and then back (e.g. North America -> EU -> North America again).
2. Errors such as InitializeEngineGraphics failed or Make sure you have DirectX 11 installed probably means you are lacking Vulkan drivers for your system, or your GPU doesn't support Vulkan. Set your launch options to PROTON_USE_WINED3D=1 %command% to use OpenGL instead. If this still doesn't work, your hardware might be too old. Among us Will not open in OpenGL mode if your hardware doesn't support OpenGL 3.2 or higher (i.e. your PC/graphics card needs to be made after 2010).

If you have your own issues, comment them below. Include as much system information about your hardware/software/drivers as you can, and reproduction steps if possible.

[Orangestar12]

I found other Proton versions do not have this issue, only Proton 5.0 does. For the moment, you can try downgrading to 4.11.

[Baguettedood]

Seems like input works more consistently on 4.11. I was able to break it immediately after downgrading but not on subsequent restarts of the game. Updated the main post with this, thanks.

[kisak-valve]

Hello @Baguettedood, if you run the game with Proton 4.11, then switch back to Proton 5.0 without manually altering the wine prefix, does that have an effect on the keyboard input snafu you're seeing?

[Baguettedood]

After going back to Proton 5.0 it's remained roughly as frequent as using it on 4.11. Seems to happen more often if the game isn't in focus while it starts up, but even then is still unreliable.

[StarrKiss]

Currently, I cannot connect to the server- the game launches and runs, but I can't join or host a game since the latest update that added 6 character codes. No error message, it just has the connecting animation forever.

[Baguettedood]

Currently, I cannot connect to the server- the game launches and runs, but I can't join or host a game since the latest update that added 6 character codes. No error message, it just has the connecting animation forever.

@StarrKiss Can you see if the solution found here fixes it?

1. Go to ~/.local/share/Steam/steamapps/compatdata/945360/pfx/drive_c/users/steamuser/AppData/LocalLow/Innersloth/Among Us/
2. Delete serverInfo2.dat

[StarrKiss]

I've tried that @Baguettedood but no such file exists.

[Baguettedood]

I can't seem to replicate the keyboard issue when using GloriousEggroll's Proton-5.9-GE-6-ST as suggested here. Proton-GE and maybe other builds of Proton that include wine-staging's rawinput patches (such as proton-tkg) may solve the keyboard input problems.

[Adikso]

I found this blog post: https://churchman.nl/2019/03/14/granting-capabilities-using-capsh/
And executed commands:

export -p > ./savedenv
sudo capsh --caps="cap_net_raw+eip cap_setpcap,cap_setuid,cap_setgid+ep" --keep=1 --user=$USER --addamb=cap_net_raw -- -c "source ./savedenv; rm ./savedenv; steam"

It will run steam from which you can run Among Us with working multiplayer features. It seems like mentioned ICMP ping is a problem here.

[thebozzcl]

@Adikso 's post seems to have worked for me... though I'm not sure exactly what his command is doing.

[kisak-valve]

Among Us (945360)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4223.
@naoliv posted on 2020-09-28T02:09:56:

Whitelist Request

• Name of the game to be whitelisted: Among Us
• Steam AppID of the game: 945360

Maybe asking for whitelist is too strong here, but consider this as a positive feedback, saying that I was able to properly run the game with Proton.

System Information

• GPU: Intel HD Graphics 3000
• Driver/LLVM version: 3.0 Mesa 20.1.8
• Kernel version: 5.8.10
• Link to full system information report as Gist: https://gist.github.com/naoliv/dd213f2c3de50ab1c3878378f2b95ffb
• Proton version: 5.0-9

Since the GPU doesn't support Vulkan, the game was called with PROTON_USE_WINED3D=1 %command%

I confirm:

• [X] that pressing the Play button in the Steam client is sufficient.
• [X] that runtime config options are necessary to run the game.
• [X] that no workarounds other than PROTON_* env variables are necessary.

Issues

• [X] I haven't experienced any issues.
• [ ] There are no issues left open for this game.
• [ ] Although I consider the gaming experience equal to Windows there are remaining issues:

[baryluk]

@Adikso 's post seems to have worked for me... though I'm not sure exactly what his command is doing.

The command from Adisko grants you temporarily (in a local shell for a duration of its existence only) additional privileges (without granting full root permissions) to send and receive ICMP packets, thus making wine be able to implement ping / ICMP functionality. It is a decent solution. This is what cap_net_raw+eip part does. The pcap part is packet capture (like network analyzer, like wireshark or tcpdump is using pcap), not sure why it is needed, but maybe it is for local discovery of servers, or something, it shouldn't be needed for ICMP I think. Similary I don't think cap_setuid is needed.

I tried to give wine-preloader executable file the these permissions (using setcap), but then there are some issues with dynamic linker. So I think capsh solution from Adisko is more reliable.

@Adisko is the cap_setuid really nacassary? That seems a bit dangerous.

Update. It appears pcap and setuid are needed.

Here is simplified command:

sudo --preserve-env capsh --caps="cap_net_raw+eip cap_setpcap+ep cap_setuid,cap_setgid+ep" --keep=1 --user=$USER  -- -c "/usr/bin/env steam"

[kisak-valve]

Among Us russian input does not work

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4246.
@lenwtet posted on 2020-10-08T18:32:56:

Compatibility Report

• Name of the game with compatibility issues: Among Us
• Steam AppID of the game: 945360

System Information

• Proton version: 5.0

I confirm:

• [*] that I haven't found an existing compatibility report for this game.
• [*] that I have checked whether there are updates for my system available.

Symptoms

Russian input does not work in proton. I tried to launch with options > LC_ALL=ru_RU.UTF-8 %command% < but nothing has happened. If I run this game on wine via > LC_ALL=ru_RU.UTF-8 wine "Among Us.exe" < It's works fine.

[Baguettedood]

@lenwtet That would run with your system-installed wine, probably newer with different fixes compared to Proton. What version of wine have you installed to your system?

In addition, have you tried launching Among Us via a version of GloriousEggroll's proton-ge-custom?

[alcnode]

@Baguettedood I have installed wine version 5.18. proton-ge-custom did not help

[Baguettedood]

@lenwtet Tell me more about your system. What graphics card/drivers/etc. The information that the compatibility reports ask for when creating a new issue.

When you say "does not work" do you mean it doesn't open at all, or that the game opens fine but you can't move your character/some other issue?

[Baguettedood]

I see a lot of people on ProtonDB mentioning disabling esync as a fix (PROTON_NO_ESYNC=1), always coupled with using wined3d (PROTON_USE_WINED3D=1). Does disabling esync actually help people play the game when not paired with using wined3d or is it just placebo? (i.e Is there a case where he game doesn't load without changing the setting, but does if changing only this setting?) Esync/Fsync/Neither all work on my machine.

[naoliv]

With Proton 5.13-1 it's still working without any issues here.
With 5.13-1 I was also able to run another game which I had no success with 5.0-9 (#4222)
Maybe people who had issues could give a try with the new Proton version?

[Baguettedood]

The keyboard issue does seem fixed with Proton 5.13. As far as I'm now aware, there should be no more symptoms directly stemming from Proton, but players may still experience issues depending on configuration/hardware/actual game bugs.

[DestyNova]

I was able to run it and join a public game with 5.13, but only with the PROTON_USE_WINED3D=1 option, which has the side effect of making all on-screen players the same colour, so it's sadly unplayable, at least with the Nouveau driver. I couldn't get it to work with the NVidia proprietary driver at all.

[ChrisMondok]

I still have no keyboard input on Proton 5.13-1 (or 5.0-9). Keyboard input works for me on 4.11-13. I have not set any custom launch options.

Steam System Information

[Baguettedood]

I can't replicate the keyboard input issue anymore but I'll include the GloriousEggroll solution for those who still have troubles.

[gquittet]

I can't use accents with Proton 5.13 and the US international keyboard.
I'm using PopOS 20.10 by the way.

[KairanD]

I can't use accents with Proton 5.13 and the US international keyboard.
I'm using PopOS 20.10 by the way.

@gquittet Hello! I'm dealing with this issue in all multiplayer games running with Proton, since I switched from Windows 10 to Ubuntu. However, I'm using keyboards with the Portuguese ABNT2 layout (with dedicated keys for accents). This can be extremelly annoying and also a critical issue in games like Among Us when you're trying to type in languages like Portuguese, Spanish or French.

XIM is disabled by default in the registry, so you can try enabling it, as shown in https://github.com/ValveSoftware/Proton/issues/3791#issuecomment-670811393. You can also try setting the locale manually, as shown in https://github.com/ValveSoftware/Proton/issues/3528#issuecomment-716204617.

This seems to fix the issue (according to Debian and Slackware users). However, I've tried it in different versions of Ubuntu and it doesn't work. I'm still trying to figure out why. PopOS is based on Ubuntu, so let's see how it goes.

EDIT: GOT IT WORKING! With a fresh install of Ubuntu 20.10. The problem was my system. Now I can confirm that the solution above works. In my case, it wasn't necessary to run with LC_ALL=pt_BR.UTF-8 LANG=pt_BR.UTF-8 %command%.

[brauliobo]

The keyboard issue does seem fixed with Proton 5.13. As far as I'm now aware, there should be no more symptoms directly stemming from Proton, but players may still experience issues depending on configuration/hardware/actual game bugs.

5.13 doesn't work at all here, see https://github.com/ValveSoftware/steam-runtime/issues/290

[haroldm]

Controls does not take into account keyboard layout switch:

• Keyboard layout used for controls will always be starting keyboard layout
• Keyboard layout used for chat is correctly taken into account when switching

Tested with Proton 5.13

[adoloran]

Hi. I'm using proton 4.11.13 (because 5 for among us doesn't work). I have my AZERTY turn into a qwerty US (langage also fr/eng) but when I want to play with the qwerty on, AZERTY is always on for the game and the keyboard don't let me play with qsdz but with award. I don't know if I'm clean but I write in qwerty in the game but keyboard play with AZERTY at the same time. Can you help me ? I'm on a Ubuntu 18

[haroldm]

@adoloran Try to switch keyboard layout before starting the game. It seems to be a generic problem with Proton.

[adoloran]

@haroldm hi thanks for your answer. But it doesn't seem to work either :(

[saboya]

Game does not lauch for me with Proton >=5.0. 4.11 works fine.

[Baguettedood]

@saboya Might be because newer Proton versions require newer drivers (specifically because of newer DXVK versions). What is your graphics driver version?

[saboya]

@Baguettedood Mesa 20.2.2 with 5.9 kernel. Ryzem 3700U / Vega 10.

[Baguettedood]

@saboya I dunno then. Maybe looking through the logs generated by PROTON_LOG=1 could help figure it out, but if what you have works fine then no real need to worry about it.

[saboya]

@Baguettedood Just found out why:

https://github.com/flathub/com.valvesoftware.Steam/issues/642

There's a flatpak-compatible 5.13 Proton alternative there that runs against flatpak environment.

[Baguettedood]

@saboya So Proton 5.0 works fine, you're just having trouble with Proton 5.13?

[saboya]

@Baguettedood Yeah, I just tested here, and 5.0 does work, my bad.