-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Game Report - Cyberpunk 2077 #31
Comments
Thanks for the report. I've added the game to the working games list. futex2 is not supported by wine-wayland, if/unless it is added to the kernel. Otherwise there is little difference with fsync currently and wine-wayland does not support patches outside of mainline wine and fsync/esync. Regarding resolution, proton uses fshack to change resolutions, which wine-wayland does not support. If this game has resolution scaling you can try that as an alternative to changing resolution. |
Hi. I played in borderless window both on wine and wayland to test how the fps behaves on different resolutions. As far as that goes, there's no problems. But it's like there's some bottleneck, because lowering the details doesn't help. On wine and proton it does. Also, on wine and proton the main menu runs at 200+ fps but on wine-wayland it's 60-70 (my monitor is 144hz). |
Fsync (any variety) actually decreases performance in Cyberpunk 2077 from everything I've seen (and experienced). This isn't unheard of, Fsync is incompatible with some games, it hurts performance in some others. |
Game runs fine for the most part. There are some problems with performance though.
Running the game on ultra gives pretty much the same result as normal wine or proton (20-25 fps on 1440p on my rig). However, as you lower the detail or resolution, the fps rises only to about 45 fps. On normal wine/proton I can get 80+ fps on low settings and very small resolution.
There's also one spot that slows the game to single digits fps. On normal wine/proton this spot is also slowing the game, but not THAT much. This might be caused by the lack of futex2 though. New proton has futex2 enabled and some additional cyberpunk specific patches.
The text was updated successfully, but these errors were encountered: