search

ValveSoftware / Proton

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

Rising Storm 2: Vietnam (418460) #2726

Open opal1974 opened 5 years ago

opal1974 commented 5 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Like its sister games Red Orchestra 2 and Killing Floor 2, Rising Storm 2 tries to install .net everytime you play it. On my previous set up (under Kubuntu) I would sometimes get crashes on launch or when changing maps (I discuss this more at length at the Killing Floor 2 bug page) but since moving to Manjaro I have not gotten these crashes with this game. So far its just the annoyance of the .net install issue

Some time ago, there was a problem with Easy Anti-Cheat, but it started working a couple months ago? I didnt have the game before then, I bought it because people on protondb said it was working, which it is. You can play the game pretty much perfectly on my set up save for the annoyance of the .net install issue.

Reproduction

Install, start game.

solenum commented 5 years ago

Correct me if I'm wrong, but I think it is using Easy Anti Cheat, which is currently not working via wine/proton?

Looking forward to the day it does work, RS2 is one of my favorites :|

opal1974 commented 5 years ago

I dont know about that, but the game works fine for me now (see the OP). I've put in over 30 hours on the game since I bought it. I don't have a windows dual boot.

solenum commented 5 years ago

Holy crap really? I'll install it now and report back I guess, I had no idea EAC stuff was working with Proton yet.

solenum commented 5 years ago

God damn, it runs flawlessly. I'm getting a more stable framerate than I do on windows, multiplayer works without a single issue. I guess I need to try out other EAC games I figured where broken.

solenum commented 5 years ago

Here's some gameplay footage I recorded, overall it seems to work fine (I also get the .net install every time, as well as with a lot of other games but it only takes ~3 seconds).

For some reason though, colors seem to be very saturated and dark compared to what it looks like on Windows, anyone else experienced this?

Bumbadawg commented 5 years ago

Thanks @exezin for informing, i'll install and tell you. Glad it's off the EAC list. Maybe it's a gamma/compositor issue you're having. I remember back when EAC backed me off servers, colors were fine in solo.

solenum commented 5 years ago

I've come across one issue, it appears the map VTNE-HueCity is locked at 30fps for some reason, every other map I've played on has worked fine at about ~130fps.

Changing video settings down to the lowest etc doesn't seem to effect anything, and it appears to be locked at 30fps and not just running badly as it will literally never go over 30. I know each map sort of has its own post-processing and shader setup to look unique, this might have something to do with it.

Performance is fine on Windows.

solenum commented 5 years ago

I think I have found the solution to the color issue, it appears the gamma defaulted to some weird value and you can't easily change it via settings. You need to enable the console, open it with tilde (~) and type 'gamma '. Goes from a value of 1.0 to 2.5, setting it to 2.5 made it look normal again for me.

Still no solution to the HueCity performance though.

Edit; Found the solution. Disabling instanced rendering in video settings resolves the weird performance issue in the VNTE-HueCity map. For those that want to easily test this open the console and type 'Open VNTE-HueCity' to load into the map in singleplayer. I assume its a proton bug/issue?

Bumbadawg commented 5 years ago

I confirm @exezin sayings, VTNE-HueCity is locked at 30fps max while the other maps ran at 100fps+ (mostly CPU dependant). There might be an issue with instance rendering with this specific map. I could provide a log if needed.

opal1974 commented 5 years ago

OK there was a tiny update to RS2 and now I am getting a crash - everytime - upon loading a multiplayer level (havent tried practice offline maps yet). This worked earlier this morning.

steam-418460.log

EDIT: Just confirmed the offline practice maps work. Is this EAC not working again?

Bumbadawg commented 5 years ago

@opal1974 i updated to latest Steamworks redistribuables and didn't encounter issues on playing MP games with EAC enabled.

solenum commented 5 years ago

Can confirm that it still works fine for me as well, doesn't appear to be an EAC issue.

Bumbadawg commented 5 years ago

@kisak-valve if it helps to debunk. Here's a gist of me starting the game, joining a server with the map HueCity (which causes a 30fps lock atm, running at 37fps when looking at the ground/sky). I ran around for a minute then disconnected. As a reminder, every other map run at 100~140fps maxed out. Not this one. Which is not normal.

opal1974 commented 5 years ago

I reinstall steamworks, and now the game is working online again. False alarm I guess.

solenum commented 5 years ago

@Bumbadawg can you confirm that disabling instanced rendering solves it for you as well?

Bumbadawg commented 5 years ago

@exezin yes it fixed it! Well found mate.

Bumbadawg commented 5 years ago

Whether on ultra/lowest settings, after a game or two, the framerate drops and i have sluggish lags making the game almost impossible to play. Like whenever i look 30° left or right, the game starts to stutter down to 30fps, while when i look in the same direction, it goes up to 110/130fps. I tried disabling Esync but it didn't change. This suttering happens on Mordhau as well (UE4). Once restarted the game doesn't lag anymore, but it reoccurs after a game or two.

It's like the memory is leaking. I got 8GB VRAM and 16GB RAM. Does anyone get this issue ? Or is it just my hardware going AWOL :D

solenum commented 5 years ago

@Bumbadawg I've had a similar thing in KF2, I found that disabling the steam overlay resolved it for me (as far as I could tell). Worth a shot I suppose?

Edit; Also check out gamemode (https://github.com/FeralInteractive/gamemode) or at the very least set your CPU governor to performance, this increase performance in games for me a fair bit.

Bumbadawg commented 5 years ago

EDIT: removing the Steam overlay did the trick. Far better performance and no performance downgrade over time. Thanks @exezin!

As for gamemode, yep that's an imperative now =) It should be integrated with Proton frankly. Helps with CPU-limited games.

Zorrototo commented 5 years ago

You can have it for your Steam games by modifying the Steam launch options for a game: gamemoderun %command%

This way it is integrated with all Steam games without waiting for Valve :D

edit: so I don't get it, the EAC for this game works? How is that possible I didn't see any news regarding EAC Proton support. Are the servers you test protected by EAC?

I'm tempted to install but it is a large download.. not worth if it is not working.

solenum commented 5 years ago

@Zorrototo I'm not totally sure on the sitrep with EAC, but this game for sure uses it for its servers, another EAC games seem to be working on and off. Its often a case of it starts working with Proton one day, then EAC updates and it breaks again.

So its going to be hit and miss for a while, but EAC have said they will eventually work with valve to bring Proton support. Other games that I know work (at least for the moment) with EAC are Squad, and Apex Legends.

And yes I can confirm with 100% certainty that it is working with Proton at the moment. I've been putting in a few hours each day, performance is fantastic (make sure to disable instanced rendering & steam overlay).

Bumbadawg commented 5 years ago

You can have it for your Steam games by modifying the Steam launch options for a game: gamemoderun %command%

Yup, here's my launch options now with Steam overlay disabled: PROTON_NO_ESYNC=1 DXVK_HUD=version,fps,frametimes,memory PROTON_LOG=0 gamemoderun %command% -nostartupmovies (not very noob convenient one might say)

Ingame options:

It seems that Proton requires 6+core CPUs to run like on native with 4core most AAA games. Even a 4.4GHz quadcore CPU-limits high-end GPUs most of the time (GTX 1070 with nvidia-430 in present case), making it idling at 70%.

EAC: yes it works atm, and it's good news Apex does too (like it first did before the breaking update). Once EAC will whitelist Proton it'll be a safe stance to say all EAC titles should work with Proton.

Bumbadawg commented 5 years ago

Reporting a minor graphic issue with brightness/gamma, can you guys confirm: when ingame, the "soldier" menu have super low gamma.

solenum commented 5 years ago

@Bumbadawg gamma in general seems odd to me, enable developer console in the settings and then open it with tilde key (~). type in "gamma 2.5" to change the gamma, values appears to be between the range 1.0 and 2.5. I have found values of 2.3-2.5 to be decent for me.

Zorrototo commented 5 years ago

Default gamma is 2.2 if I'm correct, looking at both my windows and linux config files for this game. From my experience never mess with gamma in the game as it feels that it looks never the same to me after that.

I can confirm that game works online I played multiple games on popular server without getting EAC kicked or banned (that is my biggest fear currently testing Proton with non compatible games).

Game was running with lowest settings on first launch, with noticeably poor performance in menu. I disabled instanced rendering, set everything but shadow to maximum or high value, and I could play properly but performance was way worse than on Windows. Also noticed some smokes on the ground disappearing or reappearing randomly.

Bumbadawg commented 5 years ago

If you type "gamma" in console it resets to a default value which is 2.2 indeed.

@Zorrototo

I could play properly but performance was way worse than on Windows. Also noticed some smokes on the ground disappearing or reappearing randomly.

It seems you might lack VRAM/RAM that Proton adds up compared to native, i noted the game maxed out might allocate 5.2GB VRAM on some maps in 1920x1080, it'll usually eat up to 3.4GB RAM max. For the performance, the most impacting setting so far seems to be World detail. I set it to medium. Since UE3 is mostly single-thread, you'll require one powerful core to lead up your performances up, even on Win10 most players can't crank up the 144fps+ because of that.

Zorrototo commented 5 years ago

No it just performs badly compared to Windows.

mozo78 commented 5 years ago

It's pretty normal. When the game gets a native release, then you can compare the performance.

sunnyyssc commented 5 years ago

After updating proton to 4.2.6, now I get "Authentication timeout (1/2)" when I join a server. It used to work in 4.2.5

kisak-valve commented 5 years ago

Hello @SunnyYSSC, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Bumbadawg commented 5 years ago

I confirm @SunnyYSSC @kisak-valve , here's a log of failing to authenticate with 4.2-6.

solenum commented 5 years ago

Yeah getting the same issue here, I can join a server and play for maybe 30 seconds before I get kicked with the same reason, "Authentication timeout (1/2)".

benyben27 commented 5 years ago

using the 3.16-9 Beta has the same problem. is there a way to roll back to 4.2-5 on steam maybe?

Zorrototo commented 5 years ago

Not that I know. Maybe manually replace files.

DerRidda commented 5 years ago

I can confirm this regression with 4.2-6, would love to be able to toll back to -5 to see if it's the Proton update that did it or if EAC changes caused the issue.

EDIT: I would like to confirm explicitly that this error message is caused by Easy-Anti Cheat as older posts in the RS2 Steam forums about identical errors show.

Zorrototo commented 5 years ago

It may be a Steam or a EAC error, did you look into your GAME log file?

edit: .local/share/Steam/steamapps/compatdata/418460/pfx/drive_c/users/steamuser/My Documents/My Games/Rising Storm 2/ROGame/Logs/

So something weird I noticed in last week's log:

[0000.95] Log: Loading anticheat from Z:\home\omano.local\share\Steam\steamapps\common\Rising Storm 2\Binaries\Win64\EasyAntiCheat/easyanticheat_x64.dll [0000.95] Log: Loaded anticheat DLL [0000.95] Log: Loaded anticheat init [0000.95] Warning: Warning, Anticheat is not loaded. You will not be able to connect to any Anticheat protected servers.

I have exact same message in today's log:

[0000.87] Log: Loading anticheat from Z:\home\omano.local\share\Steam\steamapps\common\Rising Storm 2\Binaries\Win64\EasyAntiCheat/easyanticheat_x64.dll [0000.91] Log: Loaded anticheat DLL [0000.91] Log: Loaded anticheat init [0000.91] Warning: Warning, Anticheat is not loaded. You will not be able to connect to any Anticheat protected servers.

So I wonder, were you all sure that you were playing on EAC protected servers last week? I'm not ure now that I see that I didn't remember filtering servers for EAC enabled ones

solenum commented 5 years ago

I was indeed playing on EAC protected servers on the previous version of proton with no issue.

benyben27 commented 5 years ago

@Zorrototo it did work, but it needed the launch option cd "<steam folder>/steamapps/common/Rising Storm 2/Binaries/Win64"; %command% to work in EAC servers. if you don't have that launch option it is probably because of it.

solenum commented 5 years ago

It was working on EAC servers without that command for me on the previous version of Proton.

Edit; Tried the above command with latest proton and still have the same issue, not working.

benyben27 commented 5 years ago

It was working on EAC servers without that command for me on the previous version of Proton.

well you used to need it in 4.2-2, maybe it changed

ehea617 commented 5 years ago

I am also experiencing this regression that occurred when upgrading to 4.2-6 from 4.2-5. Before, I was able to play on all servers with no EAC issues and no special launch options. After the update, the game can no longer stay connected to servers for longer than a minute. Trying the workaround that benyben27 suggested did not make any difference.

ehea617 commented 5 years ago

After further testing, I can confirm that this is not an issue with the update to 4.2-6. It is instead a new issue with EAC on Proton. Downgrading to 4.2-5, the version it used to work for me on, results in the same error. This makes me believe that EAC received an update that broke Proton support. It was not the update to 4.2-6 that broke EAC support.

nmenetrier commented 5 years ago

Same issue for me, even with proton-4.2-5 it's not working anymore since the recent EAC update.

solenum commented 5 years ago

@ehea617 any way to downgrade to 4.2-5 without compiling from source?

ehea617 commented 5 years ago

@exezin Open the Steam console (steam://nav/console) and run "download_depot 1054830 1054831 325796197665791634". Wait for it to say download complete in the console, then install the downloaded files like you would with a custom build into ~/.steam/root/compatibilitytools.d/. You will need to create a compatibilitytool.vdf file for Steam to detect the build (see https://github.com/ValveSoftware/Proton/blob/proton_4.2/compatibilitytool.vdf.template).

Bumbadawg commented 5 years ago

Went back to 4.2-5 and still got the authenticate error. Here's my log.. Might be due to new Steam Network API Error reading SteamExe key EDIT: i opted out of beta to check, still does authentification failure. Can anyone confirm that issue with 4.2-5 ?

Bumbadawg commented 5 years ago

@kisak-valve Reporting for 4.2-7: it still does EAC authenticate error. steam-418460.log

PrimaMateria commented 5 years ago

I tried to follow @ehea617 comment with steps listed below. At the end the authentication problem is still present :-(

  1. Run steam with console: steam -console
  2. "Console" page link should be visible
  3. In console execute download_depot 1054830 1054831 325796197665791634
  4. Create compatibilitytools.d folder if it doesn't exist: mkdir ~/.steam/root/compatibilitytools.d
  5. Copy downloaded depot to compatibilitytools.d folder: cp -r ~/.local/share/Steam/ubuntu12_32/steamapps/content/app_1054830/depot_1054831 ~/.steam/root/compatibilitytools.d/
  6. cd ~/.steam/root/compatibilitytools.d
  7. mv depot_1054831 proton-4.2-5-risingStorm2-EAC-fix
  8. nvim proton-4.2-5-risingStorm2-EAC-fix/compatibilitytool.vdf
  9. Use the configuration below the steps
  10. Restart steam
  11. Open Rising Storm 2 properties
  12. In General tab check checkbox "Force the use of specific Steam Play compatibility tools"
  13. Choose proton-4.2-5-risingStorm2-EAC-fix
  14. Run the game

{
  "compat_tools"
  {
    "proton-4.2-5-risingStorm2-EAC-fix" // Internal name of this tool
    {
      // Can register this tool with Steam in two ways:
      //
      // - The tool can be placed as a subdirectory in compatibilitytools.d, in which case this
      //   should be '.'
      //
      // - This manifest can be placed directly in compatibilitytools.d, in which case this should
      //   be the relative or absolute path to the tool's dist directory.
      "install_path" "."

      // For this template, we're going to substitute the display_name key in here, e.g.:
      "display_name" "proton-4.2-5-risingStorm2-EAC-fix"

      "from_oslist"  "windows"
      "to_oslist"    "linux"
    }
  }
}
ehea617 commented 5 years ago

@PrimaMateria I quite clearly said that it doesn't work. Not once did I imply that it did. Read https://github.com/ValveSoftware/Proton/issues/2726#issuecomment-500171015

solenum commented 5 years ago

Game just got a decently large update, situation still the same. Getting kicked after about a minute for the same reason. Likely just anticheat that updated and borked it again, its always back and forth like this.

I wish EAC would just step up and contribute, rather than (intentionally?) break support literally every update. It feels like as soon as wine/proton updates and EAC starts working again, EAC promptly release an update that breaks it.