ValveSoftware
Battlefield™ V (1238810)
Compatibility Report
- Name of the game with compatibility issues: Battlefield™ V
- Steam AppID of the game:1238810
System Information
- GPU: RX 580
- Driver/LLVM version: Mesa 20.1.1 - kisak-mesa PPA
- Kernel version: 5.4.0-37-generic
- Link to full system information report as Gist: https://gist.github.com/guustflater/ee3faef827bd7a7321b8c9cb94b8b9e6
- Proton version: 5.0-9 / proton 5.9-2-MF (glorious egroll)
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
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.
Have you tried it with gamemode? https://github.com/FeralInteractive/gamemode
Something I've noticed in other games with heavy stutter in Proton is that uncapping the framerate often helps. Did you try that?
https://www.protondb.com/app/1238840 people are reporting that (at least for Battlefield1) there is a fix to solve the performance issues,
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.
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
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
@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.
@pingubot could you upload the system information for the machine where you are seeing the dx12 failure?
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.
@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.
Running Battlefield V for the first goes through these steps:
- runs up the OriginThinSetup process.
- play button switches to "Launching" for a very long time
- 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:
- Experimental
- 6.3-6
- 5.13-6
- 6.9-GE2
- 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
@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.
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.
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?
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:
BF1:
Took me quite a lot time of troubleshooting :(
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
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.
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.
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
- Name of the game with compatibility issues: Battlefield V
- Steam AppID of the game: 1238810
System Information
- GPU: AMD Radeon RX 5700 XT
- Video driver version: Mesa 23.1.4
- Kernel version: 6.1.38-4
- Link to full system information report as Gist: Gist link to system info and runtime diagnostics
- Proton version: Proton Experimental
I confirm:
- [ * ] that I haven't found an existing compatibility report for this game.
- [ * ] that I have checked whether there are updates for my system available.
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
- Install steam with flatpak (Debian 12, gnome)
- Install Battlefield V and enable Proton Experimental in compatibility options.
- Launch game, open Team Deathmatch in Multiplayer.
- Select a lobby and join.
- 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.
- Sometimes I can play for a few minutes and then the freeze occurs.
- Happens every single time without fail.
Thanks for transferring. Please let me know if I can provide any more info.
@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.
@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.
@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).
@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 :)
@mediocretwo Alright - I have enough suggestions to warrant a new comment instead of just editing the last one :)
-
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 🗡️
-
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.