Battlefield 4™ (1238860)

[ipkpjersi]

Compatibility Report

• Name of the game with compatibility issues: Battlefield 4™
• Steam AppID of the game: 1238860

System Information

• GPU: GTX 1070
• Driver/LLVM version: NVIDIA 440.82
• Kernel version: Linux 4.15.0-106-generic x86_64
• Link to full system information report: Gist
• Proton version: 5.0.9

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

This isn't a problem specific to Linux with Proton, but rather, a problem that also exists on Windows. When you first install the game and enter a multiplayer game, after 5 minutes or so you will get kicked from the multiplayer game by PunkBuster, but there is an easy fix available for this. Other than that, the game seems to run quite well for me and I haven't really noticed any other issues.

Solution

The solution to this is fairly simple, it was originally posted by Feline Fowl on ProtonDB. I will crosspost it here so others can easily find it. The solution is as follows:

Battlefield 4 uses "PunkBuster" Anti-Cheat, however the game has an issue (also happens on Windows) where even though during the install it says everything is fine, you'll get kicked from every multiplayer match. To fix this, you'll have to manually download PunkBuster for Windows from the site, and run the EXE via Wine: https://www.evenbalance.com/pbsetup.php

I recommend putting this EXE in its own folder, as it downloads some extra files. Run it with the same prefix that Battlefield 4 uses, so run the game at least one time and then close it. Then run WINEPREFIX="/path/to/library/compatdata/1238860" wine pbsetup.exe. Select "Battlefield 4" from the dropdown, and point it to the game's install folder if it didn't find it automatically. It might take a while to download, but it'll complete and Battlefield 4 multiplayer will work!

[Xiretza]

There is also the issue of no ping indicator in multiplayer matches - the leaderboard simply shows - instead of the RTT in ms. Many servers have plugins that automatically kick players with a missing ping. Of note is that all other in-game latency displays, such as in the server browser or in the debug overlay, work correctly.

Unfortunately I don't have the game on steam, but the ratings on ProtonDB suggest that at least some steam players also have the problem. As an attempted workaround, I tried setcap cap_net_raw+epi /usr/bin/wine-preloader, which results in ping working inside wine (which it didn't before), but no change in BF4 ingame latency display.

$ wine ping steampowered.com
Pinging steampowered.com [104.96.45.241] with 32 bytes of data:
Reply from 104.96.45.241: bytes=32 time=34ms TTL=54
Reply from 104.96.45.241: bytes=32 time=31ms TTL=54
Reply from 104.96.45.241: bytes=32 time=34ms TTL=54
Reply from 104.96.45.241: bytes=32 time=38ms TTL=54

Ping statistics for 104.96.45.241
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
	Minimum = 31ms, Maximum = 38ms, Average = 34ms

Personally I've never encountered any punkbuster related kicks on a vanilla Wine/Origin setup.

[ThaChillera]

Same issue with the ping, getting kicked is super annoying. Haven't managed to solve it yet with the setcap solution, but others apparently have

[ipkpjersi]

Battlefield 4 no longer even opens for me with Proton 5.09, I had to switch to Proton-5.11-GE-1-MF by GloriousEggroll to get it to open. Is anyone else having this problem or is it just me?

edit: the problem was just me. I had Proton installed on an external drive SteamLibrary for some reason, I was in the process of replacing the drive (which meant it no longer existed)

As for the issue with ping not displaying and getting kicked for missing ping, I am not having that issue. I have tried over 10 different servers and I have yet to be kicked once I completed the initial PunkBuster setup.

Everything is working as expected for me once again.

[toma678]

I appear to be having an issue with the game (Origin overlay?). The game starts with Proton 5.11-GE-2-MF. The mouse works in the menus however if I join a game, neither the mouse nor the keyboard work. The keyboard doesn't work in the menus as if I try and change a key binding, there's no response from any keys.
I can't disable the overlay as I own the game through Steam and so it launches Origin in external launcher mode which defaults the overlay on and it can't be turned off from what I can see.

Can anyone shed any light on this?

EDIT: I was using GE proton as 5.09 didn't appear to work. It seems to work using 5.09 however now although the mouse works in the menu, when selecting a deployment point, the selection "scrolls" through vertically and the mouse is frozen in game, but the keyboard works.

[ipkpjersi]

I had a similar issue I think with my keyboard not working in Battlefield V, I don't believe it was related to Origin in-game overlay or Steam in-game overlay. I switched from Fullscreen to Borderless and that fixed my keyboard not working in Battlefield V, might be worth a try for you.

[Cherser-s]

I have a similar issue with keyboard not working in both menu and a game, as well as mouse in locked mode in game, though Origin overlay is disabled. Thought at first it was due to XWayland, but it doesn't work in native Xorg window manager either as well as Wine virtual desktop.

[warriormaster12]

When is the ping issue going to be fixed or is there at least a workaround for it?

[Cherser-s]

Well, there is a workaround for ping, you just need to allow wineserver and wine-preloader binaries (both 64 and 32) to use raw sockets.
https://appdb.winehq.org/objectManager.php?sClass=version&iId=31145

[poperigby]

I'm having an issue with Origin not recognizing the game as installed. I get all the way through the setup, but when I press play Origin launches and says:

The game Battlefield 4™ Premium Edition does not appear to be installed. Please install it or try relaunching the game.

OS: Arch Linux
Proton version: 5.13-4

[fedebenelli]

When I try to launch the game steam just nothing happens except for Steam showing it as running. Doesn't even launch Origin

OS: Arch Linux
Proton version: Proton 5-21-GE-1
GPU: Nvidia GTX 960
CPU: AMD FX 6300

[tunanachos]

Any update on the no ping issue? Picked this up during the Winter summer sale on Steam and it works fine (using Proton-5.21-GE-1).
The main issue I have (besides Origin being a bit difficult at launch) is not having a ping, for the majority of the servers I've joined they are running an addon which kicks you for this.

I've found numerous posts on Reddit / forums detailing how to fix this, however they are running these fixes (and the installs) with Lutris and not Steam+Proton.

Just for clarification, I did try the fix on WineHQ and @Cherser-s suggestion but my ping is still missing/the issue remains.

[tunanachos]

Replying to #3994 (comment)

No and unfortunately there doesn't seem much interest in fixing the issue. if your total playtime is under 2-hours I sincerely suggest refunding and buying one of the other battlefields.

[sigzegv]

The setcap issue is explained here https://www.reddit.com/r/linux_gaming/comments/gc5qss/wine_and_ping_support_on_ubuntu_a_guide/

But this solution doesn't work for me either in my ubuntu 20.04, I tried to link the custom proton-ge's libwine.so I'm using in steam to the ld.conf.so.
So from what I understood is that could be solved by a spefic way to build wine. Does somebody have such build ?

[sigzegv]

After reading this #4586 (about ping issue), I tried to run bf4 from a windows steam with a lutris wine build, and after running the setcap trick on the lutris wine's binaries, it seem that ping works ingame. So the only workaround for BF4 and ping issue is to not use Proton.

[nowburp]

Installed yesterday and ootb was getting ping
but also getting kicked after 3-4 minutes by punkbuster.

Today I tried to manually reinstall (and update) punkbuster
with the:
WINEPREFIX=$HOME/.steam/steam/steamapps/compatdata/1238860/pfx wine pbsetup.exe
trick
and it broke my ping.

So I removed the proton prefix
and also moved the game (from within steam) from spinning rust to ssd
had it performed the origin and punkbuster setup
and still got no ping
(so actually worse than yesterday :))

I've tried various "setcap cap_net_raw+epi" solutions
also symlinking the used wine* files to my /etc/ld.so.conf

also tried various proton versions

I'm on Debian 10

if anyone has suggestions let me know

[sigzegv]

As it's said on my previous post, ping doesn't work with proton either with setcap trick, you must run the game directly from a wine build (lutris or wine-tkg as example)

[nowburp]

As it's said on my previous post, ping doesn't work with proton either with setcap trick, you must run the game directly from a wine build (lutris or wine-tkg as example)

I hear you mate but there are plenty of ppl here playing it with proton:
https://www.protondb.com/app/1238860
perhaps those are old reports and it broke recently ?

[sigzegv]

no idea if a distrib issue or a regression, I know many people is playing without the ping on servers that dont' kick for that. Fact is that proton is now bothering with setcap trick.

[Cherser-s]

Interesting, after latest Wine update I can't get Origin working, and it simply hangs while trying to connect to some api server for eternity, if I have capability cap_net_raw+epi on wine-preloader (32 bit version). If I remove this, Origin launches fine, but I think I won't be able to connect to Punkbuster servers.

I simply get winsock error 10035 infinitely, this probably is connected to Origin updater checking, if new version is available.

[TheGreatestJannet]

Has anyone found a fix yet for the ping issue that doesn’t require running Windows Steam in wine though Lutris? I was thinking of buying the game but if the ping issue means it doesn’t work in proton it might not be worth it.

[tunanachos]

Has anyone found a fix yet for the ping issue that doesn’t require running Windows Steam in wine though Lutris? I was thinking of buying the game but if the ping issue means it doesn’t work in proton it might not be worth it.

Don't buy it. I spent ages trying to fix it and couldn't. You'll be kicked from 95% of the multiplayer servers because of some stupid add-on most of them run.

[GloriousEggroll]

looks like a patch for the ping issue was proposed last night:
https://source.winehq.org/patches/data/207990

Here's a proton-ge test build with the patch, i was able to play for about 45 min in multiplayer without issue (completed a match start to finish):
https://drive.google.com/file/d/189Y7Khlpeti-1vLiNbWPYV7X-OTAIOxG/view?usp=sharing

[tunanachos]

Replying to #3994 (comment)

Not to try and insult you by asking this, but are you 100% sure you were playing on a server that has this issue?

I'm sure you're right correct and it's working - I just thought I'd double check before getting my hopes up.

Still, that being said I guess that only goes to prove the old adage about the internet; "if you want the answer to something don't ask for it, Instead post the wrong answer and someone will correct you almost immediately" 😛

[sigzegv]

I can confirm the Proton-6.11-GE-1 fixes the issue. I tried it, ping displays nicely, sometimes it takes some couple of seconds to be refreshed and displayed, but it definitely works.

[Sturmlocke86]

looks like a patch for the ping issue was proposed last night:
https://source.winehq.org/patches/data/207990

Here's a proton-ge test build with the patch, i was able to play for about 45 min in multiplayer without issue (completed a match start to finish):
https://drive.google.com/file/d/189Y7Khlpeti-1vLiNbWPYV7X-OTAIOxG/view?usp=sharing

Found this conservation by randomly googling the subject and just created a Github account in order to provide feedback for this type of thing. Going to test your new 6.11 build tonight and report back asap. In any case, thanks for taking the time to fix this issue in ProtonGE. My family and friends have moved over to Ubuntu / Suse / Fedora Linux and we all just bought BF4 on Steam a couple of days ago. Your timing is perfect in our case. Looking forward to the official release.

Cheers

[Sturmlocke86]

Update: Ok, just played online a couple of rounds: no kicks whatsoever, ping was shown just fine. Worked like a charm.

[Cherser-s]

Interesting, this patch doesn't work for me (in vanilla wine version, that is), if I don't enable raw sockets capability for wine binary files.

I've ran wine ping commands to test this patch.
In the case if I enable those capabilities, then Origin just doesn't start and hangs, looping through some crypt32 calls or something like that. The same happens, if wineserver is already running (regardless of capabilities being set).

UPD: I allowed unprivileged ICMP requests for my user by sysctl. Also Origin started working somehow and doesn't hang just as in case with setcap, so I could start bf4 and play multiplayer with working ping. Though Origin still hangs at the start in case if wineserver wasn't initiated by Origin executable. Something isn't right with Origin itself probably.

[Sturmlocke86]

Another update: The game is still working just fine ping-wise (with ProtonGE 6.11), but I noticed a different issue.

The game stutters heavily every second or two when playing online. I checked ProtonDB and noticed that there are other users with the same issue. I've tried a bunch of the suggested workarounds (-notexturestreaming, gamemode, turning off bandwith optimization etc.), unfortunately to no avail.

According to one ProtonDB report (from the user "Arge"): "Origin, when being online, seems to heavily stutter this game (as well as Battlefield1 via Lutris) exactly every single second. If one manages to launch the game with the chat of Origin being offline, this stutter doesn't exist."

Is anyone else experiencing the above? I am able to confirm the issue on two separate machines, one equipped with an RTX 2080 Super. OS: Ubuntu 21.04 and 20.04.2.

Thanks!

[TheGreatestJannet]

Are you sure it isn’t compiling shaders? On my Arch Linux i5 6500 and GTX 1060 6GB machine, it does stutter online but not as frequently as every 1 or 2 seconds.

[BETLOG]

Should proton logs include the games' proton compatdata setup/install? Or just the game start>fail>exit?

[BETLOG]

It works fine for me using Proton Experimental and Proton 8.0-2

You got my hopes up.
It seems I have been using the beta steam client for so long I forgot. Now reverted to standard steam.
I'm surprised this log is half the size of the prior one i gumby-posted, even though this one also includes the container/EA/PB/DX setup.
Still fails to get beyond a dead BF4.exe window though.

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

Maybe it is unrelated, but the way the initial install sequence interrupts mouse/keyboard at random intervals seems to be a direct indicator that the resulting install will fail to launch the game.

[gmod64bit]

I havn't been able to play battlefield 4 in like 8 months. I really miss my favorite game.

Every proton version.
Every GE version.
Deleting compatdata between each runner.
Arch, void, devuan, nothing works.
Log: https://mega.nz/file/H6YGRAzL#8JszUvfGQ8neYFy8Og039MLqTYtEmCI3STJh_oTJpnY

[BETLOG]

Two things that are clearly not intended function and did not appear until a few months ago:

1. Contrast increases after exiting menu (no changes made).
2. Settings "save changes" dialog appears, despite no changes being made.

proton 7.0-100
(because 8.x cant even start the game)

Steps to reproduce:

• start bf4
• join online game/create 'test range' session.
• spawn/Deploy
• note contrast
• hit escape (menu appears)
• select 'options'
• do not click anyhting
• hit escape twice (menu disappears, return to game)
• note contrast has increased

This is extremely tedious, the game is already overly black in scenes where nothing could ever be THAT black, and if i dare enter a menu everything is suddenly even darker.

2023-05-23--23-24-42.094_Battlefield4_h264-qp18_00.00.14.932-00.00.31.698_reStream_H264-veryslow.mp4

PROTON_LOG=1 %command%
https://drive.google.com/file/d/1TBxD1NRzjknbUgSVOcgkL9jzypFXk15l/view?usp=sharing

[alasky17]

@BETLOG I have 2 suggestions to try for the 8.0 issue you are seeing. 1) Could you try changing/lowering the level of focus loss prevention in the KDE settings? The setting is under Window Management -> Window Behavior. and 2) Could you try Proton - Experimental? For this test, please delete (or move) the prefix first just in case a new prefix works better :)

[BETLOG]

[edit] it looks like your responses may have been related to #3994 (comment) In which case, no, i cant test with proton experimental, nor any 8 series proton.
I assumed it was a response to: #3994 (comment) (dead black window under 8-X proton)

@alasky17

1. Could you try changing/lowering the level of focus loss prevention in the KDE settings?

Changed from low, to none. All other settings in window behaviour>focus are unchanged (defaults).

2. Proton - Experimental

ok, 8.0-102

please delete (or move) the prefix first

Always.

... Same result. Dead black window with titlebar.

PROTON_LOG=1 %command%
https://drive.google.com/file/d/1BGO9SUCzINFg_xpswTPguwy1HGkk2MWr/view?usp=sharing

[BETLOG]

Correction: I CAN run 8-series proton; but it's not a steam proton:
1685831131 TKG-proton-experimental.bleeding.edge.8.0.45426.20230602

I am still unsure which issue you asked me to disable focus stealing prevention for, but the above proton:

• DOES darken-after-menu
• Does NOT dead-blackscreen-window on game launch.

[dreamcat4]

This original report was for NVIDIA gpu, proton version 5.0... so things have come a ways since then.

Today the game is running for me on AMD 5700xt, with KDE Plasma. And so is the EA App.exe too (the origin launcher, multiple exes).

Here is a gist with some supplementary infos. Which shows

a) proton version
b) how to check if ipv6 is enabled state and/or re-enables ipv6 (to do that before launching the BF4 game in steam
c) the names of the background processes. For EA App. What are the exes being launched.

Can confirm (like others)

• Version 8 or proton / wine / GE edition - the game will not display any video output. It just presents an entirely black screen. The game is running, but you cannot see anything, it's al blacked out.
• Wheras Proton 7.0.-6 works
• If you mess up, then need to go and delete this folder: YOUR_STEAM_GAMES_DATA_FOLDER/steamapps/compatdata/1238860

Since that ^^ compatdata/STEAM_GAME_ID folder (=1238860 for BF4). Then this is where proton gets copied into (whenever you change proton versions). And its also the folder where EA auto downloads both the Punkbuster updates (for anti cheat, it works). And also where EA downloads it's EA App.exe launcher programs into.

• If you are running pipewire, and node.autoconnect = false. Then you need to keep connecting up the audio device probe nodes being created.

Which is probing for your surround sound, in game headset. etc. In fact multiple DIFFERENT executables will be doing this probing over and over again (in turn, as the EA app first loads up, then a 2nd or even 3rd launcher app, then finally the BF4.exe game itself.

Anyhow this is all just to say, if the game is launching, and nothing is happening. Then maybe it is probing for audio under wine. And then the loading stages will not progress, until those audio stream endpoints have been connected (at least some of them, to satisfy the probing routine). And the EA App still does take a long time to load up (in the background).

What could NOT confirm:

• IPV6 situation for EA App.

Whether or not it is in fact needed to enable IPV6. (If you have a system with IPV6 disabled, many of us do). This is because i was trying multiple things at the same time. However 1 of the 2 things Was indeed to re-enable IPV6 networking using the sysctl command shown in my above gist. Since I happened to boot with kernel flags disabling the ipv6.

So after getting over obstacles, as of TODAY. Both EA App (Origin launcher things) + BF4 game itself. Seems to be running / works. And I did not observe any obvious bugs or glitches or crashing. Perhaps it might crash in the background after exiting I cannot remember. But in all other respects... seems to work with the other details provided as per my gist / pastie details.

[dreamcat4]

This is not to say the bug should be closed. Because it still needs to get to bottom of fixing for proton8... that new breakage: gettting the black screen for ANY Proton versions 8 and above. (or wine 8+). Whatever broke it.

Until then, we remain stuck on proton 7.0-6 for this game. (Maybe similar other EA games too, IDK)

[Blisto91]

I'm unsure how to reproduce the black game screen issue.
I've tried with both radv 23.1.0 and git on proton 8.0-2 and Experimental. Also Both fullscreen and Windowed mode. But it's been fine so far.
This is with a 7900xtx

[dreamcat4]

would like to help, and go back to double check. unfortunately did not make proper note of blackscreen exact precise proton 8 version today... i should have. but failed to do this.

having just gotten it working, am now loathe to break it again.

[Blisto91]

@BETLOG Are you also using flatpak?

[BETLOG]

• The game is running

Mine isn't. Or at least it produces no audio that would indicate it running, and yeah: black screen.
Pulseaudio

I'm unsure how to reproduce the black game screen issue.

[edit] wait, no, disregard this. TKG is the only 8.x that works for me
Try an 8-series TKG
https://github.com/Frogging-Family/wine-tkg-git

@BETLOG Are you also using flatpak?

no.

having just gotten it working, am now loathe to break it again.

Just rename the compatdata/<gameId> folder to keep it safe and copy/rename it back after testing.

I can confirm that it works fine for me as well, using Proton 7.0-6

Yes, we know that. It's 8-series that the recent reports are talking about.

[Blisto91]

Is the black screen also present when using wined3d?

[dreamcat4]

if the TKG build works, and other types of the proton-8 [and/or GE,Experimental,beta]. Then is it worth examining the TKG build options. Or asking the TKG maintainer for comment? To try to understand what might be needed to transfer from TKG to other versions (for GE or steam's own official proton).

[Blisto91]

Ideally i need to be able to reproduce the issue first.

Does the issue go away in regular Proton when you use wined3d?

[BETLOG]

Does the issue go away in regular Proton when you use wined3d?

I haven't responded to this query becasue I have never used wined3d afaik, and I'm not sure how I would even go about that. From memory its a proton argument, but googling it is an SEO wasteland of windows references.
[edit] ... UNTIL isearch for proton AND wind3d...doh
PROTON_USE_WINED3D=1 %command%

[Blisto91]

Ye thats the one. Sorry should have written it. Made an assumption that it was already known.

[BETLOG]

I'm tired, so I might have the dumb and not be able to brain, but I wasnt expecting this to fail in less than 3 seconds:

remove compatdata/1238860
set proton 8.0-2
PROTON_USE_WINED3D=1 %command%

didnt even start EA, just immediately ended

Proton: Upgrading prefix from None to 8.0-101 (/home/user/.steam/steam/steamapps/compatdata/1238860/)
Traceback (most recent call last):
  File "/home/user/.steam/steam/steamapps/common/Proton 8.0/proton", line 1636, in <module>
    g_session.init_session(sys.argv[1] != "runinprefix")
  File "/home/user/.steam/steam/steamapps/common/Proton 8.0/proton", line 1431, in init_session
    g_compatdata.setup_prefix()
  File "/home/user/.steam/steam/steamapps/common/Proton 8.0/proton", line 789, in setup_prefix
    os.symlink("../drive_c", self.prefix_dir + "/dosdevices/c:")
FileNotFoundError: [Errno 2] No such file or directory: '../drive_c' -> '/home/user/.steam/steam/steamapps/compatdata/1238860/pfx//dosdevices/c:'
GameAction [AppID 1238860, ActionID 1] : LaunchApp changed task to SynchronizingControllerConfig with ""
GameAction [AppID 1238860, ActionID 1] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 1238860, ActionID 1] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 1238860, ActionID 1] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 1238860, ActionID 1] : LaunchApp continues with user response "CreatingProcess"
/bin/sh\0-c\0PROTON_USE_WINED3D=1 /home/user/.steam/ubuntu12_32/reaper SteamLaunch AppId=1238860 -- /home/user/.steam/ubuntu12_32/steam-launch-wrapper -- '/home/user/.steam/steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/user/.steam/steam/steamapps/common/Proton 8.0'/proton waitforexitandrun  'link2ea://launchgame/1238860?platform=steam&theme=bf4'\0
Game process added : AppID 1238860 "PROTON_USE_WINED3D=1 /home/user/.steam/ubuntu12_32/reaper SteamLaunch AppId=1238860 -- /home/user/.steam/ubuntu12_32/steam-launch-wrapper -- '/home/user/.steam/steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/user/.steam/steam/steamapps/common/Proton 8.0'/proton waitforexitandrun  'link2ea://launchgame/1238860?platform=steam&theme=bf4'", ProcID 1332337, IP 0.0.0.0:0
chdir "/home/user/.steam/steam/steamapps/common/Battlefield 4"
ERROR: ld.so: object '/home/user/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 1238860, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""

(steam:1331648): GLib-GObject-CRITICAL **: 22:45:57.073: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(steam:1331648): GLib-GObject-CRITICAL **: 22:45:57.073: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
GameAction [AppID 1238860, ActionID 1] : LaunchApp changed task to Completed with ""
Proton: Upgrading prefix from None to 8.0-101 (/home/user/.steam/steam/steamapps/compatdata/1238860/)
Traceback (most recent call last):
  File "/home/user/.steam/steam/steamapps/common/Proton 8.0/proton", line 1636, in <module>
    g_session.init_session(sys.argv[1] != "runinprefix")
  File "/home/user/.steam/steam/steamapps/common/Proton 8.0/proton", line 1431, in init_session
    g_compatdata.setup_prefix()
  File "/home/user/.steam/steam/steamapps/common/Proton 8.0/proton", line 789, in setup_prefix
    os.symlink("../drive_c", self.prefix_dir + "/dosdevices/c:")
FileNotFoundError: [Errno 2] No such file or directory: '../drive_c' -> '/home/user/.steam/steam/steamapps/compatdata/1238860/pfx//dosdevices/c:'

(steam:1331648): GLib-GObject-CRITICAL **: 22:45:58.261: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(steam:1331648): GLib-GObject-CRITICAL **: 22:45:58.261: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Game process removed: AppID 1238860 "PROTON_USE_WINED3D=1 /home/user/.steam/ubuntu12_32/reaper SteamLaunch AppId=1238860 -- /home/user/.steam/ubuntu12_32/steam-launch-wrapper -- '/home/user/.steam/steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/user/.steam/steam/steamapps/common/Proton 8.0'/proton waitforexitandrun  'link2ea://launchgame/1238860?platform=steam&theme=bf4'", ProcID 1332337 
ThreadGetProcessExitCode: no such process 1332490
ThreadGetProcessExitCode: no such process 1332340
ThreadGetProcessExitCode: no such process 1332339
ThreadGetProcessExitCode: no such process 1332338
Uploaded AppInterfaceStats to Steam

(steam:1331648): GLib-GObject-CRITICAL **: 22:45:58.443: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(steam:1331648): GLib-GObject-CRITICAL **: 22:45:58.443: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(steam:1331648): GLib-GObject-CRITICAL **: 22:46:00.288: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(steam:1331648): GLib-GObject-CRITICAL **: 22:46:00.288: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[2023-06-19 22:47:37] Background update loop checking for update. . .
[2023-06-19 22:47:37] Checking for available updates...
[2023-06-19 22:47:37] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12?t=9035574
[2023-06-19 22:47:37] Manifest download: send request
[2023-06-19 22:47:37] Manifest download: waiting for download to finish
[2023-06-19 22:47:38] Manifest download: finished
[2023-06-19 22:47:38] Download skipped: /steam_client_ubuntu12?t=9035574 version 1686880776, installed version 1686880776, existing pending version 0
[2023-06-19 22:47:38] Nothing to do

[BETLOG]

Question:
My system seems very capable of producing a stable 120fps, and yet despite my conservative low to medium game video settings, and some user.cfg tweaks, it mostly only does 90-100fps.
Notably: whenever I'm in a server with less than about 20 players I get an almost completely unwavering 8ms frametime (120Hz), but otherwise its fluctuating near 30-10ms (30-100fps).
Significantly less than 50% of my CPU/GPU (like: ~30%) are ever used.

What's with that? and how can I fix it?

Typically i precede %command% with:

qdbus org.kde.KWin /Compositor suspend
sudo cpufreq-set --related --governor performance

export PROTON_ENABLE_NVAPI=1 # compulsory for FrostByte
export WINE_CPU_TOPOLOGY=3:0,1,2 # this seems to easily encapsulate bf4's requirements on this 8C/16T system
export DXVK_FRAME_RATE=120 # specific HDMI screen max
export DXVK_HUD=frametimes,compiler,fps
export DXVK_ASYNC=0 # i *was* using it prior to GPLibrary, so my gamewrapper script still has it as an option
export WINEFSYNC=1 # uwu
export vblank_mode=1
nvidia-settings -a SyncToVBlank=1
nvidia-settings -a OpenGLImageSettings=3 # performance
nvidia-settings -a AllowFlipping=0 # required by x11grab for desktop recording

dxvk.conf

dxgi.customVendorId = 10de
# RTX 2060 Tuff

user.cfg

GameTime.MaxVariableFps 121
RenderDevice.ForceRenderAheadLimit 3
RenderDevice.TripleBufferingEnable 0
WorldRender.MotionBlurEnable 1
WorldRender.MotionBlurRadialBlurMax 0.06
WorldRender.MotionBlurQuality 0
WorldRender.MotionBlurMaxSampleCount 20
WorldRender.DxDeferredCsPathEnable 1
WorldRender.FxaaEnable 0
WorldRender.SpotLightShadowmapEnable 0
WorldRender.SpotLightShadowmapResolution 256

[BETLOG]

The ping / setcap issue is still a thing.
#3994 (comment)
#3994 (comment)

Solution:
sudo sysctl net.ipv4.ping_group_range='1000 1000'
Seems to be a debian and derivatives issue only (I'm Kubuntu 23.04)

This also solves the no-ping issue on battlelog web server browser

[dreamcat4]

Perhaps a (slightly) better way... to add your user account to a new;y created ping group:

sudo groupadd ping
sudo usermod --append --groups ping $USER
GID="getent group ping | cut -d":" -f3"

# to enable for this session only
sudo sysctl "net.ipv4.ping_group_range = $GID $GID"

# to make persistent across system reboots
echo "net.ipv4.ping_group_range = $GID $GID" | sudo tee -a /etc/sysctl.conf

However in have not actually tried this myself yet... (but in theory according to the kernel docs, for how it's supposed to work).

[develcooking]

so I tryed everything i could find i used proton 7.0-6; proton experimental; proton ge 8-11

I tryed to run it stock
I tryed to run it in gamescope
I enabled my ping group

but I always get an purple box with nothing in it

Has anyone an idea what i still can try out?

Info to my setup
My window manager is hyprland

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: ROG STRIX B450-F GAMING II
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 5800X 8-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5488 MHz
16 logical processors
8 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.4.10-arch1-1
X Server Vendor: The X.Org Foundation
X Server Release: 12301002
X Window Manager: wlroots wm
Steam Runtime Version: steam-runtime_0.20230606.51628
Video Card:
Driver: AMD AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.52, 6.4.10-arch1-1)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.5
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 164 Hz
VendorID: 0x1002
DeviceID: 0x731f
Revision Not Detected
Number of Monitors: 3
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 5760 x 1155
Primary Display Size: 20.47" x 11.42" (23.43" diag), 52.0cm x 29.0cm (59.5cm diag)
Primary VRAM: 8192 MB
Sound card:
Audio device: USB Mixer
Memory:
RAM: 31992 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: C.UTF-8
Total Hard Disk Space Available: 805253 MB
Largest Free Hard Disk Block: 716024 MB
Storage:
Number of SSDs: 0
Number of HDDs: 0
Number of removable drives: 0

[solenum]

Just getting 'the app timed out' trying to launch this. Normally works for me, but then this problem starts and I have to spend 30 minutes faffing around with Proton versions and stuff, deleting the prefix and then running with Proton 7 to let the eac app install, and then switching to experimental works, but then I'll try to play the following day and I'll have the same issue and have to spend another 30 minutes faffing around to get past the ea app 'the app timed out' error.

After I finally get it working, I can play a match for a few mins before being booted for some Punkbuster issue. Also sometimes I stop and start the game after it had been working again, and then simply trying to start the game again leads me to the same "the app timed out" error. Super inconsistent and frustrating.

Edit; Disabling fsync appears to solve the punkbuster issue (so far), but the rest of the issues persist.

[JustCauseWhyNot]

I'm getting similar behavior as I am with gta iv. The game launches, and then a window never opens. Here's my steam-1238860.log.

[mmmsalmon]

The audio disappears and reappears from time to time, sometimes music starts and repeats again and again when loading. PULSE_LATENCY_MSEC=90 %command% is likely most relevant to this issue but it didn't fix it for me.

[frmdstryr]

As of the last steam client update the game no longer starts on the primary monitor.

[DaforLynx]

I get to the EA App opening very briefly before immediately closing. Tried many different Proton versions including the GE version which runs the app fine in Lutris. No dice.