Cyberpunk 2077 (1091500)

[julienbenjamin]

NOTE FROM PROTON TEAM: The game will not currently run stably on NVIDIA, we don't advise to attempt to run it; if you do, please do NOT report additional issues about this known problem. Please see this comment for more details about current status and known issues.

Compatibility Report

• Name of the game with compatibility issues: Cyberpunk 2077
• Steam AppID of the game: 1091500

System Information

• GPU: RTX 2070 Super
• Driver/LLVM version: 450.80.02
• Kernel version: 5.9.0-4-amd64
• Link to full system information report as Gist:
• Proton version: Proton 5.13-4

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

Avatar's face does not render.

Reproduction

1. Click on "Play" on the Steam client
2. Run the game via the CDPR launcher without account
3. Start a new game
4. When avatar is displayed, his/her face is not rendered. Same in-game.

steam-1091500.log

Screenshots

[Niedzwiedzw]

just tried running on manjaro linux + proton 5.0, my gfx card is 1080 (not TI)
the game does not run, it's just a black box
gonna try on proton 5.13 now

[kisak-valve]

https://github.com/ValveSoftware/Proton/wiki/Changelog#513-4 notes that the game currently needs Proton 5.13-4 or newer and mesa git. That implies that Proton builds older than today will not work and there's more issues to be worked out between the game, vkd3d-proton, and the nVidia proprietary driver. Proton Experimental is recommended, as it contains performance improvements and bug fixes for this game.

---

From @Plagman posted at #4450 (comment):

There's a couple of known sound issues by now:

    No enemy gunshot sounds
    No car radio
    No background NPC dialogue

Audio fix available for testing in Proton e‍xperimental-5.13-shmem-20201214.

---

Proton Experimental experimental-5.13-20201218c known audio quirks:

• Low volume from some audio sources like TVs.
• Audio crackling that can be manipulated with PULSE_LATENCY_MSEC, possibly due to pulseaudio's server being overloaded from mixing 14 audio channels. Configuring pulseaudio to use resample-method = speex-float-1 may speed up the server.
• Spacial sound effects may be missing. Cyberpunk 2077 (1091500) #4450 (comment)
• Can not hear the dialog of some background NPCs. Cyberpunk 2077 (1091500) #4450 (comment)

Audio fix available for testing in Proton e‍xperimental-5.13-20210115. #4450 (comment)

---

NVIDIA proprietary drivers older than 455.xx will have graphics artifacts and all current NVIDIA drivers are generally expected to crash and freeze. The game will not currently run stably on NVIDIA, we don't advise to attempt to run it, and if you do please do not report additional issues about this known problem.

---

Some distros allow you to multi-slot a point release of mesa and mesa git. In that situation, the game can pick up the older version of mesa/radv and have a hard time. Also, AMDVLK (v-2020.Q4.5) and AMDGPU-PRO (20.45) is not expected to work with the game right now. Having them installed might cause the game to fail to start.

---

Updating mesa is not needed or beneficial if you use the nVidia proprietary driver. They are completely unrelated driver stacks.

---

The game might crash on pre-AVX CPUs. Triaged by game update 1.05.

[Niedzwiedzw]

after clicking "sign up" the console shows
2020-12-10 01:38:47.575 [Information][ (0)] [TID 768][red-launcher]: Skipping sending event 'view_focused' because it's disabled (view 'login').
and this happens

not sure if it's linux specific

[Niedzwiedzw]

I managed to succesfully go into the main menu on Proton 5.13.4, redownloading the game now to play in Polish :D

[G-Alevizos]

Any luck with changing the PROTON_HIDE_NVIDIA_GPU env variable?

[ruslang02]

Radeon RX 5600XT, Proton 5.13-4, Manjaro, linux 5.9.12

On 5.21-GE the game has artifacts.

[kisak-valve]

Hello @ruslang02, what version of mesa are you using? Anything older than mesa git from a couple days ago is older than should be used with this game.

[fatino]

With mesa-git 21.0(compiled 1 hour ago) proton 5.13-4 and rx 470:

• after mesa-git steam shows only black pages
• I'm able to start Cyberpunk 2077 launcher through taskbar.
• game starts, shows CD PROJECT RED logo, music plays, then black screens and then it crashes my GPU drivers, because all screens show wierd rainbow lines.
  Log from steam-native(arch linux):
  cyberpunk_2077.log
  Doesn't really look like much, seems like mesa bug.

EDIT: Normal mesa from repo 20.3.4 does exactly the same. At least steam works properly.

[alex9k1]

Just tried the game for a few minutes. Seems to work fine on Arch + Radeon VII. Had to install mesa-git and vulkan-radeon-git. Before that, ingame screen and characters in character creation were all completely black.

Performance could be better tho, but still able to play with 60FPS.

[ben-romer]

I was able to play through for 30 minutes or so, on 5.13-4 Proton, Nvidia driver 455.45.01, Ubuntu 20.04 with kernel 5.4.0-56-generic. I had to drop the settings to low to get a reasonable framerate, but I'm also on a GTX980M so that's not really surprising.

If you're on NVidia and getting a black screen, try dropping the settings some.

[Trezamere]

I was also able to play briefly before I needed to step away, Fedora 33, Proton Experimental

kernel 5.9.12-200.fc33.x86
2070 super driver version: 455.45.01
mesa 20.2.3

framerate was around 30 fps but everything maxed, will report back later with more detail.

Getting crashes after about 30 minutes of play +-. Journal shows the following, someone mentioned might be related to VRAM? Will check.

kernel: NVRM: GPU at PCI:0000:0a:00: GPU-9436b076-8c43-5f1e-da15-4e783ada041b
kernel: NVRM: GPU Board Serial Number: 
kernel: NVRM: Xid (PCI:0000:0a:00): 31, pid=8003, Ch 000000be, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_0 faulted @ 0x1_91c80000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ

[class101]

There I don't have the invisible skin issue, I did not find any issue beside the fact the game does not detect my low end specs and tend to choose the High graphic level, have to tune it to low or so to have a better performance.

I did not installed mesa-git, just all updated from the Arch repo

Steam Client Beta (In Steam > Settings > Account > I choose Steam Beta Update)
Proton 5.13-4

Nvidia 455.45.01-6
extra/mesa 20.3.0-3

OS: Arch Linux x86_64
Kernel: 5.9.13-arch1-1
Uptime: 1 hour, 6 mins
Packages: 1015 (pacman)
Shell: bash 5.1.0
Resolution: 1920x1080
DE: Cinnamon 4.8.2
WM: Mutter (Muffin)
WM Theme: Mojave-dark (Mojave-dark)
Theme: Mojave-dark [GTK2/3]
Icons: McMojave-circle [GTK2/3]
Terminal: guake
CPU: Intel i7-4770K (8) @ 3.900GHz
GPU: NVIDIA GeForce GTX 980
GPU: NVIDIA GeForce GTX 980
Memory: 2538MiB / 15942MiB`

Screenshots

[RookySoap]

I have a GTX 970, Ubuntu 20.10, kernel 5.8.0-31-generic, nVidia driver 450.80.02, Proton 5.13-4. Game crashes on startup, after displaying the CD Projekt Red logo, and goes to a black screen

[lostpolaris]

Bump, running Manjaro Linux, Proton 5.13-4 and latest mesa drivers (5700XT), running into Artifacting crash after launching game from launcher.

[udev]

Getting the following crash log after clicking "play" from the launcher using proton 5.13-4

Registered crash info file...
InternalVersion: 3.0.3214677  P4CL: 4155897  Stream: //R6.Root/R6.Patch0Hotfix2 
!!!CRASHED!!!
Error Reason: Assert
Expression: commonFileLoaded
Message: Failed to load in-game config file from 'Z:\home\steamsteam\debian-installation\steamapps\common\Cyberpunk 2077\r6\config\settings\options.json'
File: e:\r6.patch0hotfix2\dev\src\common\redconfig\src\ingameconfigreader.cpp
Line: 449

"uptimeSeconds":0
"stopThreadID":139
"exceptionCode":0x80000003`
"processID":138
"Engine/CommitFailedErrorCode@1#TID=0":"0"
"Configuration/Name@2#TID=0":"FINAL"
"Configuration/Name2@3#TID=0":"FINAL"
"Game/Patch@7#TID=0":"1.03"
"Engine/OOM@4#TID=0":"false"
"GlobalMode/IsClosing@5#TID=0":"false"
"GlobalMode/IsGame@6#TID=0":"false"
"Jobs/InitParam/MaxLatentJobs@8#TID=0":"131072"
"Jobs/InitParam/MaxCriticalPathJobs@9#TID=0":"65536"
"Jobs/InitParam/MaxImmediateJobs@10#TID=0":"2048"
"Jobs/InitParam/WorkerThreadStackSizeKB@11#TID=0":"1024"
"Jobs/InitParam/MaxThreads@12#TID=0":"27"
"Jobs/InitParam/AllJobsCriticalPath@14#TID=0":"false"
"Jobs/InitParam/UseJobDebugger@13#TID=0":"false"
"Jobs/Dispatcher/NumDispatcherThreads@15#TID=0":"3"
"Jobs/Dispatcher/MaxHWConcurrency@16#TID=0":"4"
"##CrashDump##/DumpCrashDataSeconds":"0" 

Was able to locate an options.json in ~/.steam/debian-installation/steamapps/common/Cyberpunk 2077/r6/config/settings but I'm struggling with where to put it 😅

[fatino]

Journalctl after cdp logo and black screen:

gru 10 02:52:53 greyhill kernel: amdgpu 0000:08:00.0: amdgpu: GPU fault detected: 146 0x0000480c for process Cyberpunk2077.e pid 5602 thread Cyberpunk2:cs0 pid 5643
gru 10 02:52:53 greyhill kernel: amdgpu 0000:08:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
gru 10 02:52:53 greyhill kernel: amdgpu 0000:08:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0604800C
gru 10 02:52:53 greyhill kernel: amdgpu 0000:08:00.0: amdgpu: VM fault (0x0c, vmid 3, pasid 32786) at page 0, read from 'TC4' (0x54433400) (72)
gru 10 02:52:58 greyhill kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
gru 10 02:53:04 greyhill kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
gru 10 02:53:04 greyhill kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
gru 10 02:53:04 greyhill kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=97333, emitted seq=97336
gru 10 02:53:04 greyhill kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Cyberpunk2077.e pid 5602 thread Cyberpunk2:cs0 pid 5643
gru 10 02:53:04 greyhill kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset begin!
gru 10 02:53:08 greyhill kernel: amdgpu 0000:08:00.0: amdgpu: failed to suspend display audio
gru 10 02:53:08 greyhill kernel: amdgpu: cp is busy, skip halt cp
gru 10 02:53:08 greyhill kernel: amdgpu: rlc is busy, skip halt rlc
gru 10 02:53:08 greyhill kernel: amdgpu 0000:08:00.0: amdgpu: GPU BACO reset
gru 10 02:53:09 greyhill kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset succeeded, trying to resume
gru 10 02:53:09 greyhill kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
gru 10 02:53:09 greyhill kernel: [drm] VRAM is lost due to GPU reset!
gru 10 02:53:09 greyhill kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
gru 10 02:53:09 greyhill kernel: amdgpu 0000:08:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.2.1 test failed (-110)
gru 10 02:53:09 greyhill kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
gru 10 02:53:09 greyhill kernel: [drm] UVD and UVD ENC initialized successfully.
gru 10 02:53:09 greyhill kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
gru 10 02:53:09 greyhill kernel: [drm] VCE initialized successfully.
gru 10 02:53:09 greyhill kernel: [drm] recover vram bo from shadow start
gru 10 02:53:09 greyhill kernel: [drm] recover vram bo from shadow done

[iWeaker]

For all NVIDIA Debian / Ubuntu users. the latest NVIDIA drivers are required, 455 as it includes extensions necessary for its correct functionality.

Ubuntu PPA:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install nvidia-driver-455

[crypnull]

Bump, running Manjaro Linux, Proton 5.13-4 and latest mesa drivers (5700XT), running into Artifacting crash after launching game from launcher.

Same problem, same drivers, same card, only difference is I'm on base Arch not Manjaro.

[yoyossef]

I'm stuck on "Preparing to launch..." with my 6800XT and mesa-git, can't even get in-game.

[arBalasquide]

Anyone having audio issues? I get static noise that can be fixed with PULSE_LATENCY_MSEC=60 but I can't hear gunshots, club music nor NPCs talking.

[cabal19421]

Debian Testing
kernel 5.9.0-4-amd64
steam proton 5.13-4
OpenGL ES 3.2 Mesa 20.2.3
LLVM 11.0.0
RX580

• All models are black on the character creation screen
• Game begins with all overlay (text choices, minimap) working but completely black / dark rendering. Everything is mired in black / darkness.

attempted to use proton-experimental, no change.

attempted to use all low video settings, no change.

attempted to use all ultra video settings, no change.

attempted to try different vsync, no change.

Read above someone else had this issue too but they run Arch and grabbed mesa-git and vulkan-radeon-git both of which isn't available on Debian without manual intervention which I don't want to do.

There are two alternative drivers, amdpro and amdvlk that can be used, will report back on results after switching.

[mattlennon3]

I can boot the game and walk around. Some issues are that I can't hear npcs and it shows controller icons only, even though I am using the keyboard to move. 20fps on low graphics settings.
Arch 5.4.81-1-lts
Nvidia 455.45.01 GTX1070
Proton 5.13-4

[TheFynx]

I'm in game and playing, hasn't crashed yet. No invisible/blacked out models issues or artifacting. Though horrible FPS at any graphics setting. About to test in windows for comparison, though I've heard it's just as bad. So probably needs Dev updates.

No launch options

Running Pure Arch Linux

• Proton: 5.13-4
• Kernel: 5.9.13-zen1-1-zen
• CPU: AMD Ryzen 7 3800X 8-Core Processor
• RAM: 32084 Mb
• GPU
  • Driver: NVIDIA Corporation GeForce RTX 2070 SUPER/PCIe/SSE2
  • Driver Version: 4.6.0 NVIDIA 455.45.01
  • OpenGL Version: 4.6
  • Mesa: 20.3.0-3

Settings

• Resolution: 3840x1600
• High: 20 FPS (30 FPS in Windows, 60+ FPS w/ DLSS Quality Windows)
• Medium - 25-30 FPS (35-40 FPS Windows 70+ FPS w/ DLSS Quality Windows)

** Updating with windows comparison for my dual boot just for reference of performance between Windows/Linux-Proton

[McMarius11]

game runs but the performance is extremely bad.

on low 30 - 35 fps
1920x1080

Proton 5.13-14

Distro:Manjaro Linux
Kernel:5.9.12-1-MANJARO
RAM:24 GB
GPU Driver:NVIDIA 455.45.01
GPU:NVIDIA GeForce GTX 1070
CPU:Intel Core i5-7600K @ 3.80GHz

[niculw]

@cabal19421 I see same behavior in pop_os 20.10, running kernel 5.9.10 and proton 5.13-4. Using a 5700xt.

[b10rn]

I cannot hear any NPC conversations. The problems with black textures were solved by installing mesa-git. Performance seems to be good, but I have only played for a few minutes.

Arch Linux
Radeon RX 5700
Proton experimental

[RookySoap]

iWeaker4you's advice works, game runs with the 455 driver. One thing I noticed is that the game freezes for me when my VRAM usage hits 100%, so I just put my textures setting to low

[xioren]

As with others (with nvidia), game runs but poor performance. Audio crackling, adding PULSE_LATENCY_MSEC=40 helped. Missing audio, especially in the club scene (voices + music). Sometimes when I start the game the launcher just shows a black box and does nothing, retrying usually works. I have had several hard freezes that I have to SIGKILL to recover from.

Linux Mint 20
Kernel 5.8.0-31
Nvidia GTX 1070 Driver: 455.38
Intel i7-6700k
16g ram

[sluedecke]

I have audio crackling in crowded scenes and especially when driving a car.

System

• GPU: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile]
• Driver version: 550.67
• Distro: Arch Linux, Kernel 6.8.2-arch2-1
• Audio system: pipewire, pipewire-pulse
• Launcher: Heroic
• Proton: Proton-GE-Proton9-2
• Cyberpunk: 2.12

Symptoms

Unbearable audio crackling when driving a car. Riding a bike is ok-ish and just walking around works fine 99%.

What I tried:

• pw-metadata -n settings 0 clock.force-quantum 50 and various other values
• WINEDLLOVERRIDES="xaudio2_7=n,b"
• PULSE_LATENCY_MSEC=90 and various other values
• Change the wine audio backend from pulse to ALSA with winetricks / protontricks
• Change output type from Analog to Digital
• Setting pipewire default sample rate to 96000 or 48000

Since this is breaking the game experience, I appreciate any pointers / help to get this fixed.

[kodatarule]

Game is also freezing on startup on Fedora Linux for me. Proton Experimental. diagnostics.json steam-1091500.log

Can confirm that with Proton Experimental I also have the freeze on startup, game works fine on Proton 9.0(Beta)

[kisak-valve]

Hello @kodatarule, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the freeze, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

[kodatarule]

Hi Kisak, log has been attached and here is the gist https://gist.github.com/kodatarule/6cf33b60e96a611b6d320d7fe860788d
steam-1091500.log

[Scrashdown]

Hello, for a few days now my game usually freezes or crashes immediately after the splash screen. Sometimes I am able to start playing, but it crashes or freezes within a few seconds. Sometimes it freezes with a black screen at startup, but I can still hear the game's sounds.

Proton log: https://kdrive.infomaniak.com/app/share/356870/076002fe-483b-4e6f-8282-355985dfbe0e (it is 100 MB so I could not attach it here on Github)

Steam info: https://gist.github.com/Scrashdown/ea766bd5512baaf3fb7ca74b7e081165

I've tried Proton 9, Proton Experimental. I've also tried reverting to the current LTS kernel.

Command: PROTON_LOG=1 gamemoderun mangohud %command%

EDIT:

I changed the command to PROTON_LOG=1 %command% --launcher-skip --intro-skip and the game doesn't even start now. However the log file becomes much shorter:
steam-1091500.log

[kisak-valve]

Hello @Scrashdown, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and see how the game behaves. (6.6.30 does not count as older in this case.)

[Scrashdown]

Hello @Scrashdown, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and see how the game behaves. (6.6.30 does not count as older in this case.)

Thanks for letting me know about this bug. With kernel 6.1.90-lts, the game starts and I am able to play for a while. However I still get a crash after a few minutes, though I suspect this is more of a thermal (my CPU reaches 82 C) or power supply issue (might be a bit underpowered).

[Kron4ek]

Hi everyone. On my system with a 32-thread CPU (Ryzen 7945 HX) the game performance is relatively poor, it gives me around 50 FPS on any graphics settings, even on the lowest, and both CPU and GPU are severely underloaded.

I found out that overriding CPU topology to 16 threads via WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 doubled the performance, now i get around 100 FPS and the GPU is almost fully utilised now. Hope this helps someone.

[shmerl]

I didn't need it with Ryzen 9 7950X, but that also depends on your SMT settings in the game. It should be set to auto.

[Kron4ek]

@shmerl Thanks, this SMT setting in the game was enabled and was causing a massive performance hit. Disabling it or setting it to auto improves the performance same way as overriding CPU topology on my system.

[netfab]

Let's talk about cyberpunk on the steam deck.

Current version of Cyberpunk (version 2.12) is affected by a bug that makes massive audio crackling
with ugly distortions when fighting/driving or even during cutscenes dialogs. Sometimes it even
induces some fps drops. You can find dozens of topics about this issue everywhere.
Affected systems: Windows, XBox, Linux, SteamOS. I do not know if developers will ever fix this,
but this bug is making the game impossible to play.

I tried a lot of « fixs », found here and there, nothing worked.
Until I found a topic that suggests to unplug every gamepad/controller from the system.

But, how to do it on the steam deck ? You will need a deck docking station to play cyberpunk
in desktop mode with keyboard/mouse.

1. connect your steam deck on the docking station with keyboard/mouse
2. switch to desktop mode
3. open a Konsole, and set a password to the steamdeck user by running :

$ passwd

4. open your ~/.bashrc with an editor
5. append the following bash function at the bottom of your ~/.bashrc :

toggle-steam-controller() {
	local -r USBHIDDIR='/sys/bus/usb/drivers/usbhid'
	for x in 0 1 2; do
		# device path here is from steam deck OLED, may vary depending on your system
		local USBDEVICE="3-3:1.${x}"
		local ACTION='bind'
		if [ -L "${USBHIDDIR}/${USBDEVICE}" ]; then
			ACTION='unbind'
		fi
		local my_command='echo "'${USBDEVICE}'" > '${USBHIDDIR}'/'${ACTION}
		#printf "$my_command\n"
		sudo bash -c "${my_command}"
	done
	printf "${ACTION}ing steam controller done\n"
}

6. reboot and switch to desktop mode again (or run: $ source .bashrc)
7. in desktop mode, open a Konsole, and run :

$ toggle-steam-controller

Output :

$ toggle-steam-controller
[sudo] password for deck:
unbinding steam controller done

Output of kernel's dmesg :

[ 606.645498] hid-steam 0003:28DE:1205.0003: Steam Controller 'FYZZ35000C7B' disconnected

You can now play cyberpunk. No more sound crackling/distortions. That's magical.

8. Once you played cyberpunk, if you want to re-enable the steam controller, run again :

$ toggle-steam-controller

Output :

$ toggle-steam-controller
[sudo] password for deck:
binding steam controller done

Output of kernel's dmesg :

[ 707.130102] hid-steam 0003:28DE:1205.000C: Steam Controller 'FYZZ35000C7B' connected

I know that's not a proton/steam/deck bug, but every linux user may come here when
dealing with this problem while trying to play cyberpunk.

[alasky17]

@kodatarule Are you still seeing a freeze on experimental? If so, could you get a new log?

[kisak-valve]

No audio whatsoever

Issue transferred from #7965.
@GitBingus posted on 2024-08-05T16:01:06:

Compatibility Report

• Name of the game with compatibility issues: Cyberpunk 2077
• Steam AppID of the game: 1091500

System Information

• GPU: RTX 2060 6GB
• Video driver version: 555.58.02
• Kernel version: 6.8.0-39-generic
• Link to full system information report as Gist:
• Proton version: GE-Proton9-10

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.

steam-13822821710669283328.log

Symptoms

When I launch the game, absolutely no audio is played. I have tried changing the Wine audio backend from Pulse to ALSA and OCC with no change, as well as other audio output devices. I downloaded the game with Heroic Game Launcher on an EXT4 Hard Drive via GOG. I then added the game to Steam so I can use Proton-GE easier. Here are my runtime commands:

gamemoderun mangohud PROTON_LOG=1 PROTON_FORCE_NVAPI=1 WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=60 %command%

When I launch the game, it should play the intro track, but I hear nothing, as well as, well, anything when I actually play the game.

Reproduction

[kakra]

WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=60 %command%

You should not longer use these overrides. And I'd recommend using pipewire instead of pulseaudio which may eliminate audio crackles altogether.

[RubenKelevra]

Replying to #4450 (comment)

Can confirm this.

[fbievan]

Replying to #4450 (comment)

This is happening to me too... with the same GPU

[RubenKelevra]

@fbievan yeah in my case it's not the same GPU but another Intel GPU build-into a Intel CPU.

I can play for a minute or 5 minutes, then it crashes.

[fbievan]

Replying to #4450 (comment)

Is there further debugging to be done here, anyone up to try to solve this very annoying issue.

[RubenKelevra]

My guess is that the log reduces the execution speed so a race condition isn't happening inside the GPU driver.

If this is a wine issue or a GPU driver issue or something in between isn't really clear just from the symptoms.

Have you tried playing Witcher 3 in Dx12 mode? As it's the same engine it may be able to trigger the same bug - it's not running on my weaker hardware in Dx12 mode at any playable speed.

Apart from that, yes you can try this:

https://gitlab.winehq.org/wine/wine/-/wikis/Commands/winedbg

And this, on various log levels, to see if a less verbose log level may still trigger the bug, but also shows the issue:

https://gitlab.winehq.org/wine/wine/-/wikis/Debug-Channels

Apart from that you could try to lower the settings, to get the maximum execution speed of the engine - and maybe still trigger the bug with logging on.

[fbievan]

My guess is that the log reduces the execution speed so a race condition isn't happening inside the GPU driver.

This is probably true

Have you tried playing Witcher 3 in Dx12 mode? As it's the same engine it may be able to trigger the same bug - it's not running on my weaker hardware in Dx12 mode at any playable speed.

If i try and play Witcher 3 In DX12 Mode, it freezes on load
steam-292030.log
This is the log related to that, it does not crash, even or progress upon the black screen after loading with PROTON_LOG, I should note also, that performance is subpar, even with DX11

Apart from that, yes you can try this:

https://gitlab.winehq.org/wine/wine/-/wikis/Commands/winedbg

Using Wine debug, it refuses to crash, this could be a more space efficient way of preventing the crash, without fixing it.

And this, on various log levels, to see if a less verbose log level may still trigger the bug, but also shows the issue:

https://gitlab.winehq.org/wine/wine/-/wikis/Debug-Channels

I'll try these later...

Apart from that you could try to lower the settings, to get the maximum execution speed of the engine - and maybe still trigger the bug with logging on.

This doesn't seem to work.

[fbievan]

after trying again, with gdb with this method.... the issue has completely disappeared, even without any PROTON_LOG, gdb, or anything else....

I cannot further replicate the issue.... even after rebooting

[RubenKelevra]

Great, I should try this solution 😬

[netfab]

For the record, the problem (and the workaround) described in #4450 (comment) are reproducible with Cyberpunk version 2.13.

[SkyLeite]

For the record, the problem (and the workaround) described in #4450 (comment) are reproducible with Cyberpunk version 2.13.

You can also fix the issue by disabling controller vibration in the game's settings.

[netfab]

For the record, the problem (and the workaround) described in #4450 (comment) are reproducible with Cyberpunk version 2.13.

You can also fix the issue by disabling controller vibration in the game's settings.

That's the first thing I tried months ago when I played Cyberpunk for the first time, and, this change nothing.

[SkyLeite]

For the record, the problem (and the workaround) described in #4450 (comment) are reproducible with Cyberpunk version 2.13.

You can also fix the issue by disabling controller vibration in the game's settings.

That's the first thing I tried months ago when I played Cyberpunk for the first time, and, this change nothing.

Interesting. It fixed the issue for me just yesterday.

[kisak-valve]

Steam app 1091500 playing window not shown after using workspace switcher in Ubuntu

Issue transferred from ValveSoftware/steam-for-linux#11288.
@CaptainMorgan12 posted on 2024-09-23T04:12:35:

Environment:
Ubuntu 24.10 beta Ubuntu Oracular Oriole (development branch), Apple Inc. MacPro7,1, Intel® Xeon® W-3223 × 16, AMD Radeon™ 2 x Radeon RX 6800 XT, Custom kernel for the MacPro Linux 6.11.0-1-t2-noble (so the fans work), Wayland 1.36-1, Mutter 47.0-1ubuntu2, mesa-vulkan-drivers 24.3git2409221842.fd11bboibaf~n, Steam Version: 1726604483, Proton 9.0-3, Cyberpunk 2077 (or any other steam game), Display 3840x2160, Fraction Scaling On 150%, Refresh Rate 144Hz (Fixed).

Maybe Related:
#8218

Steps to repeat:

1. launch game with proton compatibility mode cyberpunk 2077 in my case
2. launch option "-fullscreen"
3. observe game launches in fullscreen window
4. use workspace switcher and switch to a workspace to the left or right of the steam app window that is running the game
5. switch back to the steam app window

Observe steam app window shown in workspace switcher, but shows nothing once switched to the steam app window.

Workaround:

1. launch option -windowed
2. launch option -fullscreen and do not switch to another window using workspace switcher

With the smaller windowed steam app window when switching work spaces and then back to the steam app window it does not disappear. However, this is not an ideal window configuration since I would like to play using my entire screen.

System Report:
Steam_System_Report.txt

Runtime Diagnostics:
Steam Runtime Diagnostic.txt

[CaptainMorgan12]

Also in the above bug report the same happens with Proton Experimental and i am pretty sure any other proton version (i sampled few with the same result), i will collect logs as suggested above next.

Runtime diagnostics with logging turned on in launch options:

Steam_Runtime-Diagnostics_with_logging.txt

this includes launching game and switching workspaces, then observing the steam app game window not showing when selecting the workspace. I doesn't appear to actually show much more in the log though regarding the game.

Never mind here is the logfile:
steam-1091500.zip

There are a bunch of display related entries not sure if these are relevant:

Unhandled exception: page fault on read access to 0x70bf8228 in wow64 32-bit code (0x0050c3cf). 1991.985:03e4:040c:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0x6d69e418, paths 0x7df94be0, modes_count 0x6d69e41c, modes 0x7d2ef840, topology_id (nil) semi-stub 1991.986:03e4:0518:warn:vkd3d-proton:vkd3d_native_sync_handle_release: Failed to release semaphore (#12a). 1991.986:03e4:0518:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Failed to increment swapchain semaphore. Did application forget to acquire? 1991.985:03e4:0424:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0x6dddf218, paths 0x1085bcd80, modes_count 0x6dddf21c, modes 0x7ee4f4d0, topology_id (nil) semi-stub 1991.993:03e4:0404:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0x6d29e418, paths 0x7daa1430, modes_count 0x6d29e41c, modes 0x7da4eda0, topology_id (nil) semi-stub 1991.993:03e4:0518:warn:vkd3d-proton:vkd3d_native_sync_handle_release: Failed to release semaphore (#12a). 1991.993:03e4:0518:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Failed to increment swapchain semaphore. Did application forget to acquire? 1991.993:03e4:040c:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0x6d69f218, paths 0x7df94be0, modes_count 0x6d69f21c, modes 0x7d2ef3c0, topology_id (nil) semi-stub