protonscr

The Surge

protonopen appid 378540Whitelist RequestRegression
ValveSoftware/Proton#410 · opened 2018-08-24 by Dakunier · updated 2022-02-25 · 20 comments · github · game page · search this game
1 matching comments, n / p to jump
DDakunier 2018-08-24 github

Start and Opening Video play just fine, but if it comes to Ingame i see only this.picture
Log: steam-378540.log
Systeminfo: click

Ccjwijtmans 2018-08-24 github
DDakunier 2018-08-24 github

@cjwijtmans nothing changes with PROTON_USE_WINE3D11=1 %command% added.

Kkisak-valve maintainer 2018-12-23 github

The Surge (378540)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2129.
@ziabice posted on 2018-12-23T12:31:38:

Whitelist Request

  • Name of the game to be whitelisted: The Surge
  • Steam AppID of the game: 378540

System Information

I confirm:

  • [x] that pressing the Play button in the Steam client is sufficient.
  • [ ] that runtime config options are necessary to run the game.
  • [ ] 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.
  • [x] Although I consider the gaming experience equal to Windows there are remaining issues:
    some users experienced this issue #410

This game is working perfectly at very high graphic detail. Everything worked like expected, controls where smooth and I haven't noticed any issue after 2 hours of gameplay.

Kkisak-valve maintainer 2018-12-23 github

Since this game is behaving with mesa 18.2.6, which is before vulkan transform feedback was added, that invalidates the earlier hypothesis that lack of transform feedback may be the root cause of the texture issue.

@Dakunier, can you retest with Proton 3.16-6 and if that doesn't make a difference, your issue may be Intel-specific.

Hhakzsam 2019-05-07 github

This game works fine with RADV and Proton 3-16.6/4-2.3. I tested mesa-19.0.3/llvm-8 and mesa-git/llvm-git on Vega10. Unfortunately, I can't test with ANV.

Llucifertdark 2019-05-07 github

I'm able to play the game with no noticeable graphical issues with the latest Nvidia drivers. no Proton launch commands needed. Proton 4.2-3.

AAwesamLinux 2019-05-08 github

Distro: Linux Mint 19.1 Tessa (64 bit)
GPU: Vega 56
Driver/LLVM version: Mesa 19.1.0-devel/9.0.0
Kernel version: 5.1.0-050100-lowlatency
Proton version: 4.2-3

The game works perfectly for me, did not see any issues with the graphics. (I used to have the problem with invisible objects/missing textures when I tried it like 8 months ago with older Proton/Mesa drivers).

Including a log of some gameplay for reference:
steam-378540.log.zip
system_info.txt

Kkisak-valve maintainer 2019-05-08 github

Removing the Mesa drivers label because https://github.com/ValveSoftware/Proton/issues/410#issuecomment-415811827 is the strongest indicator of what caused the texture issue and there hasn't been any comments to the contrary since November.

EEmanem 2019-09-01 github

The Surge should be whitelisted indeed. Playing flawlessly with latest proton 4.11-3 on Nvidia 430.

Kkisak-valve maintainer 2019-09-01 github

Is anyone seeing an issue with this game that would block it from being whitelisted?

EEmanem 2019-09-01 github

Is anyone seeing an issue with this game that would block it from being whitelisted?

I thought the poison fumes displayed as rainbow were a broken shader, but then I saw a playthough on Windows and it's the same rainbow effect :-)

Let me know if I should look/test/report for something particular/peculiar - otherwise all great!

AAwesamLinux 2019-09-01 github

System Information

  • GPU: RX VEGA 56
  • GPU Driver: Mesa 19.1.5
  • Kernel version: 5.2.11-200.fc30.x86_64
  • Distro version: Fedora Workstation 30 (64 bit) (Gnome)
  • Proton version: 4.11-3

Compatibility Report

  • Fullscreen and Windowed mode works
  • Alt+Tab back and forth desktop/game works
  • Nintendo Switch Pro Controller works

Everything looks to be working fine in this game.

fedora

system_info_fedora.txt


System Information

  • GPU: RX VEGA 56
  • GPU Driver: 19.1.0+aco+git1566739320-db73bde35cc-1bionic1 (Valves PPA)
  • Kernel version: 5.2.11-050211-lowlatency
  • Distro version: Linux Mint 19.2 Tina (64 bit) (Cinnamon)
  • Proton version: 4.11-3

Compatibility Report

With current Valve experimental ACO+Mesa driver the game is not rendered properly (no difference between ACO and LLVM).
mint
(compare with the above screenshot, objects are missing/invisible).

This appears to be a regression with current Valve experimental ACO/Mesa PPA driver (no difference between ACO and LLVM). I tested this game previously back in July 10 with the ACO experimental driver and it rendered correctly, so this is a new problem.

steam-378540-proton-4.11-3.log.zip
system_info.txt

My opinion is that this game probably can be whitelisted (I have not played far into the game though). But be aware that it is borked with the current experimental Mesa ACO driver.

Hhakzsam 2019-09-02 github

@AwesamLinux Can you re-test with https://gitlab.freedesktop.org/mesa/mesa/commit/966a455bb912cc9fd22580c6cf9b74e27faa4491 in your tree please? The missing objects problem should be fixed.
Thanks!

AAwesamLinux 2019-09-19 github

System Information

  • GPU: RX VEGA 56
  • GPU Driver: 19.3.0~git1909171715.374999ecfdf~b~mesaaco2 (ppa:ernstp/mesaaco)
  • Kernel version: 5.3.0-050300-lowlatency
  • Distro version: Linux Mint 19.2 Tina (64 bit) (Cinnamon)
  • Proton version: 4.11-5

Retest Compatibility Report

Game still works perfectly with LLVM, but has remaining issues with ACO.

@hakzsam I ran into problems compiling the Mesa drivers :sweat_smile:, so I never got around to test that.

However I did just now try with the drivers from ernstp/mesaaco PPA (that I assume includes it)

The problem with the invisible objects using ACO with this driver have been fixed. Performance and graphics are fine throughout the first introduction section of the game (like first 5-10 minutes when you are in the wheelchair).

But then at the outdoor segment when the game really begins, there is major performance issues, frequent 2-5 second freezes. These freezes do not occur with LLVM, and it used to not occur with ACO either when I tried it before. (Also tested llvmvs launch option and it made no difference)

surge
(notice the spikes)
steam-378540-proton-4.11-5-aco.log.zip
steam-378540-proton-4.11-5-llvm.log.zip
system_info.txt

I could probably produce a renderdoc capture if that would be useful

(I do realize from a Proton perspective this game is working fine, so probably I should be reporting this on the ACO github istead. Just wanted to flag any issues people might run into here)

AAwesamLinux 2020-01-08 github

As mentioned at https://github.com/daniel-schuermann/mesa/issues/150

I have retested the game with an RX 5700 and more recent Mesa:

  • GPU: RX 5700
  • GPU Driver: Mesa 20.0.0-devel (git-3bd4bcd 2020-01-07 bionic-oibaf-ppa)
  • Kernel version: 5.3.18-050318-lowlatency
  • Distro version: 19.3 Tricia (64 bit) (Cinnamon)
  • Proton version: 4.11-11
    system_info.txt
    steam-378540-logs.zip

With this setup I'm seeing dark stripes with both ACO and LLVM, that look like this :point_down:
20200107220209_1
This goes away if hitting escape and then resuming the game, other than that it works fine.

However, with older Proton version 4.2-9 there is no glitches at all with either LLVM or ACO. Here is what combinations of Proton / DXVK I have tried:

Proton DXVK Compiler Worked?
4.2-9 1.2.1 ACO SUCCESS
4.2-9 1.2.1 LLVM SUCCESS
4.2-9 1.5 ACO SUCCESS
4.2-9 1.5 LLVM SUCCESS
4.11-11 1.2.1 ACO FAIL
4.11-11 1.2.1 LLVM FAIL
4.11-11 1.3.4 ACO FAIL
4.11-11 1.3.4 LLVM FAIL
4.11-11 1.4.5 ACO FAIL
4.11-11 1.4.5 LLVM FAIL
4.11-11 1.4.6 ACO FAIL
4.11-11 1.4.6 LLVM FAIL
4.11-11 1.5 ACO FAIL
4.11-11 1.5 LLVM FAIL

:thinking:

NNTMan 2020-01-12 github

Is Proton/Wine developers here?
I want report about bug which reproduce in newer version Proton, but not reproduced in older.
When I launch "The Surge" in Poton 4.11-11 the vertical dark stripes run across the screen, but it not happens in Proton 4.2-9. Of cource I recheck this issue on GloriousEggroll Proton 4.21-GE-2 and sure that it reproduced too there.

Screenshots and RenderDoc I uploaded in the mesa bugreport

Is there any point fill a separate bug report at https://bugs.winehq.org or reporting here is enough?

GGuy1524 2020-01-14 github

@NTMan If you are able to reproduce this issue with wine or wine-staging, and bisect the regression to a wine commit, it would be a very good idea to report that at winehq.

AAwesamLinux 2020-05-17 github

System Information

  • GPU: RX 5700 ITX
  • GPU Driver: Mesa 20.1.0-rc1 (ppa:ernstp/mesarc)
  • Kernel version: 5.7.0-050700rc4-lowlatency
  • Distro version: 19.3 Tricia (64 bit) (Cinnamon)
  • Proton version: 5.0-7

Retest Compatibility Report

Everything in the game works, except that on the first area (scrap yard), there is still the flickering shadow issue.

Steps to Reproduce

  • Play the game until you get to the first area (the scrap yard)
  • You will see the flickering shadow across the screen as pictured in my previous post (if you don't see it, quit the game and resume/load a save from that area)
  • If you hit escape and then resume the game, the flickering shadow disappears and all is fine

steam-378540-proton-4.2-9.log.zip
steam-378540-proton-5.0-7.log.zip
system_info.txt

Iipr 2022-02-25 github

With Proton 7.0, Mesa 21.3.5 and kernel 5.16.11 it works fine.
There is no flickering in the shadows that I can see.
After switching to newer Proton I need to exit once and start the game again for gamepad to work, a minor one-time issue.

Proton versions

Launch options

Launch lines

Upstream links