search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.49k stars 1.07k forks source link

Assassin's Creed Odyssey (812140) #1757

Open matty-r opened 6 years ago

matty-r commented 6 years ago

Compatibility Report

System Information

I confirm:

Log File

(Too Large to paste here) Log File

Symptoms

Uplay will launch and update, after update Uplay will report "Connection Lost, A ubisoft service is currently unavailable. You can try again later or switch to offline mode". Offline mode will not work as it's required to login atleast once before offline mode is allowed.

Reproduction

Start the Game without any additional launch options.

aeikum commented 5 years ago

gnutls30 is shipped with Steam now, in both production and beta clients. There's no need to be messing around with symlinks, and you should undo any symlinks you made previously.

ananace commented 5 years ago

Ran into one issue when playing, where if my Steam controller turns off at any point during play then gamepad input stops working (But KB+M bindings keep functioning), and the only thing that seems to restore it is a complete restart of the game.

Vash63 commented 5 years ago

I'm able to load into the game without issue after setting the virtual desktop size in winecfg, but random cutscenes are missing dialogue or have dialogue in the wrong places. Unfortunately it seems to largely be the ones more important to the story, which makes it fairly serious from a playability standpoint if you care about the story. Also I can rule this out as an audio bug as the subtitles are missing or misplaced in these scenes as well, but the animations (including lips) move as if they were supposed to be speaking.

I've tested this on Proton 4.2-9 and a custom build of 4.12.1

Vash63 commented 5 years ago

Having the same issue with fsync, so it seems the cutscene bug is happening with either fsync or esync. I've uploaded my game saves below, unfortunately the file write dates don't match the times displayed in game so I'm not sure which one is the correct one to duplicate this, but if you put these in your "Program Files (x86)\Ubisoft\Ubisoft Game Launcher" directory and in game load the oldest save dated 21 July, just run up the hill and start the cutscene. With either fsync or esync on my Ryzen system the cutscene plays out of order, including camera pans, so it is not an issue with just audio. Disabling both fsync and esync resolves the issue.

savegames.zip

jomarocas commented 5 years ago

hi this log is from proton 4.11.1 and is when i try to execute a perfomance test this crash

jomarocas commented 5 years ago

hi this log is from proton 4.11.1 and is when i try to make a secundary mission later of talk to blacksmith https://gist.github.com/jomarocas/b873d217c63df9b1f77821ebac73ee47

Vash63 commented 5 years ago

Correction on my earlier statement - I got the out of order cutscene playback once even with esync/fsync disabled... so it seems to be somewhat random and maybe some race condition or timing issue. It does seem to happen more frequently with esync/fsync on though.

Vash63 commented 5 years ago

Testing on Proton 4.11-3, performance is still really good with fsync/esync but either of them I still have random missing or repeated dialogue in cutscenes. It isn't very common but it happens on important enough cutscenes that if you care about the story you still need to disable both fsync and esync.

Edit: 4.11-3 did fix my controller issues though, my DS4 now works with no tweaking needed, before I had to launch into Big Picture every time before it would be picked up.

FloBEAUG commented 5 years ago

Hi everyone, After the 1.5.0 update of AC Odyssey and in the same time, update 4.11-3 of Proton, the game doesn't want to start anymore (in fact I think Uplay doesn't launch)... Do you have any idea please ?

I tried to downgrade to Proton 4.2-9 but it's the same.

Thanks.

Here are the logfiles : steam-812140.log

Vash63 commented 5 years ago

Hi everyone, After the 1.5.0 update of AC Odyssey and in the same time, update 4.11-3 of Proton, the game doesn't want to start anymore (in fact I think Uplay doesn't launch)... Do you have any idea please ?

I tried to downgrade to Proton 4.2-9 but it's the same.

Thanks.

Here are the logfiles : steam-812140.log

You may want to delete your Proton bottle and start fresh (basically reinstall the game). Launchers like Uplay and especially Origin like to break themselves in wine and require fresh installs from time to time. May want to backup your saves just in case the cloud backups weren't working first, but the location will be steamapps/compatdata/812140/

FloBEAUG commented 5 years ago

You may want to delete your Proton bottle and start fresh (basically reinstall the game). Launchers like Uplay and especially Origin like to break themselves in wine and require fresh installs from time to time. May want to backup your saves just in case the cloud backups weren't working first, but the location will be steamapps/compatdata/812140/

I reinstalled everything and it doesn't work... I managed to launch Uplay in command line under the right WINEPREFIX (I used the "run" script generated by proton debugging option under /tmp) but I still can't launch the game.

DorfGit commented 5 years ago

Hi everyone, After the 1.5.0 update of AC Odyssey and in the same time, update 4.11-3 of Proton, the game doesn't want to start anymore (in fact I think Uplay doesn't launch)... Do you have any idea please ?

I tried to downgrade to Proton 4.2-9 but it's the same.

Thanks.

I used protontricks (via 'protontricks gui') to reinstall uPlay, and it launched normally again. Seems uPlay now breaks when you switch between Proton versions.

FloBEAUG commented 5 years ago

I used protontricks (via 'protontricks gui') to reinstall uPlay, and it launched normally again. Seems uPlay now breaks when you switch between Proton versions.

I just tried to reinstall Uplay with protontricks --gui. At the end of the installation, Uplay launches, but when I want to start the game with steam nothing happens (it shows "game launched" during 5 seconds and it disappears).

The game is purchased via Steam, is there a way to launch it directly via Uplay ? (now when I click "Play" in Uplay nothing happens neither)...

FloBEAUG commented 5 years ago

I Think I'm not the only one in that case : https://www.protondb.com/app/812140

FloBEAUG commented 5 years ago

Some update :

I can run the game on my laptop. It's not playable due to the low frame rate but the game launches... What I don't understand, is that I have the same software version on both my computers :

OS : Linux Mint 19.1 Kernel : 4.15.0-58-generic Nvidia Driver : 430.14 Steam : 1560817063 Proton : 4.11-3 ASOdyssey : 1.5.0

Hardware is not the same : Laptop Intel i7-4700HQ Nvidia GeForce 840M

Desktop AMD Ryzen 5 3600 Nvidia GeForce RTX2080

I even tried to copy all .local/share/Steam folder from my laptop to my desktop computer but still the same thing. I'm starting to think that I'm missing some libraries.

Is there a dependency list for games to run properly ?

adojck commented 5 years ago

There is strange GPU usage pattern with this game:

gpu-usage-odyssey

In game FPS all the time jumps from 10 to 60. I have tried two Proton versions:

My system: OS: Arch Linux Kernel: x86_64 Linux 5.2.11-arch1-1-ARCH NVIDIA Driver: 435.21 Steam Built: Aug 30 2019, at 18:54:19 (Steam Beta)

Bought this game for my Arch machine. Sad I can't play it as I don't have Windows... But as Proton is developing at such rate, I will not ask for a refund, I'm pretty sure in near future this game will be playable! :+1:

FloBEAUG commented 5 years ago

Finally discovered the solution !

Some update :

I can run the game on my laptop. It's not playable due to the low frame rate but the game launches... What I don't understand, is that I have the same software version on both my computers :

OS : Linux Mint 19.1 Kernel : 4.15.0-58-generic Nvidia Driver : 430.14 Steam : 1560817063 Proton : 4.11-3 ASOdyssey : 1.5.0

Hardware is not the same : Laptop Intel i7-4700HQ Nvidia GeForce 840M

Desktop AMD Ryzen 5 3600 Nvidia GeForce RTX2080

I even tried to copy all .local/share/Steam folder from my laptop to my desktop computer but still the same thing. I'm starting to think that I'm missing some libraries.

Is there a dependency list for games to run properly ?

It was related with the Ryzen 3xxx UMIP #2927 Addind clearcpuid=514 in the grub boot options did the trick. Kernel Update + Proton Update + ASO Update = a big mess to search where the problem really is.

Beyonderforce commented 5 years ago

Game literally stopped working for me since 4.11-3 I think. I'm using an Acer Nitro 5, Intel® Core™ i5-8300H CPU @ 2.30GHz × 8, GeForce GTX 1050/PCIe/SSE2, 16gb RAM.

Any workarounds? Using Nvidia 435.21

kisak-valve commented 5 years ago

Assassin's Creed Odyssey (812140) broken since 4.11-7 (can't find Uplay installation)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3148. @donutloop posted on 2019-10-13T11:56:53:

i updated from 4.11-6 to 4.11-7 since then this game isn't playable anymore because it can't anymore detect the Uplay installation on the machine. Everything worked on 4.11-6 without issues.

Selection_001

Compatibility Report

System Information

``` Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz CPU Family: 0x6 CPU Model: 0x9e CPU Stepping: 0xc CPU Type: 0x0 Speed: 5000 Mhz 16 logical processors 8 physical processors HyperThreading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 18.04.3 LTS (64 bit) Kernel Name: Linux Kernel Version: 4.15.0-65-generic X Server Vendor: The X.Org Foundation X Server Release: 11906000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20190711.3 Video Card: Driver: NVIDIA Corporation GeForce RTX 2080 Ti/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 415.27 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 120 Hz VendorID: 0x10de DeviceID: 0x1e07 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 1920 x 1080 Primary Display Size: 20.94" x 11.97" (24.09" diag) 53.2cm x 30.4cm (61.2cm diag) Primary Bus: PCI Express 16x Primary VRAM: 11264 MB Supported MSAA Modes: 2x 4x 8x 16x Sound card: Audio device: Realtek ALC1220 Memory: RAM: 32098 Mb Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 467922 Mb Largest Free Hard Disk Block: 37278 Mb VR Headset: None detected ```

Proton version

Vash63 commented 5 years ago

I've been playing Odyssey without issues on 4.11-7. You might have a broken wine prefix, I'd try removing your prefix and letting Proton reinstall Uplay.

Vash63 commented 5 years ago

Nvidia 435.27.07 fixed the last of my graphical issues with this game, it's now 100% compatible for me outside of Uplay screwing up sometimes and needing to be reinstalled (which hasn't happened for a while).

ShalokShalom commented 4 years ago

Hi there :)

So, I confirm this issue with the borders on my up-to-date rolling KaOS with current versions of Linux, mesa and so on.

Screenshot_20191216_162706

It seems like this is an unresolved issue that happens for a lot of people and I also confirm, that by default my resolution was set to an absolute minimum, probably because by the driver is officially not supported, so a fallback.

I am wondering if this black border issue is also related to it. Like some fallback. 1920x1200, so 19:10 is selected in the game settings.

I am ready to provide any information that is helpful to solve this issue.

My specs: AMD Radeon RX 480 Graphics (POLARIS10 DRM 3.33.0 5.3.8-1 LLVM 8.0.1) v: 4.5 Mesa 19.2.7

Thanks a lot

@kisak-valve :hugs:

Vash63 commented 4 years ago

Status update since it's been a while. Currently game works fine with Proton 5.0+ but requires the following changes:

  1. Cutscene logic breaking with missing dialogue and scripted sequences. FIX: Disable both esync and fsync via user_settings.py (using variables in launch options seems to still leave one of the two enabled, as confirmed via logs).
  2. Incorrect aspect ratio / letterboxing issues in fullscreen FIX 1: Use the wine virtual desktop via winecfg OR FIX 2: Compile proton/wine with the following patch: https://github.com/Tk-Glitch/PKGBUILDS/blob/master/community-patches/wine-tkg-git/0001-Add-some-semi-stubs-in-user32.mypatch
  3. Caves not lit properly and graphical artifacts on the wave patterns near shores (nvidia only). FIX: Use Nvidia 440 driver or higher
  4. Uplay breaks and the game says it is not detected (usually when trying to run the game with a different Proton release than it was originally installed with). FIX: Remove the proton bottle and let Steam recreate it.
ShalokShalom commented 4 years ago

Thanks a lot, you solved all the glaring issues at once, great work :smiley:

FIX: Disable both esync and fsync via user_settings.py (using variables in launch options seems to still leave one of the two enabled, as confirmed via logs).

Is this considered an own issue report worth and which directory stores the user_settings.py?

Thanks

Vash63 commented 4 years ago

Thanks a lot, you solved all the glaring issues at once, great work 😃

FIX: Disable both esync and fsync via user_settings.py (using variables in launch options seems to still leave one of the two enabled, as confirmed via logs).

Is this considered an own issue report worth and which directory stores the user_settings.py?

Thanks

Thanks. I'm not sure if that's a Proton issue or an issue with Steam not allowing multiple variables at once in the launch options. If it does deserve its own report it should probably go in the steam-for-linux not proton tracker. I would imagine you could also set the variables when launching Steam to bypass that.

The file is in each Proton install's root directory, usually ~/.steam/root/compatibilitytools.d/$PROTONVERSIONHERE/user_settings.py

One other note with the Nvidia driver I was specifically testing with 440.48.02 - I tried one of the 'stable' 440 releases and the water mist broke again so you may want to try that driver specifically.

ptkato commented 4 years ago 
1. Cutscene logic breaking with missing dialogue and scripted sequences.
   FIX: Disable both esync and fsync via user_settings.py (using variables in launch options seems to still leave one of the two enabled, as confirmed via logs).

I disabled both esync and fsync via user_settings.py, and while most of the time it works ok, some cutscenes still breaks.

The game also often crashes when I open the steam overlay.

andersnylander commented 4 years ago 
3. Caves not lit properly and graphical artifacts on the wave patterns near shores (nvidia only).
   FIX: Use Nvidia 440 driver or higher

No, the cave issue affects AMD (radv) also. Pretty much all caves are either missing ambient lighting completely (forcing you to rely solely on already existing torches or raise the brightness setting a lot, and in particular areas will display artifacted, grid-patterned lighting instead. grid-lighting-aco

kisak-valve commented 4 years ago

Hello @andersnylander, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. ~Also, are you using RADV/LLVM or RADV/ACO with the game?~ RADV/LLVM from the DXVK info in the screenshot.

andersnylander commented 4 years ago

Hello @andersnylander, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. ~Also, are you using RADV/LLVM or RADV/ACO with the game?~ RADV/LLVM from the DXVK info in the screenshot.

Hello, my system information can be found here: https://gist.github.com/andersnylander/2e67db1f77178ebd987a9a1cff9cbf4a

As for LLVM vs ACO, as you could tell from the screenshot, it's LLVM. Should I look into using ACO for this title?

kisak-valve commented 4 years ago

It should be fairly painless to test with RADV/ACO on your system by adding RADV_PERFTEST=aco %command% to the game's launch options. It would also be interesting to know if mesa 20.0.x + llvm 10.0.0 is equally affected, but that'll be more hassle to try.

andersnylander commented 4 years ago

It should be fairly painless to test with RADV/ACO on your system by adding RADV_PERFTEST=aco %command% to the game's launch options. It would also be interesting to know if mesa 20.0.x + llvm 10.0.0 is equally affected, but that'll be more hassle to try.

I can confirm that when using ACO things look notably different. I don't know if it's accurate, but it certainly feels like it should be a lot closer to what the developers intended. screenshot_2020-03-26-175150 I tried it with Mesa 20 as well (using mesa-aco-git 20.0.0.20200226.7a965bd4c38-1) and it looked fine there also, but not when specifically selecting LLVM.

Haven't tried it with LLVM10 as the backend, but it seems ACO is the way to go for this title for now.

hakzsam commented 4 years ago

@andersnylander Would be nice if you can test with LLVM 10. LLVM 9.0.1 is known to have some problems..

andersnylander commented 4 years ago

@andersnylander Would be nice if you can test with LLVM 10. LLVM 9.0.1 is known to have some problems..

I did make an attempt at building llvm-git from AUR yesterday for the purpose of testing this. No dice, the build failed on me. LLVM10 was officially released 3 days ago, but the package in Arch's official repo has at the time of writing this not been updated yet. I do intend on testing this again once it's available from Arch's official repo.

Update: It appears the issue is still present with LLVM 10. I had to build the toolchain from scratch before I could use it to build mesa-git. I don't know if this could influence the result I'm seeing, as I had to disable the Arch-specific patch applied to LLVM 9 to get it building (link).

One thing I noticed now that I didn't notice when I began playing this game, is that this incorrect ambient lighting shader affects all of the games' visuals, but also has a gameplay impact in caves and during nighttime when there's not enough light sources in the environment, making the RADV/LLVM combination very hard to recommend for this title.

jomarocas commented 4 years ago

goo day for all

i recently play he oddysey, in protondb appear this game working good, and i play origins for more than 50 hours in steam and all good, but this game cannot pass of the checking content message, i add the virtual desktop for graphic, and i have all latest nvidia drivers, i attach my log i have proton 5.0.6 steam-812140.log

roennowmads commented 4 years ago

I have the same situation as jomarocas. Origins works just fine, but I have been trying make Odyssey work for days. Also Proton 5.0.6, nvidia drivers. Log: steam-812140.zip . Edit: Game now works after updating from Pop OS 19.10 to 20.04.

jomarocas commented 4 years ago

I have problems, still with screen, and checking content crash, with proton 5.0.7 i have ubuntu 20.04 ryzen 5 2600 and nvidia gtx 970 with 440 steam-812140.log

jomarocas commented 4 years ago

I have the same situation as jomarocas. Origins works just fine, but I have been trying make Odyssey work for days. Also Proton 5.0.6, nvidia drivers. Log: steam-812140.zip . Edit: Game now works after updating from Pop OS 19.10 to 20.04.

hey i only verify data, and working, because need to download data

RipleyTom commented 4 years ago

Caves are still nearly pitch black with Nvidia 440.82(latest as of now) and proton 5.0-7 here and I sadly can't go back as older Nvidia drivers aren't compatible with kernel >=5.6.

Vash63 commented 4 years ago

Caves are still nearly pitch black with Nvidia 440.82(latest as of now) and proton 5.0-7 here and I sadly can't go back as older Nvidia drivers aren't compatible with kernel >=5.6.

I'm not sure if the fixes have made it to their stable branch yet, however I can confirm that the very latest developer drivers (440.66.12) still work, which have their most recent Vulkan code. The fixes should make their way to the stable branch at some point.

haraldkrischner commented 4 years ago

I can confirm dark caves.

I played the game for dozens of hours with well lit caves. At some point my gtx 1060 suffered a lightning damage, I got it replaced by a 2060 super. I am not sure at which point it broke, perhaps I changed the used Proton version, a Nvidia driver updated… but I cannot get it back to work. Whilst outside the lighting is fine, caves are unplayably dark… I tried updating the the driver from 440.64 to 440.82, reverting the driver to 435.21, used Proton-5.6-GE-2, 5.0-9. It won't start with 4.11-13 I start it with launch option PROTON_NO_ESYNC=1

Vash63 commented 4 years ago

I can confirm dark caves.

I played the game for dozens of hours with well lit caves. At some point my gtx 1060 suffered a lightning damage, I got it replaced by a 2060 super. I am not sure at which point it broke, perhaps I changed the used Proton version, a Nvidia driver updated… but I cannot get it back to work. Whilst outside the lighting is fine, caves are unplayably dark… I tried updating the the driver from 440.64 to 440.82, reverting the driver to 435.21, used Proton-5.6-GE-2, 5.0-9. It won't start with 4.11-13 I start it with launch option PROTON_NO_ESYNC=1

I've stated multiple times in this thread that this issue was already fixed. You need the Vulkan developer drivers. I have tested this on 440.66.15 now and confirmed there are still no regressions. Nvidia has not updated the stable branch in a few months, it does not have the required fixes. There is no use testing or reporting feedback on stable branch updates until a new branch comes out (445 or 450+).

haraldkrischner commented 4 years ago

I've stated multiple times in this thread that this issue was already fixed. You need the Vulkan developer drivers. I have tested this on 440.66.15 now and confirmed there are still no regressions. Nvidia has not updated the stable branch in a few months, it does not have the required fixes. There is no use testing or reporting feedback on stable branch updates until a new branch comes out (445 or 450+).

Thank you for clarification @Vash63, I read your comment above FIX: Use Nvidia 440 driver or higher and thought it should be fixed in 440. That said I still don't get why it worked before and I cannot roll it back to a working setup. Anyway, I'll have to wait, thanks

RipleyTom commented 4 years ago

Just to confirm that black caves are fixed with new nvidia drivers 450.51(not sure about 440.100). I played the game quite a bit and as far as issues I noticed it still has: -It seems to only render on part of the screen somehow by default(requires settings a virtual desktop to desired size in winecfg for proper rendering). -It seems to skip some dialog lines during in-engine cinematics(as in silence instead of the voice line). This is with PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1, without those I think it used to actually play wrong sound samples(ie as a voice line from a different dialogue).

Vash63 commented 4 years ago

Just to confirm that black caves are fixed with new nvidia drivers 450.51(not sure about 440.100). I played the game quite a bit and as far as issues I noticed it still has: -It seems to only render on part of the screen somehow by default(requires settings a virtual desktop to desired size in winecfg for proper rendering). -It seems to skip some dialog lines during in-engine cinematics(as in silence instead of the voice line). This is with PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1, without those I think it used to actually play wrong sound samples(ie as a voice line from a different dialogue).

With the second issue, did you confirm in your logs that you don't see "fsync: up and running" or "esync: up and running" in them? I have difficulty setting the two variables in Steam, it seems only one of them makes it through to the environment Proton runs in, so I have to use the user_settings.py file if I want to disable both at the same time.

RipleyTom commented 4 years ago

I just did a grep on proton log and both are correctly registered(grep on log showed Options: {'forcelgadd', 'nofsync', 'noesync'} and no other mention of sync).

kisak-valve commented 4 years ago

AC Odyssey doesn't work in full-screen mode.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4065. @Dimitrov1295 posted on 2020-07-13T21:34:29:

Compatibility Report

System Information

I confirm:

steam-812140.log

Symptoms

This is what the game looks like when I start it in fullscreen: https://prnt.sc/th6469 It doesn't look like that when I run it in borderless mode.

Reproduction

It does it 99% of the time I launch it. Screenshot from 2020-07-13 22-01-55

jomarocas commented 4 years ago

please @Dimitrov1295 read i find before post any new github, exist information in https://www.protondb.com/app/812140 or simple do this

first launch of uplay for driver support, erase folder compatdata and first time launch disable all messages from uplay, first launch of the game disable steam key with ctrl+alt+tab, later you can make this

WINEPREFIX=(Steam-folder)/steamapps/compatdata/812140/pfx/ winecf

Later enable virtual desktop and you put you monitor resolution, later edit with gedit in my case the following file

gedit (Steam-folder)/steamapps/compatdata/812140/pfx/drive_c/users/steamuser/My Documents/Assassin's Creed Odyssey/ACOdyssey.ini

FullscreenWidth=1920 FullscreenHeight=1080

mnn commented 4 years ago

After Steam update yesterday game stopped working. It shows an error message and closes.

Unable to detect Uplay installation. Please make sure Uplay is installed.

2020-07-18_10-46

I configured the game originally as described in this protondb post:

2020-07-18_10-45

I tried verifying local files and Steam reported everything is ok.

Any advice or tip would be appreciated, I would like to finish the game.

Edit: It's working again now, after few Steam restarts and weird behaviour where I could launch Uplay, but after trying to launch the game, the game instantly closed.

artemyto commented 4 years ago

Here is a fix for black bars issue: https://github.com/GloriousEggroll/proton-ge-custom/commit/87080f2f89977430720a1adfdc26d22e0575068b

I hope we will see this issue solved in the next proton-ge release.

artemyto commented 4 years ago

Proton 5.9-GE-5ST fixed the black bars issue! https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.9-GE-5-ST