search

ValveSoftware / Proton

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

Battlefield™ V (1238810) #3977

Open guustflater opened 4 years ago

guustflater commented 4 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Stuttering.. It starts already in the menu, looks almost the same kind of stuttering as in NFS heat (already reported). Too bad as the game should run almost perfect for the rest but is now kind of unplayable.

guustflater commented 4 years ago

Doesn't start with proton 5.0-9 steam-1238810.log

guustflater commented 4 years ago

Proton 5.9-GE-2-MF log

steam-1238810.log

SOlsson91 commented 4 years ago

Have you tried it with gamemode? https://github.com/FeralInteractive/gamemode

Newbytee commented 4 years ago

Something I've noticed in other games with heavy stutter in Proton is that uncapping the framerate often helps. Did you try that?

Revilum commented 4 years ago

https://www.protondb.com/app/1238840 people are reporting that (at least for Battlefield1) there is a fix to solve the performance issues,

KibaGasteiz commented 3 years ago

Very unstable with the latest Proton Experimental (updated today). The log is big so Github won't let me upload, using Mega instead: https://mega.nz/file/SVV3XSqB#BjUPxaGhXVHPaaasuqAkwnNImClxph1mkRYoeKwWYkc Proton 6.3-3 working perfectly.

kodatarule commented 3 years ago

The game works just fine with DXVK, but fails to run with VKD3D(D3D12). The issue is that it causes a hard system freeze you can't even enter another desktop with CTRL+ALT+F2 nor open just a terminal session with CTRL+ALT+F6 it's just stuck right before opening the main menu. steam-1238810.log

pingubot commented 3 years ago

HI,

the game works fine with Proton 6.3.5 but it crashes with proton experimental in dx12 mode. This is not an issue of the vkd3d version in use, as all vkd3d versions i tested (2.3.1, master, master+rbar) work fine with 6.3.5 but do not with proton experimental. The game simply hangs and then closes.

Log attached: steam-1238810-bfv-crash.txt.gz

pingubot commented 3 years ago

@kisak-valve : might be worth to take a look at that issue as we are seeing a regression from proton 6.3.5 to proton-experimental here.

alasky17 commented 3 years ago

@pingubot could you upload the system information for the machine where you are seeing the dx12 failure?

pingubot commented 3 years ago

@alasky17 : steamsysinfo.txt

kisak-valve commented 3 years ago

Hello @pingubot, CClientJobGatherRuntimeInformation: container read output failed at the end of your system information tells us that Pressure Vessel failed to gather the extended diagnostics information in the Steam Linux Runtime - Soldier container environment, which is used by Proton 5.13 and newer.

Blind guess that this is related to your local git build of mesa/RADV, but setting that aside, I'd expect that Proton 5.13 and 6.3 to also fail to start the game with that hint. Please open a new issue report in the steam-runtime issue tracker focusing on your system information.

pingubot commented 3 years ago

@kisak-valve i didn't use pressure vessule runtime to run the game cause i partly have issue with the runtime (games not starting at all) and therefore it is unrelated to that issue. Maybe the system information does not work cause i modified the v2 entry point script to avoid the runtime usage.

The game itself works great with radv git and my tested versions of vkd3d proton on Proton 6.3. As soon as i switch to 6.3 experimental the game freezes show up. Those freezes show up on all my tested vkd3d-proton versions in experimental and work fine with the same vkd3d-proton and radv versions when 6.3 is used. Imo, the issue here is related to something in proton-experimental which is not in 6.3 yet.

Update: I tried 6.3.6-rc2 in addition, also works fine.

pingubot commented 3 years ago

any news on that issue ?

Richard-Payne commented 3 years ago

Running Battlefield V for the first goes through these steps:

1) runs up the OriginThinSetup process. 2) play button switches to "Launching" for a very long time 3) eventually starts the game.

on subsequent launches, it switches the play button to launching for a few seconds and then goes back to "play" indicating that game has crashed.

I've verified the integrity of the local game files.

I have tried different Proton versions:

1) Experimental 2) 6.3-6 3) 5.13-6 4) 6.9-GE2 5) 5.21-GE1

I attached the Proton log for 6.3 experimental. steam-1238810.log

DISTRIB_ID=ManjaroLinux DISTRIB_RELEASE=21.1.4 DISTRIB_CODENAME=Pahvo DISTRIB_DESCRIPTION="Manjaro Linux"

Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.10.68-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

cdgriffith commented 3 years ago

@Richard-Payne I have had the same issue for a while, easy to work around in my case thankfully. In the case where it doesn't launch, open your favorite process / system monitor and you'll notice either EA-Link.exe or Origin.exe using 100% on one core. Kill that process and wait a few seconds for all other *.exe to die (wineserver, explorer, etc...) then try again. Sometimes it works on next launch, sometimes it takes 3~4 times of doing that.

Richard-Payne commented 3 years ago

Thanks @cdgriffith, will keep that in mind for next time.
After seeing your comment, I tried again and it's now working properly without any intervention. Maybe "someone" fixed "something". Who knows.

shavenne commented 3 years ago

I can confirm the problems which @pingubot has. 6.3-7 is working fine and absolutely stable (with DX12 enabled) but I get random crashes to desktop (first the picture freezes for some seconds and then crash to desktop) on Proton Experimental if DX12 is enabled (it seems... I'm not 1000% sure if it's stable with DX12 disabled). Sometimes within 5 minutes of playing, sometimes after half an hour. steamsysinfo.txt

Edit: It doesn't seem to happen with Proton 6.3-8 RC. Is this even plausible?

shavenne commented 2 years ago

BF5 and BF1 (maybe BF4 too) are somehow broken with proton (tried 6.3, 7.0 and experimental) if it uses amdvlk (2022.Q1.3-1) instead radv. Bad performance and graphic glitches.

BF5: Screenshot_20220226_001928 Screenshot_20220225_231821

BF1: Screenshot_20220226_163514

Took me quite a lot time of troubleshooting :(

ibasaw commented 2 years ago

i can launch the gamer, then inside the game it ask for update, pc become unrespondable, 7% and crash to desktop, can't play. wine 7 + ubuntu 21

NGStaph commented 2 years ago

Audio stops working (mid-game) on the latest proton experimental.

mentos1386 commented 1 year ago

I have issues running it using Proton Experimental and Proton Next (7.0-5) and Proton 7.0-4.

Not sure if it's Battlefiled V problem or the "EA Game Launcher" client thing that starts before it. As with Proton 7.0-4 (and others mentioned) i don't see the launcher starting, it seem to "crash" before.

Proton 6.3-8 seems to work fine.

BloodyIron commented 1 year ago

Yeah BF V broken for me. Proton Experimental or 7.0-6, doesn't matter. EA app launches, then closes, game doesn't launch, whole application quits. Completely unusable.

kisak-valve commented 1 year ago

Battlefield V crashing on map load every time with Proton Experimental

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7067. @mediocretwo posted on 2023-09-02T13:44:30:

Compatibility Report

System Information

I confirm:

Symptoms

The game is freezing and completely crashing to desktop during loading screen, whenever I try to join a map (Team Death Match) or within few minutes. This issue is not occurring with Proton version 8.0.3.The logo animation on the loading screen completely freezes and after around 20-30 seconds the game fully crashes and exits to desktop. Happening on every launch, not some intermittent issue. I'm using steam as flatpak.

Note

The Proton log file generated was HUGE (2.1 GB) and compressing it is not enough to meet Github's 25 MB file upload limit. (The compressed file is still 120 MB). So I did not upload the log file here. Let me know how else you would like me to upload the Proton Log file.

Reproduction

  1. Install steam with flatpak (Debian 12, gnome)
  2. Install Battlefield V and enable Proton Experimental in compatibility options.
  3. Launch game, open Team Deathmatch in Multiplayer.
  4. Select a lobby and join.
  5. Game starts loading the map, then freezes for 20-30 seconds and then crashes to desktop during the loading screen animation or right after completing the loading of map.
  6. Sometimes I can play for a few minutes and then the freeze occurs.
  7. Happens every single time without fail.
mediocretwo commented 1 year ago

Thanks for transferring. Please let me know if I can provide any more info.

alasky17 commented 1 year ago

@mediocretwo Unfortunately, I am not seeing any crash like this which makes this difficult to investigate. I am on a slightly newer mesa version (23.1.6) which could help? It would be great if you could upload the log somewhere so we can take a look. One option is you could create a random repo on github and upload the compressed log there? Also - did you try compressing with xz -T0? It likely wouldn't get it small enough still, but I've found that to be a pretty efficient way to compress these text log files.

mediocretwo commented 1 year ago

@alasky17 Hi, I tried compression with xz (with highest compression - lvl 9) and the log file came down to 38 MB. This is still too large for github, so I uploaded the file to Google drive. Here is the link to it: Proton Logs. Hope that is fine.

Regarding Mesa version, I thought it might not make a difference since this issue only happens with Proton Experimental and does not occur with version 8.0-3. However, the EA/Origin overlay is bugged with version 8.0-3 (the overlay is just blank white, no content rendering) so I am using Experimental, where the EA overlay is working fine again. The only issue is the crash. Hope the logs help with knowing whats going wrong.

alasky17 commented 1 year ago

@mediocretwo Thank you for the log! Hopefully there will be some hint in there. If you want to experiment in the meantime, could you try disabling the EA overlay? Since you happened to mention that as a difference from 8.0-3, I wonder if it is something in the "correctly functioning" overlay that is causing the crash. (This is just a pure hunch).

alasky17 commented 1 year ago

@mediocretwo Someone took a look at the log and it turns out the problem is an access violation happening in dxvk. Pinging @doitsujin @Blisto91 ... I would also suggest trying with gamemode disabled :)

alasky17 commented 1 year ago

@mediocretwo Alright - I have enough suggestions to warrant a new comment instead of just editing the last one :)

1) Could you please try the most recent experimental release (20230907). There was a known regression in the experimental version from your log that is already fixed, so it would be great if this is already solved 🗡️

2) If you still get the crash with 0907, could you try dropping the dxvk version from Proton 8.0-3 (where you don't get the crash right?) into Proton Experimental? This would confirm if this is a dxvk regression or something else potentially going wrong. To do this: cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/dxvk/ ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/dxvk/. cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib64/wine/dxvk/ ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/dxvk/.

After testing, you can delete the Proton - Experimental/files/lib64/wine/dxvk folder and run "verify integrity of files" on Proton Experimental, and it should get you back to the stock dxvk version.

mediocretwo commented 1 year ago
  1. Could you please try the most recent experimental release (20230907). There was a known regression in the experimental version from your log that is already fixed, so it would be great if this is already solved 🗡️

@alasky17 I'm not sure how I upgrade to the most recent experimental release, I just select 'Proton Experimental' from the Compatibility tab in Battlefield properties. Can you tell me if there's anything I should do apart from that?

Edit: Also turning off gamemode didnt help, still crashing.

alasky17 commented 1 year ago

@mediocretwo Yes, just selecting Proton Experimental is enough. Since it is not fixed by the known regression fix, could you please try Step 2 that I detailed above so that we can determine if this is a Wine regression or a DXVK regression?

mediocretwo commented 1 year ago

Hey @alasky17 I was just about to report back, I tried the 2nd step last night and it worked like a charm! I finally played two games without a crash, with the Origin overlay working as well, so I didn't have to miss any messages from my friends. Thank you so much, it's impressive how you got straight to the problem, it shows that you really have a lot of deep understanding of the software! Hope you guys can implement this fix in the Experimental version now.

Also, what do I do next? Will the changes I made locally get reverted when Proton gets an update? And how will I know when I don't have to apply this manual fix anymore and let it go back to its original state?

alasky17 commented 1 year ago

@mediocretwo Thank you for trying that! To clarify, we did not actually fix anything at this point -- the swap that I suggested was to test if the change between 8.0-3 and experimental that caused the crash was due to some change in DXVK, and your findings indicate that it was. The next step will be to try to narrow down what specifically is causing the crash.

I would suggest that you save the contents of ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/dxvk/ and ...../lib64/wine/dxvk/ somewhere locally so that after the next round of testing suggested below, you can easily replace the dxvk/* files and play the game while we figure out what is going wrong :) That way, if we have not fixed the issue before the next Proton release, you will still have an easily accessible version of the dxvk files to use.

While examining the log you provided, someone noticed that the game is using a d3d12.dll file from the game folder (~.var\app\com.valvesoftware.Steam.local\share\Steam\steamapps\common\Battlefield V\d3d12.dll) that does not ship with the game. It looks like this dll is what is causing the crash for you, and explains why we were unable to reproduce the crash. Could you try: 1) Run "verifying the integrity of files" on Proton - Experimental to re-grab the broken dxvk files that ship currently 2) Remove the d3d12.dll from the common/Battlefield V folder temporarily 3) See if you still get the crash?

If removing the d3d12.dll fixes the crash, could you please upload a copy of the dll to google drive where you put the log so that we can investigate locally?

Edit: Also, do you know where that dll came from? From a mod? Native Windows? Somewhere else?

mediocretwo commented 1 year ago

Yes, I do know where that dll came from, its from ReShade! I use it to apply post processing graphics effects like sharpening etc. And you were right, after restoring Proton Experimental to its original state, removing the dll fixed the crashes. If I reinstall reshade for this game, the crash is coming back. I didn't think much of it since it worked flawlessly on Proton 8.0-3, so maybe there's some changes in Experimental that do not work well with ReShade? I'm uploading the dll to drive here if you need to take a look at it. You can look at ReShade github as well if it helps you understand what exactly it is doing. I would like to keep using ReShade in the future, so I hope you can try to make it work with Proton. Let me know if you need anything else from my side.

alasky17 commented 1 year ago

@mediocretwo Thank you for the info! It turns out that this was the culprit, and with the dll info, @gofman was able to fix the regression in dxvk :) The fix was merged last night and is now live in Proton - Experimental bleeding-edge. We also cherry-picked the fix into the Proton 8.0-4 release candidate . It would be great if you could confirm that this fixed the crashing for you :) You can select the 8.0-4-rc as a beta option in Proton 8.0.

mediocretwo commented 1 year ago

I just checked the game again with the Beta version/Release Candidate of Proton 8.0-4. It was a bit inconsistent, the crash was still happening in the beginning but after like an hour and a half there was an update to Proton. After that update installed, the crash has disappeared now. Will keep an eye out if it returns, but seems to be gone after that update. Also the EA overlay is working too, so thats good as well.

alasky17 commented 1 year ago

@mediocretwo We made a mistake and I think forgot to push the release candidate with the fix live to the public branch yesterday. I pushed it live a couple of hours ago, which hopefully lines up with when the crash magically got fixed? Thank you for the details! We definitely want to hear if the fix is only helping intermittently :)

mediocretwo commented 1 year ago

Yeah the crash stopped after an update around 4-5 PM UTC. I've played for about an hour now and it has not crashed, I think it has been fixed. Never could play this long when the crash was happening before, would crash within 10-15 minutes maximum.

JCDentonCore commented 11 months ago

I'm having crashes when activating ray tracing in this game, it starts but when I try to load the menu it closes every time.

In other games raytracing works normally like cyberpunk 2077

Pc specs: Ryzen 5800x, 32 GB ram DDR4, RTX 3070, SSD 2 TB, monitor 1440p 165 Hz, OS Manjaro Linux (KDE) with kernel 6.7rc1

Proton Experimental bleeding edge, steam beta and runtime beta, steam variables MANGOHUD=1, PROTON_LOG=1

Nvidia drivers 535.43.16

Proton log:

https://drive.google.com/file/d/1vhksnOtfj_SnnUgV6WaAhGSlUIlhr3hE/view?usp=sharing

Steam runtime log: steamruntime.log

kisak-valve commented 11 months ago

Battlefield V Mouse Input sensitivity broken on vertical axis.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7355. @LethalManBoob posted on 2023-12-16T20:59:27:

Sens is halved when looking down but only when looking down. This is lessened when changing the raw input setting on or off but does not fix, i cannot get it to be consistent.

I confirm:

LethalManBoob commented 11 months ago

Hope this gets fixed soon, its not very playable atm

waspennator commented 7 months ago

Ea is planning on adding its anti cheat to this game soon, so it'll be broken on Linux in general

LethalManBoob commented 7 months ago

Ea is planning on adding its anti cheat to this game soon, so it'll be broken on Linux in general

Lets hope it stops there. Not really the biggest loss. Just means I wont be buying any ea games anytime soon. Lol.

JCDentonCore commented 7 months ago

https://github.com/ValveSoftware/Proton/issues/3977#issuecomment-2023434544> Ea is planning on adding its anti cheat to this game soon, so it'll be broken on Linux in general

Offtopic:

Source?, oh God no!

waspennator commented 7 months ago

Ea is planning on adding its anti cheat to this game soon, so it'll be broken on Linux in general

Source?, oh God no!

https://www.ea.com/en-gb/games/battlefield/battlefield-5/news/eaac-and-battlefield

LethalManBoob commented 7 months ago

Ea is planning on adding its anti cheat to this game soon, so it'll be broken on Linux in general

Source?, oh God no!

https://www.ea.com/en-gb/games/battlefield/battlefield-5/news/eaac-and-battlefield

To be fair the cheating situation was extremely bad. Almost unplayable. But yes this is the worst company in america continuing to be as such.

JCDentonCore commented 7 months ago

So finally it's gone?

mediocretwo commented 7 months ago

Welp. I play this game everyday. Sad day of my life. Back to windows I go.

LethalManBoob commented 7 months ago

Welp. I play this game everyday. Sad day of my life. Back to windows I go.

Enjoy your goyslop. Can't say the community will miss you.