LEGO City Undercover
Works perfect. No issues, no fixes, no workarounds
What distro, if you don't mind me asking? For me, it doesn't launch on SteamOS (steamos beta + steam beta) with Proton 3.16-4 but works well with 3.7 (albeit the background sound is always on max volume with no means to change it). I switched to 3.16 in hope it would fix the sound issue but instead it stopped working altogether.
From the linked System Information: Ubuntu 18.04.1 LTS (64 bits)
@kisak-valve
Whitelist Request
- LEGO City Undercover
- 578330
System Information
- GPU: RX 570
- Driver/LLVM version: Mesa 18.3 & LLVM 7
- Distro: Sabayon
- Link to full system information report as Gist
- Proton version: 3.16-5
I confirm:
- [✔] that pressing the
Playbutton in the Steam client is sufficient.
Issues
- [✔] I haven't experienced any issues.
- [✔] There are no issues left open for this game.
All audio issues are now fixed! :+1:
I can confirm that with Proton 3.16-5 the game runs perfect on SteamOS and all sound issues are gone. :-)
System Information
- GPU: GTX 970
- Driver/LLVM version: 396.54
- Distro version: SteamOS 2.166
- Proton version: 3.16-5
̶f̶̶r̶̶o̶̶m̶̶ ̶̶a̶̶ ̶̶c̶̶e̶̶r̶̶t̶̶a̶̶i̶̶n̶̶ ̶̶m̶̶i̶̶s̶̶s̶̶i̶̶o̶̶n̶̶,̶̶ ̶̶i̶̶t̶̶ ̶̶a̶̶l̶̶w̶̶a̶̶y̶̶s̶̶ ̶̶c̶̶r̶̶a̶̶s̶̶h̶̶e̶̶s̶̶,̶̶ ̶̶p̶̶r̶̶e̶̶v̶̶e̶̶n̶̶t̶̶i̶̶n̶̶g̶̶ ̶̶m̶̶e̶̶ ̶̶t̶̶o̶̶ ̶̶c̶̶o̶̶n̶̶t̶̶i̶̶n̶̶u̶̶i̶̶n̶̶g̶̶ ̶̶t̶̶h̶̶e̶̶ ̶̶g̶̶a̶̶m̶̶e̶̶.̶
̶e̶̶d̶̶i̶̶t̶̶:̶̶ ̶̶i̶̶s̶̶ ̶̶r̶̶e̶̶l̶̶e̶̶a̶̶t̶̶e̶̶d̶̶ ̶̶t̶̶o̶̶ ̶̶d̶̶x̶̶v̶̶k̶̶ ̶̶t̶̶u̶̶r̶̶n̶̶ ̶̶i̶̶t̶̶ ̶̶o̶̶f̶̶f̶̶ ̶̶f̶̶o̶̶r̶̶ ̶̶t̶̶h̶̶i̶̶s̶̶ ̶̶o̶̶n̶̶e̶̶ ̶̶m̶̶i̶̶s̶̶s̶̶i̶̶o̶̶n̶̶ ̶̶w̶̶i̶̶t̶̶h̶̶ ̶̶p̶̶r̶̶o̶̶t̶̶o̶̶n̶̶_̶̶u̶̶s̶̶e̶̶_̶̶w̶̶i̶̶n̶̶e̶̶d̶̶3̶̶d̶=̶1̶̶ ̶%̶c̶̶o̶̶m̶̶m̶̶a̶̶n̶̶d̶%
from a certain mission, it always crashes, preventing me to continuing the game.
We 100%'ed the game on SteamOS so it certainly is possible. Try different proton flags as well as different resolutions (this one might require manually editing the game's config), the crashes occur on Windows too, so it might not even be fixable in Proton. There are lots of topics mentioning possible solutions: https://steamcommunity.com/app/578330/discussions/search/?q=crash&gidforum=135512931358081225&include_deleted=1
from a certain mission, it always crashes, preventing me to continuing the game.
We 100%'ed the game on SteamOS so it certainly is possible. Try different proton flags as well as different resolutions (this one might require manually editing the game's config), the crashes occur on Windows too, so it might not even be fixable in Proton. There are lots of topics mentioning possible solutions: https://steamcommunity.com/app/578330/discussions/search/?q=crash&gidforum=135512931358081225&include_deleted=1
Okkay after a new installation of my distro everything works again :D
I wanted to add that the game works with ESYNC, but crashes on cutscenes with FSYNC on my machine.
DXVK and D3D both work, but DXVK is much faster.
Hello @nariox, can you also add a note to #2922 with your findings.
Yes, @kisak-valve. I have added the info on the issue tracker yesterday, but didn't have time to reply here. Let me know if any other information is desired (traces, debug log, etc).
With a default install of a steamdeck I've experienced that game progress isn't saved. We need to restart from the beginning every time.
It's fixed now... update I guess?
System Information
- GPU: AMD AMD Radeon 780M Graphics (integrated)
- Video driver version: Mesa 25.1.4-arch1.1
- Kernel version: 6.15.3-arch1-1
- Link to full system information report as Gist: https://gist.github.com/rinsuki/2d7216bac764b5417c594dcf73dcab6d
The OP movie is glitched in Proton 9.0-4, Proton 10-1 (beta), and Proton Hotfix, but works fine in Proton 8.0-5 and/or Experimental.
Hello @rinsuki, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, can you grab a screenshot of the misrendering or elaborate on the nature of the glitch you're seeing?
@rinsuki Thank you for the regression report! It turns out this is already fixed in upstream dxvk which is why it was working in experimental. It is still great for us to know when things are regressed on a stable release - thank you!
LEGO City Undercover uses single controller input for both players
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9387.
@TitanNano posted on 2026-01-10T21:01:43:
Compatibility Report
- Name of the game with compatibility issues: LEGO City Undercover
- Steam AppID of the game: 578330
System Information
- GPU: RTX 5060
- Video driver version: NVIDIA 580.119.02
- Kernel version: 6.17.12
- Link to full system information report as Gist: https://gist.github.com/TitanNano/2f5506b1dc6aaf7b964d78b7c565ab98
- Proton version: 10.0-3
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.
Symptoms
When launched through Steam Big Picture Mode, the game recognized the single connected Steam controller as input for both players.
- This issue did not exist before Proton 10. (i.e., Proton 9 works fine)
- This issue does not occur when launching the game through the regular desktop mode of Steam.
Reproduction
- start big picture mode
- Start LEGO City Undercover
- Load a save game or start a new one.
- In the game world, press any of the controller buttons. (Moving the analog stick does not trigger the issue.)
- The second player gets enabled.
- Both players are controlled by the same controller.
@TitanNano what controller are you using and how are you connecting it to your computer? (bluetooth/usb)
@simifor I'm using one of the original Steam controllers.
EDIT: The controller is wirelessly connected via the USB dongle.
Proton versions
proton 8.0-5x1 2025-06proton 9.0-4x1 2025-06proton hotfixx1 2025-06proton 3.16-5x1 2018-12proton 3.16-4x1 2018-11
Launch options
PROTON_LOG=1x1 2025-06
Upstream links
- ValveSoftware/Proton/issues/9387x1 2026-01
Whitelist Request
System Information
I confirm:
Playbutton in the Steam client is sufficient.Issues