I too have this issue. If switching to GE does not work after it is installed, you need to delete the pfx for the game, then launch it again before switching over again to proton experimental (makes it easier to log in).

Running Proton Experimental and the launcher will launch, but I'm having problems inserting login credentials.

Deleting the pfx and switching to the latest GE (6.20.1) doesn't work for me, the game just won't launch. It may have something something do with running Wayland, but I can't be bothered to switch to XOrg.

IME, the launcher gets stuck at the black screen (which I think is the non-interactable loading screen) on wayland (sway) and doesn't even load the launcher correctly.

Proton-GE 6.20 loads the launcher just fine on Xorg and hangs on Wayland.

The launcher seems to be using CEF.

Can anyone reproduce the issue with Freesync https://github.com/ValveSoftware/Proton/issues/5314?

Freesync running at half rate when framerate is above native refresh rate in Planetside 2 (and possibly some other games)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5314.
@Atemu posted on 2021-11-13T16:29:40:

Compatibility Report

• Name of the game with compatibility issues: Planetside 2
• Steam AppID of the game: 218230

System Information

• GPU: RX 570
• Driver/LLVM version: Mesa 21.2.5
• Kernel version: 5.14.16-lqx1
• Link to full system information report as Gist: https://gist.github.com/Atemu/25baf10cbaf6db2ecf1492acbf237c3c
• Proton version: Experimental

Atemu/Nixpkgs@f8e92efb576a88d9b687499425cb0ac3cf170a62
Atemu/nixos-config@d7066af064997845240f63f469552faabfd04951

I confirm:

• [ ] 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.

steam-218230.log.zip

Symptoms

When controlling the character in-game and when the FPS are above or close to 144, my monitor drops to 1/2 refresh rate (so, 80Hz for 160fps for example). This is very unexpected and ruins responsiveness.

The bug does not happen in the loading screens weirdly (not just because of the higher framerate though).

I've only found one instance of another user experiencing this: https://www.reddit.com/r/linux_gaming/comments/p5lxzv/freesync_setting_refresh_rate_to_half_the_fps/

I don't own the games they've had issues with, so I can't confirm their findings but I thought it'd be better to keep this bug separate from Planetside 2 compatibility.

Reproduction

1. Have a Freesync monitor with LFC
2. Start game
3. Log in and launch using the workaround described in https://github.com/ValveSoftware/Proton/issues/5295
4. Select a character and press play
5. Have a framerate greater than monitor refresh rate
6. Open monitor OSD and observe refreshrate being roughly 1/2 of the fps

Running Proton Experimental and the launcher will launch, but I'm having problems inserting login credentials.

Deleting the pfx and switching to the latest GE (6.20.1) doesn't work for me, the game just won't launch. It may have something something do with running Wayland, but I can't be bothered to switch to XOrg.

I was able to get the launcher to initialize by first running the game with Proton Experimental and a fresh pfx. Then I used Proton-6.20-GE-1 to login (with the same pfx), and switched back to Proton Experimental for play (while guessing where the start button is).

Proton-6.21-GE-1 was just released today with patches for Battleye, which if they work correctly, should remove the requirement of Proton Experimental for play. EDIT: It looks like in Proton-6.21-GE-1 the launcher no longer works. Perhaps this is related to/ broken due to Battleye support specifically? (Due to Proton GE being a custom fork, this is really just speculation and probably doesn't apply to Proton.)

Not sure if there are issues specific to Wayland as I run Xorg.

Can anyone reproduce the issue with Freesync #5314?

Freesync running at half rate when framerate is above native refresh rate in Planetside 2 (and possibly some other games)

Unfortunately since I run NVIDIA I don't think my experience is of much help, however I have not noticed issues related to VRR in any Proton games as of yet (Including in Planetside 2).

Unfortunately since I run NVIDIA I don't think my experience is of much help

No, it is!

It working fine for you, that would single out the AMDGPU implementation of VRR.

I have not noticed issues related to VRR in any Proton games as of yet (Including in Planetside 2).

Could you open the monitor's OSD in-game and specifically check that the refresh rate is at max (i.e. 144Hz) when framerate > refresh rate?

Does your monitor support LFC?

Could you open the monitor's OSD in-game and specifically check that the refresh rate is at max (i.e. 144Hz) when framerate > refresh rate?

The refreshrate is as expected (144hz when >144hz) when looking at the monitor's OSD.

Does your monitor support LFC?

Not that I am aware of, I double checked the specs online but see no mention of it (must be a feature that was standard/available slightly after I got this one.)

See: Section 3.2

Thank you!

LFC smells like the most likely culprit then. Could anyone with an LFC-capable monitor chime in?

Just moved this post here.
Native Proton Exp builds have a issue with it's launcher and will display a white or black box. (you can still blind click areas to activate stuff)

When I tested it I used protonGE6.8 to install as it solved the launcher issue, then I switched to proton-exp and launched the game (blind click) and it worked fine.
Hopefully launcher fixes start getting applied to mainline proton more such as this one and the BSG launcher of Tarkov (it requires dotnet48 and wined3d to see atm unfortunately).

I don't think dotnet is needed for EFT, just some mono patching and dxvk fixes to render launcher correctly.

With proton-ge 6.21, if you remove your prefix, then run the game, the launcher renders fine. i tested it yesterday.

With proton-ge 6.21, if you remove your prefix, then run the game, the launcher renders fine. i tested it yesterday.

Yes this is true, however Valve should REALLY look into patching in fixes to make all these 3rd party launchers work in normal Proton so new users of steamOS or Linux are not confused.

Not everyone is going to automatically use GE, and GE doesn't always offer the best experience for all games. (FO76 for me is unplayable in GE due to stutter bug for example)

Replying to https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-969732642

My response was not with regards to what Valve should or should not do. Valve work very hard to get as many fixes as possible in. My response was specifically because you mentioned using proton-ge to get the launcher working, and normal proton to run the game:

When I tested it I used protonGE6.8 to install as it solved the launcher issue, then I switched to proton-exp and launched the game (blind click) and it worked fine.

I was simply pointing out that a fix existed as far back as ProtonGE6.8

@GloriousEggroll did you notice any issues with VRR like the one I mentioned?

(Roughly) how is BE implemented? Could running your fork upset it somehow because it's not official Proton?

I am having trouble with mouse input on Sway+Wayland
Proton GE 6.21GE2
The mouse input is extremely laggy and jittery
However the touchpad works fine
Turning on/off raw input doesnt change anything

EDIT: fixed after reboot

The launcher worked in 3.7-8. If you force that version to login and enable autologin, you only have to guess the location of the play button in Experimental. For now that's a manageable workaround for me.

If I launch Steam from a terminal I also see these errors when the launcher window appears:

[1126/073606:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073606:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073606:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073606:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073606:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073622:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073622:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073622:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073622:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073622:ERROR:gl_surface_egl.cc(697)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[1126/073622:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/073623:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/073624:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/073628:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/073630:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/073630:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED

The errors appear in 2 bunches when the windows is black and the warnings appear as the window turns white.

AMDGPU on an RX 5500 XT connected over DP to an Acer XV340CKP. FreeSync enabled and the display has LFC.

I can't find LFC in the settings right now but a quick test in PlanetSide 2 indicates it's enabled as the monitors own FPS indicator suddenly jumps up to over 100 FPS when the framerate dips (it also feels like the framerate jumps back up just by looking at it).

What happens when your FPS are greater than your refresh rate in-game? (not loading screens!)

What happens when your FPS are greater than your refresh rate in-game? (not loading screens!)

I assume you meant me? Nothing unusual as far as I can tell. Found a wall on Sanctuary where I consistently got over 160 FPS and the monitor just reports steady 144 Hz on the OSD (shows the actual post-LFC refresh rate when FreeSync is enabled).

The only quirky thing I've found at all in-game is setting resolution scaling to 92% or less gives great performance and 93% or higher is a slideshow. Feels like it's hitting the size limit of some buffer but that's just speculation. Other than that it's just like I remember it running on Windows 10. I'll see if I can verify the bug in Windows 10, just to make sure it's not an issue in the game itself.

Thanks! We've now ruled out LFC being the unconditional cause. Only need feedback from another AMDGPU + LFC user now.

Another issue I've found is that the launchpad process seems to linger around after the game was closed, making the game stay in "running" state. Does that happen to you guys too?

Repro:

1. Launch game through launcher
2. Press exit when in the character selection screen
3. Observe game running state in Steam

@Atemu Doesn't seem to happen for me. If I click exit right after the character selection screen comes up, the game closes and after a few seconds the STOP button in the Steam library changes into PLAY again. So everything seems to function as expected. Anything I should look for in the logs for you?

P.S. Tried to confirm the 93% resolution scaling slideshow issue in Windows, didn't happen there so I'll need to do some further debugging on it. Current hypothesis is something makes it run out of VRAM in Debian Sid but not in Windows 10.

According to a user on protondb, adding --disable-gpu solved the launcher issue.

Compatibility Report

• Name of the game with compatibility issues: PlanetSide 2
• Steam AppID of the game: 218230

System Information

• GPU: AMD A6-6310 APU with AMD Radeon R4 Graphics
• Driver/LLVM version: Mesa 21.0.3 / LLVM 12.0.0
• Kernel version: 5.4.0-91-generic
• Link to full system information report as Gist
• Proton version: Experimental

I confirm:

• [ ] 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.

Here's the Proton log: steam-218230.log.gz

Symptoms

I'm using Ubuntu 20.04 with the MATE desktop on an HP 15-af116nt Notebook. I tried to play to Planetside 2, everything seems to have been installed correctly but when I click on "Play" after logging in, I repeatedly get a "Failed to create DXGI Device" error as the attached screenshot shows and I can't get to the game. I enabled Beta participation and Steam Play. The specs of my machine are probably too weak for the game, but still, this error doesn't seem normal.

Also when I closed the window my browser opened a page displaying the following:
"Game Error G2
Malfunction:

There is a problem with your computer's audio. Please update the drivers and try again."

Please note that I have no sound problems on my box other than apparently that.

Reproduction

Launch the game, log in then wait

.

Hey @kisak-valve thanks a lot for your help. I appended
|radeon.cik_support=0 amdgpu.cik_support=1| to the
|GRUB_CMDLINE_LINUX_DEFAULT| parameter of |/etc/default/grub| with nano.
Then I issued a |sudo update-grub|. I also did a
|sudo apt-get install mesa-vulkan-drviers| then rebooted.

Then when I tried to log in, I saw a black screen as described in the
comments above, which was solved by adding |--disable-gpu| to the launch
parameters of the game.

The game is now playable, but I need more RAM :) Thanks again.

One problem I have noticed is that using the microphone is patchy. I'm on Fedora 35 with Pipewire which might be causing problems. You can reproduce this by going into the Voice settings and clicking "Record" under Microphone Test. Then, speak for more than a few seconds, and listen back to your recording, and it'll cut off after about the first 1-2 seconds.

Voice chat in other apps like Discord works fine for me.

• Steam AppID of the game: 218230

Hi @kisak-valve I am not starting a new report because I think I have a very similar issue to @cardpuncher. I get the same "Failed to start DXGI device" error on ubuntu". I am on a new chipset though, Zen family AMD Ryzen 5 3600X 6-Core Processor and and GeForce RTX 2070 SUPER gpu. I have confirmed mesa-vulkan-drivers are installed and updated. I assume I need to append something to the grub parameter, but I am unsure what to do for this chipset.

@PlatanusO you've got an Nvidia card, not an old AMDGPU. The above doesn't apply to you and mesa's Vulkan drivers won't do anything for you; you need the proprietary driver. Look up how to install those and verify they're installed, you need them for any modern game on Linux.

Something is not quite right with the new 7.0 branch. With both Proton 7.0-1 and Experimental 7.0-20220218b the game feels so choppy with so many lags that it looks like a sideshow and is almost unplayable.
The game itself is CPU bound and is known for huge frame drops in larger battles, but even a single frame drop results in a choppy gameplay and the frames drop harder with the 7.0 branch.

I created two logs with roughly 10min of gameplay, one with the current Experimental (same result on the Stable 7.0-1) and one with the Stable 6.3-8d (smooth gameplay even if the fps drop down to mid 20). My system information are here as a Gist.

steam-218230_experimental-7.0-20220218b.log

The log for Proton 6.3.8 is so humongous for 10min gameplay (raw 2,3 GiB, zipped 124,2 MiB) that I had to use MEGA to share it because GitHub didn't let me. steam-218230_stable.6.3-8d.zip

@HolySoap It's working well for me on Proton 7.0-1, also on an AMD GPU. I notice your log you have some custom stuff like gamemode and Mango HUD enabled. Can you try removing those and any other extras you have and see if it helps? Also try turning off logging, sometimes logging by itself can cause performance problems.

Do you play with a controller plugged in, or M&KB only?

@aeikum I only enabled the log for the report.
I cleared the entire launch options, even the --disable-gpu, and same result.
No gamepad connected.

Hm... do you have to get into a particular part of the game to see the problem? I was just going through the tutorial and then wandering around the shared hub area. I'm not familiar with this game.

Hm... do you have to get into a particular part of the game to see the problem? I was just going through the tutorial and then wandering around the shared hub area. I'm not familiar with this game.

Yeah, lol, that's basically no test at all with that game.
Let me quote myself:

The game itself is CPU bound and is known for huge frame drops in larger battles (...)

With large battle battles i mean roughly 100vs100 or 70vs70vs70. If you are in the middle of such a shitshow the fps drop hard VERY HARD down to ~15-20fps, but with Proton 6.3 the frames are smooth, slowdown but smooth. With Proton 7.0 the frames drop harder and that in smaller fights from around 30vs30 and it is a slideshow, not smooth at all and becomes unplayable.

Play in the prime time when the server reaches above 100vs100vs100 players. Check your server here. Then join a map with the most population (one of the five available, NOT the safezone or the weapon training), press J that mostly guarantees you to join the biggest fight otherwise look at the map M yourself, then head to the most people allied or enemy doesn't matter (if you don't get killed on your way of course).

@aeikum might wanna get close to a battle by warping to an active continent and then using join combat to really stress the CPU but I wasn't able to reproduce their issue with 7.0 either (also AMDGPU).

It's probably on your end @HolySoap

@Atemu then how do you explain that 6.3 works perfect but 7.0 doesn't? The only thing that changed is the Proton version.

I don't. All I'm saying is that it works on my machine.

That's why I provided two different logs so someone smart can figure out what's wrong. :)

Hmm... got launcher from white color to normal by adding --disable-gpu to Proton BattlEye Runtime launch options... It was in some topic in steam discussions...
Now I need to restart password as I haven't played for a while...
Edit: This seems unrealiable... getting white screens now again...
Edit2: Added the line to the game now aswell, loading updates...
Edit3: Got in to the game, played a bit (died a lot) and it was my best game until now as there was no problems. First time got to play this on Linux :+1:

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
    Speed:  3900 Mhz
    4 logical processors
    4 physical processors

Operating System Version:
    Pop!_OS 21.10 (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.15.8-76051508-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12013000
    X Window Manager:  GNOME Shell
    Steam Runtime Version:  steam-runtime_0.20211207.0

Video Card:
    Driver:  NVIDIA Corporation NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
    Driver Version:  4.6.0 NVIDIA 510.54
    OpenGL Version: 4.6
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 143 Hz
    Primary VRAM: 6144 MB

Memory:
    RAM:  15961 MB

Alright two updates:

1. My VRR(/LFC?) issue only occurs on Xorg. I tested it with on Plasma, Plasma, i3 and sway. All wayland compositors don't exhibit the issue while Xorg desktops do.
2. I am able to reproduce @HolySoap's issue on Proton 7. When in a large battle, Planetside has insane lag spikes, making it unplayable. 6.8 works just fine. I've noticed that the game's CPU usage rises to over 1000% during these.

It just so happens that when I was looking around for a fix for another CEF based launcher with a white screen I found a way to fix the launcher without passing in --disable-gpu

See: https://github.com/starcitizen-lug/lug-helper/commit/21444076de8b209575770f09892e563cefaef31b

The main takeaway I got from that is that libglesv2 may be the culprit in this instance.

So adding either WINEDLLOVERRIDES=libglesv2= or disabling the library in winecfg solves the launcher issue.

I can also attest to the microstutters and reduced performance with 7.0-1.
Performance seems generally the same as 6.3-8 until you get into a big fight (100-200 players), with FPS drops below 30 and microstutters.

If someone wants to tackle this regression let me know if there is any way I can help.

Greetings everyone, for some reason the launcher always looks like this for me. I am using Proton GE 6.21-2.

When the launcher opens there is a spinning circle over the login menu and then it just changes to this. Any ideas?

Here's the packed log folder: Logs.tar.gz

Cheers

Anyone got CJK input working? I am using fcitx5, which works in all other apps, including Deep Rock Galactic and Risk of Rain 2 which are also in Proton. However, when I try typing chinese in Planetside 2, the characters all appear as ????.

Compatibility Report

• Name of the game with compatibility issues: Planetside 2
• Steam AppID of the game: 218230

System Information

• GPU: RTX 3080
• Driver/LLVM version: nvidia 515.57
• Kernel version: 5.18.9-263-tkg-pds
• Link to full system information report as Gist: https://gist.github.com/Tabascl/c3f09979618c6f77685832c0cfdcbb89
• Proton version: Proton-6.21-GE-2

Symptoms

With Proton GE 6.21 and also using a custom built linux-tkg kernel, the game runs almost as good as on Windows.
Still, 7.24 would yield better even better performance in terms of input latency (very noticeable difference in my opinion). But, as other users have already stated, the lag spikes occuring in large fights render the game unplayable at times.

But I'd like to stress again, for everyone else struggling with this issue, that especially the linux-tkg kernel has improved performance and frametime stability by a lot, on top of everything else.

I get stuck at the INSTALLING step in the launcher, progress bar doesn't start moving and there is little to no disk activity even after leaving it for a long while (15-20 minutes). Same result with both 7.0-3 and Proton Experimental. Worked just fine last time I tried a month or so ago.

I've tried clearing both the PlanetSide 2/LaunchPad.libs/LaunchPad.Cache/Cookies/ directory and the PlanetSide 2 compatdata folder with the same result, for both versions.

Perhaps try GE and see what happens.

@Djhg2000 try Proton 6.3-8

Neither GE 7-24 nor 6.20-1 seems to make any difference. Same thing with Proton 6.3-8. It just sits there, apparently without doing anything.

Edit: I just noticed the "Select Game Version" box in the launcher (press the settings button in the bottom left) is blank, and the dropdown is compressed to less than one item because it's empty. I have no idea if it looked that way before.

The strange part is this has worked fine for months on this exact machine before, ever since Proton Experimental got BattlEye support. Maybe it's some underlying change in Debian Sid?

Edit 2: I've had some progress; using Proton 3.7-8 makes the client start actually verifying the files. I haven't been able to click the PLAY button on a newer version of Proton yet, seems like the graphical glitches are preventing the it from becoming active (up until now I've only been blindly clicking the area where I expect the PLAY button to appear).

@Djhg2000 try resetting your Proton prefix.

@Atemu That didn't seem to work. But 3.7-8 always lets me log in and pass the installing stage in the launcher.

After some random hunting with the mouse cursor I can see that with Proton 7.0-3 I get the link to the error 4-503 support article. The way to solve that one is to clear the two files in the PlanetSide 2/LaunchPad.libs/LaunchPad.Cache/Cookies/ directory, which logs you out of the launcher.

I'm afraid this has turned into a catch 22; if I log in with 3.7-8 I can verify the game files, if I then start it with 7.0-3 (even after clearing the prefix) I have to clear the cookies before I can get past the (supposedly 4-503?) error screen and then it won't verify the game files. I'll try with some other Proton versions and see if I can find a working combination.

Edit: It seems like Proton 3.16-9 is the last version that lets the launcher verify the game files. I've tried a lot of GE builds and even a couple of TKG builds, none of them work.

Comparing the prefixes with the different versions seem to indicate the launcher stores the verification data in <prefix>/pfx/drive_c/users/steamuser/AppData/LocalLow/Daybreak Game Company/Digests/, but copying this and transplanting it back in with a later version prefix seems to either trigger a blank launcher with a login prompt, or if launched with %command% --disable-gpu it hangs at a garbled launcher with no interactive elements.

I also noticed the "Select Game Version" menu in the launcher works perfectly in 3.16-9, with "Live Play" as the only option in the dropdown (as expected when not using the public test version of PlanetSide 2).

Edit 2: Attached some screenshots;

This is what the "Select Game Version" menu looks like with 3.16-9

This is what the garbled launcher looks like with 7.0-3

Edit 3: I tried the flatpak version of Steam too, seems to be the same symptoms. I think this is a much older regression somewhere between the 3.16 and 4.2 branch of Proton that only now became visible (from a launcher update?). Am I understanding correctly that the launcher still works for other Steam users?

If it makes any difference I'm on Debian Sid with a Radeon RX 5500 XT, running the Mesa driver with RADV on kernel 5.18.

So now that I'm back from my trip I tried playing PlanetSide 2 again, and the launcher works flawlessly on the same exact machine. Unfortunately it seems like this bug will stay unresolved for quite some time, I have no idea what caused it or what variable it depends on.

I'm having the same issue as @cardpuncher did where I get a "Failed to create DXGI Device" error leading to the Planetside 2 website where it calls it a G2 error. However, I have an Arctic Islands card (RX 580) with a Ryzen 5 3600X on Debian 11 Bullseye.

mesa-vulkan-drivers is installed for both amd64 and i386.

Sorry this is a day late, but here is the Proton log:
steam-218230.log

I'm having the same issue as @cardpuncher did where I get a "Failed to create DXGI Device"

I had the same problem with the GE-Proton7-29 version, I switched to GE-Proton7-9 and solved it.

The heavy stutter issue still occurs with 7.0-4. To reproduce it, you must enter a semi-large fight with 50-100 players or so. It manifests itself in very long hitches; the game runs just fine and all the sudden there's a lag spike, sometimes multiple.

Proton 6.3-8 is the latest playable version.

I don't have that stutter issue, but I know the recommended GE-proton version to play with is 6.21-GE-2 ( in planetside 2 ofc) .

You don't experience the stutter in which version with what hardware? Are you able to reproduce it with 7.0-4?

You don't experience the stutter in which version with what hardware?

I don't experience the stutter with GE-Proton7-9
Hardware:
Processor: Ryzen 3 3200g
Graphics: Vega 8
RAM: 16Gbx2 3200mhz LPX Vegeance
I'm using proprietary AMD drivers - Arch linux.

And the game doesn't even boots with 7.0-4 lmao xd.

And the game doesn't even boots with 7.0-4 lmao xd.

That's likely because you've used proton-ge. Clear your prefix (Planetside doesn't store anything important in it) and try again.

Yeah, the Proton 7.x series is nearly unplayable for Planetside 2 (with my hardware at least). I am still using Debian so the DXGI error persists for the 6.x proton versions (doesn't occur on other distros for some reason..)

@Atemu Do you have Assassins Creed Origins? I have the VRR issue with that game. Unfortunately I am having difficulty getting the launcher to work even after trying the suggestions here for PS2.

Edit: Not sure if I am just an idiot or some update fixed this since the last time I looked into it. So I fixed this in AC Origins by enabling VSync in game. If VSync is disabled then it sets hz to half FPS. So if VSync is enabled in PS2 and you are still getting half refresh then the issue might be that VSync is somehow not working correctly in PS2. Also make sure it is either Borderless Window or if Fullscreen it is actually set to 144hz in game or whatever it is for your monitor.

For reference I am running...
Proton Experimental [bleeding-edge]
Mesa 22.3.0-devel
Kernel 5.19.0-76051900-generic
Pop!_OS 22.04 (X11)

(Un?)fortunately, I am no longer able to reproduce this issue in Planetside. I have switched to a 6800XT though. What's your GPU @ChaosBlades?

@Atemu 6900xt

In which frame ranges do you experience the issue? It only happened in a certain range for me; IIRC somewhere around 120Hz triggered it.

@Atemu Had to use resolution multiplier to get lower than 120fps. First world problems :). Yes exact same result. hz is half fps at 120hz and higher when I disable Vsync. Below 120fps hz is correctly matched.

Edit: I am remembering myself test this originally now. I remember experiencing this issue on my GTX 1080 and it worked the same. I remember it jump back and forth from a correct value to half fps around 120fps. I want to say Vsync didn't fix it in that instance but I can't say for sure. I figured I would have had to test it but who knows.

@ChaosBlades That sounds like the exact same issue I was experiencing.

Just a hunch but what's your display manager (lightdm, GDM, SDDM etc.) and what display protocol does it use?

@Atemu GDM3 (GNOME 42.3.1) running Pop!_OS 22.04 LTS Only thing I have really changed is I am running the latest mesa as it is developed.

Wayland or X11 in GDM?

X11

Again this is just a hunch but try making it start in wayland mode and reboot.

Assassins Creed Origins runs fine with Vsync enabled. Which Vsync should be enabled when using VRR (common misconception). So your issue that you had with PS2 had to of been either you didn't have Vsync enabled, Vsync was broken in PS2, Protons translation of it was, or your distros implementation was.

Video showing hitching on the latest Proton Experimental (2022/11/16) in a large fight. No improvements from previous 7.x versions.

6.3-8 works fine still.

I can confirm @Fushko's obvservation. It's hard to tell in the video but the bug manifests itself in somewhat infrequent stutters that are each very long.

What could this be caused by? Anything us power users could test to troubleshoot?

Demo with a frametime overlay on Proton 7.0-4.

As you can see, it starts out fine, then quickly gets worse as I approach a fight.

I figured all these videos are useless without some logs. planetside2-proton-7.0-4.log.gz

When the hitching starts, tail -f reveals a whole bunch of these exceptions being printed in quick succession:

22879.320:0278:027c:warn:seh:dispatch_exception EXCEPTION_BREAKPOINT exception (code=80000003) raised
22879.320:0278:027c:trace:seh:dispatch_exception  rax=000000000011bbd0 rbx=00000000961e85a0 rcx=000000017006a380 rdx=000000000001f020
22879.320:0278:027c:trace:seh:dispatch_exception  rsi=00000000961e8440 rdi=0000000000000000 rbp=000000000011bbb0 rsp=000000000011bb78
22879.320:0278:027c:trace:seh:dispatch_exception   r8=0000000000000020  r9=000000000011bab8 r10=00000001434e6878 r11=000000000011c01c
22879.320:0278:027c:trace:seh:dispatch_exception  r12=00000000ffffffff r13=00000001434bc400 r14=0000000000000018 r15=00000000961e8618
22879.320:0278:027c:trace:seh:call_vectored_handlers calling handler at 0000000140B9D421 code=80000003 flags=0
22879.320:0278:027c:trace:seh:call_vectored_handlers handler at 0000000140B9D421 returned ffffffff
22879.375:0278:027c:trace:seh:dispatch_exception code=c000001d flags=0 addr=0000000140EF1869 ip=0000000140EF1869 tid=027c
22879.375:0278:027c:warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised
22879.375:0278:027c:trace:seh:dispatch_exception  rax=000000000011bc18 rbx=00000000961e85a0 rcx=000000017006a380 rdx=000000000001f020
22879.375:0278:027c:trace:seh:dispatch_exception  rsi=00000000961e8440 rdi=0000000000000000 rbp=000000000011bbb0 rsp=000000000011bb78
22879.375:0278:027c:trace:seh:dispatch_exception   r8=0000000000000020  r9=000000000011bab8 r10=00000001434e6878 r11=000000000011c01c
22879.375:0278:027c:trace:seh:dispatch_exception  r12=00000000ffffffff r13=00000001434bc400 r14=0000000000000018 r15=00000000961e8618

@kisak-valve could you please take a look? Thank you very much.

I have a unique issue with planetside 2. Especially in the evenings when the population is high my game freezes and eventually crashes after a few seconds. This happens randomly while playing (sometimes after 15 min in game and sometimes after hours).
I have tried a variety of proton flags and disabling compositing on the window to no avail.

steam-218230-6.3-8.tar.gz
R5 5600g
RX6700XT
Kernel: Linux 6.0.10-zen2-1-zen
proton-6.3-8
EndeavourOS, KDE plasma, X11

Can confirm Severe performance drop when playing on proton 7.0-4 and newer(cpu usage basically doubles).
Proton GE doesn't fix the crashing.

EDIT 221211: The issue seems to have resolved itself by verifying and reacquiring 17 missing files. In the next session i haven't experienced any crashes. The next time my game crashed in the same way i verified the files again and again 17 files were missing. I suspect these 17 files somehow get removed or corrupted between sessions. They are a part of the game files and not proton.
... Crashes still occur

I have noticed that there is much less hitching when the game setting for smoothing is disabled.
That may point to the game's timing measurements being confused by how Proton reports frame completion.
The setting is changed by Settings->Graphics->Smoothing "Caps the frame rate to improve performance consistency."

@stroyan smoothing is working just fine for me.

The smoothing setting is essential for getting good input latency and a slight competitive advantage (higher RoF).

I can imagine that stutters might seem more significant with it enabled with the default framerate of 60 because 60fps is just lower in general. Try setting SmoothingMaxFramerate=90 in the game's UserOptions.ini and see if the stutters are still as significant.

A lot of people are reporting bad frames. Unfortunately for me, I cannot even log into the game. From all of the Proton versions I've tried (from 6.21-GE up to 7.47-GE), the launcher spins for a while, and then a black screen is shown. The black screen is actually a broken website where you can scroll and select text. I am using the %command% --disable-gpu launch options.

This seems like the browser integration in the launcher (CEF) is broken for me and I have no idea why. The only version I've tried where the launcher worked correctly for me was Proton 3.7-8, but if I've read correctly, the anti-cheat won't work with this one.

I am running:
Kernel: 5.15.82-desktop-1.mga8
OS: Mageia 8 x86_64
DE: Plasma 5.20.4 (X11)
OpenGL: 4.6 (Compatibility Profile)
Mesa 21.3.8
Driver: amdgpu

I am attaching the launcher's log folder in case somebody wants to take a look.
Logs.zip

Cheers

@MagicD3VIL try vanilla Proton 6.3-8 with a clean prefix and validate game files.

@Atemu I validated the game files and set the version to vanilla 6.3-8. The first time I launched it, it just crashed. On the second launch, unfortunately, it behaved the same as before, showing a broken website.

I always create a new prefix while switching versions, so no worries. Thanks for the swift reply.

Cheers

@MagicD3VIL at this point I'd remove everything in the Planetside 2 game files except for assets, UserOptions.ini and the input_user XMLs and re-download them via Steam integrity check. (This won't take long as the bulk of the large data is in assets.)

Do you have any special Networking setup like a VPN proxy?

@Atemu I removed everything except the Resources folder and I validated the files. It seems that some progress was made because now I got stuck on a different screen. The launcher, however, does not respond to any interaction with the buttons or links.

Funnily enough, it's the same one I referenced here a while ago (https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-1086310046).

I do use an OpenVPN client but this time before I validated the files I disconnected and I did everything without it, it does not seem to make a difference.

EDIT: It seems that I am basically having the same issue as Djhg2000 had a few posts above (https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-1186260114) but for them, the issue resolved itself. It is probably tied to something on the system that needs updating but I cannot tell for sure.

@MagicD3VIL is that still on 6.3-8 with a clean prefix?

At that point it can only be DE differences or magic env vars. Try launching it with gamescope perhaps.

@Atemu Yes, still on clean prefix with vanilla Proton 6.3-8. I'll try that tomorrow, thanks for the help.

@MagicD3VIL Well in my case it seemed like switching to a different internet connection solved it. I have no idea why that had any impact at all, but if you have the ability to try that (like taking your computer over to a friend and trying it there) then it may shed some light on the situation.

I don't recall this ever happening on Windows so I'm not sure it's some server side check failing, but I have never had that issue again since I got back home (I was on vacation at the time I wrote that issue report).

@Djhg2000 I have actually moved since I last reported on the issue (around summer 2022) about the launcher showing just background and no login screen. So by that I have actually tried a second connection in a different house :D

When you returned from the vacation, have you installed any updates before you tried the game again, or did it just it just suddenly worked?

I cannot guarantee that the NetworkManager is not making the launcher not like something, but since it's so common on modern distros, I don't think that would be the culprit.

Cheers

@MagicD3VIL IIRC I didn't do anything differently than before. Maybe cleared the prefix again but I did that countless times on the vacation connection without any luck. I'm fairly sure I didn't install any OS updates in between either.

I played this game for long time on proton 6.21-GE, because all proton 7, both valve and GE versions had stuttering in big battles. Now i compiled TKG-proton 8.0 and the stutter issue is gone, and i gained some performance over proton 6.x.

So, i guess the stutter issue in valve builds may be fixed once they rebase proton on newer wine.

Planetside 2 no longer runs into the DXGI Error on Devuan Stable (should also be true for Debian).

Bad frames, even on the 6.x kernel with the following:

CPU: Ryzen 5 3600
GPU: RX 580
RAM: 8 GB DDR5 @ 1600 Mhz (says 2100 MT/s in dmidecode for whatever reason)

I assumed these were good enough for the game but stutters happen constantly in battles. I'm using Proton 6.21-GE-2 since I had the same experience as @Ph42oN. I will try TKG-proton and see if there is still a lot of stuttering.

I'm not certain if this is the place to write this, since this is related to the experimental Mutter variable refresh rate patch. However, here is the issue I'm experiencing:

Variable Refresh rate (Freesync to be exact) is enabled and tested as working properly in a VRRTester app (i will update this if i find issues with other games and move the discussion over to the mutter gitlab), i.e. a framerate limit set to 134 FPS results in the monitor OSD refresh rate being reported as a rapidly changing 133-135, both with VSYNC on and off. This mirrors how VRR behaves in Windows.

However, when playing Planetside, a framerate limit of 134 results in OSD refresh rate rapidly changing between being locked at 144 and random values below 134. This isn't just a visual bug with the OSD and it does ruin the Freesync experience quite severely. Here is a list of things I tried to alleviate the issue:

• Cap the framerate at different values between 120 and 144, i.e. 123, 140, 128. This did not work. I did not, however, try doing the same with sub-120 framerates.
• Different methods for capping the framerate. I tested MangoHud through GOVerlay and setting DXVK max framerate through launch options.
• VSYNC. Tried both the VSYNC built-into the game and the various VSYNC options in MangoHUD.
• Various Proton versions. Specifically, the default Proton Experimental, the v6 of Proton offered in the standard compat suite and Proton 6-21-GE2.

System is:

• OS: Nobara 37, the issue also happened on Fedora 36 with the VRR patch COPR
• GPU: RX 5700XT
• GPU Drivers: latest Mesa

@Nereithr this is actually an AMDGPU issue AFAICT. See https://gitlab.freedesktop.org/drm/amd/-/issues/1500. Set your GPU's power profile to 3D or VR and the issue should go away.

Planetside just happens to trigger it because it's very CPU-bound on most systems, leaving the GPU opportunity to downclock too aggressively which somehow manifests in VRR issues like this.

@Nereithr this is actually an AMDGPU issue AFAICT. See https://gitlab.freedesktop.org/drm/amd/-/issues/1500. Set your GPU's power profile to 3D or VR and the issue should go away.

Planetside just happens to trigger it because it's very CPU-bound on most systems, leaving the GPU opportunity to downclock too aggressively which somehow manifests in VRR issues like this.

Thanks for the heads up, I'll check it out.

However, the linked issue appears to say that they're having issues with the actual frame times, while in my case the frame time graph is flat regardless of frame limiter used, yet the reported refresh rate still jumps around(the issue is present even in an empty Sanctuary) . Nevertheless, I'll try out changing the power settings for the gpu and report back

So leaving a comment here if others are still having stutter issues, I have found something that works for me. Your mileage may vary though.

WINEDLLOVERRIDES=libglesv2=d taskset -c 08-15 gamemoderun mangohud %command%

Those are my launch commands and along with the new proton 8 (formerly I was using TKG) I have solved the hitching for me. The thing to take note here is the taskset command. I am on AMD and it seemed the game was trying to run across CCXs, I use that command to force the game onto CCX 2 of my CPU (Which is the fastest).

If you use AMD, Have a CPU with multiple CCXs and have stutter issues try taskset.

My 5800x only has one CCX and I still experience the hitching on Proton 8; I had to go back to Proton 6 again.

I tried disabling SMT but that did not help. I once even crashed the game when the hitching evolved into unbounded insanity. CPU usage went up to 100% for a while before it crashed.

What is the WINEDLLOVERRIDES=libglesv2=d for @Nyonyix?

@Atemu That's interesting, Maybe provide logs and performance metrics if you can get it to do it again.

The dll override is to fix the launcher not working. I find that is better than the disable gpu thing, Though it's probably placebo.

I am experiencing the same issue with crashing and 17 files getting corrupted: https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-1338024261

• Proton Experimental (as of posting this)
• Kernel 6.3.7-arch-1-1
• Ryzen 7 5800H
• nVidia RTX 3060 laptop, with proprietary drivers
• Wayland through Hyprland (wlroots)
• SSD is set up on ext4, if that matters

Log file follows. I verified game files so it's clean, then I played the game until it froze and crashed. This is the log from it.

steam-218230.log.zip

Having issues on progressing past the login screen in Planetside 2. Help?

OS: EndeavourOS (arch derivative)
GPU: Radeon RX 6800 Sapphire Pulse
CPU Info:

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz
    CPU family:          6
    Model:               60
    Thread(s) per core:  2
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            3
    CPU(s) scaling MHz:  95%
    CPU max MHz:         3800.0000
    CPU min MHz:         800.0000
    BogoMIPS:            6787.05
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr s
                         se sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl 
                         xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sd
                         bg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c 
                         rdrand lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept 
                         vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts v
                         nmi md_clear flush_l1d
Virtualization features: 
  Virtualization:        VT-x
Caches (sum of all):     
  L1d:                   128 KiB (4 instances)
  L1i:                   128 KiB (4 instances)
  L2:                    1 MiB (4 instances)
  L3:                    8 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:         
  Itlb multihit:         KVM: Mitigation: VMX disabled
  L1tf:                  Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
  Mds:                   Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:              Mitigation; PTI
  Mmio stale data:       Unknown: No mitigations
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not 
                         affected
  Srbds:                 Mitigation; Microcode
  Tsx async abort:       Not affected

GL Info:

OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 6800 (navi21, LLVM 15.0.7, DRM 3.52, 6.4.3-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.3
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.1.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Log:
steam-218230.log

Screenshot:

@Ninjastorm380 validate your game files. There was a recent update that corrupted game files that'd corrupt game files in a way that prevents login in a weird way for the first three times and then caused people to glitch everywhere or not appear at all.

https://lemmy.ml/post/1681026

Has anyone tested whether 8.0-3 fixed the stuttering Proton 7 introduced?

I had a great session with Proton 8.0-3 yesterday. There were a few major lag spikes but I'm unsure they're related to issue we started seeing with Proton 7 as the symptoms were quite different. Could just have been cold shader caches.

I didn't ever have it devolve into a stutter-fest like it used to though, even in larger fights. I'll use Proton 8.0-3 over the coming weeks.

@Ninjastorm380 validate your game files. There was a recent update that corrupted game files that'd corrupt game files in a way that prevents login in a weird way for the first three times and then caused people to glitch everywhere or not appear at all.

https://lemmy.ml/post/1681026

@Atemu I've already tried uninstalling and reinstalling planetside 2 and clearing the prefix (effectively a brand new install), I still get the same issues regardless.

more specifically, my issue happens across all character saves and I cannot get in no matter how long I wait or how many times I try.

Characters are busted for everyone, it's a server-side issue.

guessing there's no way to log in right now then?

I have noticed that new kernels have some stuttering in big battles similarly to proton 7.x. It runs smoothly on 6.2 kernel.
Edit: After further investigation, actually it appears to be the cpu scheduler. Usually first few zen kernel versions after new kernel released are without custom schedulers and thats why i was having stuttering. Now i tested 6.4.12-zen1 with BMQ scheduler, and the stuttering is gone. So i guess the stutter issue can be caused by proton version or cpu scheduler.

Also something seems to have changed in how it works with external fps limiters, it no longer runs smoothly with mangohud or dxvk fps limiter. I had to switch to using ingame limiter to make it smooth at 120 limit again.

FPS limiters causing stutter could also be because of https://gitlab.freedesktop.org/drm/amd/-/issues/1500.

No its not that, it has happened in lot of games and i have the workaround. And ingame fps limiter works fine, that was never the case when that power saving bug happens.

I was mistaken; the bug inducing massive lag spikes (hundreds of ms) via near 100% CPU usage is still there in Proton 8. You can trigger it reliably in certain places. Strafing left and right at a certain spot brings me down to like 10fps.

I can't get it to trigger reliably though. On my second attempt with logging enabled, I just played without ever encountering a stutter to speak of.

Proton 9.0 (Beta11) still produced hitching for me. It always runs fine for a bit then has a handful of rather large lag spikes in close succession and then runs fine again for a bit.

Can you all watching this issue reproduce this issue? Please react with thumbs up/down.

Proton 9.0 (Beta11) still produced hitching for me. It always runs fine for a bit then has a handful of rather large lag spikes in close succession and then runs fine again for a bit.

Can you all watching this issue reproduce this issue? Please react with thumbs up/down.

What is your set up like? Kernel, wm, compositor etc?

Xanmod, i3.

More details:

https://github.com/Atemu/nixos-config/blob/ee2d85dc3665ae3cad463a3eb132f806651fe436/configs/HEPHAISTOS/default.nix#L18

https://github.com/Atemu/nixos-config/blob/ee2d85dc3665ae3cad463a3eb132f806651fe436/modules/gaming/module.nix#L17-L87

https://github.com/Atemu/nixos-config/blob/ee2d85dc3665ae3cad463a3eb132f806651fe436/modules/desktop/module.nix#L16-L161

Update on the stutter: The massive stutter is only present when I pin Planetside to the cores of my 7950x3d with V-Cache or park the other cores.

I wonder what could be happening here. Has anyone experienced such an issue in other games too perhaps?

Proton Experimental breaks the game?
Gives a generic G12 error and exits (usually means reinstall, tried that)

return to proton 9.0.3 and it works
I reinstalled PROTON EXP and it doesnt work still (and files revalidated)

also i cannot speak on the mic... it drops audio all the time everytime

im on debian stable 6.0.2 lts or something kernel

Anyone on Hyprland able to reproduce https://github.com/hyprwm/Hyprland/issues/8384? Not reproducing would also be incredibly interesting to know.

I have seen a new lag problem. This was first seen after a week away from running this game.
The game starts to have much lower and inconsistent frame rates whenever there is mouse or keyboard input.
The lag only starts after many minutes of run time. This steam log shows a case when the lag started after about 42 minutes.
https://gist.github.com/stroyan/249445563b5969dbb97cd020fefe7904

I have seen a new lag problem. This was first seen after a week away from running this game. The game starts to have much lower and inconsistent frame rates whenever there is mouse or keyboard input. The lag only starts after many minutes of run time. This steam log shows a case when the lag started after about 42 minutes. https://gist.github.com/stroyan/249445563b5969dbb97cd020fefe7904

Can confirm. Specifically it only seems to be when moving your character; being dead and looking at the world while moving the mouse pointer around is unproblematic.

Been having issues recently (past ~week) where shortly after joining a server, the game freezes for about 30 seconds, and then crashes with no error message. Here's the proton log, and here's the steam system information.

I have also seen this crash. I have discovered that the behavior changes if I use the game settings to change the resolution as soon as the game starts. In that case the hang occurs shortly after opening each new map. But it recovers after about 60 seconds. Here is a log with a hang after 93 seconds and a recovery after 63 seconds more.
https://gist.github.com/stroyan/249445563b5969dbb97cd020fefe7904

@stroyan just to clarify, are you then able to play the game normally after that recovery? If so, what did you change the resolution from/to? (Or was it just the act of changing it at all?)

The game does play normally after the 63 second hang. I changed between 4K full screen and 1440p full screen. The improved behavior persisted even if I immediately changed back to the original resolution.

This worked for me as well! Great find! Thank you for sharing!

@GleamingPulsar I think maybe I didn't manage to find a big enough fight but I couldn't get the game to desync. Have you tried newer proton versions (for example 10, or experimental)? if so, do you get the issue there as well?

I have gotten this issue on an older hotfix version, but I will attempt to try again.

The issue still occurs on proton experimental with a fight of around 100 players

The hang behavior is gone with the current Planetside version and the current proton experimental. Both the fatal hang and the non-fatal 60 second hang after doing a resolution change have stopped happening.

Also observing that the hang is gone

Has anyone else noticed positional desyncs yet in large fights? If not,
what troubleshooting steps could I take to avoid this? I know that the game
struggles with positional data after witnessing some bugs, especially with
poor internet, but this happens in every fight above a player threshold
for me, where every model that can move around does (so terminals don't).
Is this a problem with my internet specifically?

On Sun, Jul 13, 2025 at 4:48 PM Thomas Cohn @.***>
wrote:

cohnt left a comment (ValveSoftware/Proton#5295)
https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-3067293234

Also observing that the hang is gone

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-3067293234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFALRWTRVPM345URVGPEDXD3ILAYPAVCNFSM6AAAAABPS4Q4JCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANRXGI4TGMRTGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

After a December 16 update to the game planetside has been frequently crashing with an EXCEPTION_ACCESS_VIOLATION.
Here is an example steam-218230.log from a particularly quick crash.
gist

I can only get a flash of the DBG logo from the launcher before the launcher crashes. I have tried deleting the prefix/compatdata directory and recreating it via running with several versions of Proton. None of them seem to help None of the recent tinker steps from ProtonDB have worked either. Every post I have found relating to the errors I find in the Proton log say that they are not critical or game stopping errors. There are no errors or information about why the launcher crashes as far as I can tell.

I am running Kubuntu 24.04.4 LTS with HWE with the latest Canonical released kernel, Mesa and AMDGPU/Vulkan packages/drivers (RX 9070xt). Any Valve game I have tried works, but I had to really mess with Valkyria Chronicles to get it going (it complained that it couldn't change display resolution so I had to force it's setup app to run windowed). Planetside 2 has been elusive and frustrating since I cannot even eek out an error message/cause.

Is X11/Plasma 5.27 an issue? Will I have to wait until 26.04 is released with proper Wayland and Plasma 6 support?

Starting with a 5/5/2026 game update the game crashes with error G25 "Your video card had trouble initializing".
That happens with "Proton 11.0 (Beta)" but there is no problem using "Proton 10.0-4".
Here is a proton log from a failed start up.
https://gist.github.com/stroyan/69f33e6f3c5319b2b88a9f0515484a7a

@stroyan We aren't seeing this error message on our hardware. Do you have some special/unique hardware you are running this on - dual GPU system? Something else? Could you please copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report?

The system has two monitors with a single RTX 4070 SUPER GPU card.
It has a MangoHud vulkan layer installed, but the failure happens with MangoHud disabled by environment variable.
I confirmed that the start up problem still occurs on proton 11.0 with the game updated to today's download.
Here is the system information.
system information https://gist.github.com/stroyan/767267265703761d27141682f23465a8
runtime diagnostics https://gist.github.com/stroyan/2b5e883ea0f210bf777dc77c679bf829

Just a quick note that I am still seeing that G25 startup crash with proton 11 after the game's May 14 patch update.

Try with bleeding edge
https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

On Sat, May 16, 2026, 10:07 PM Mike Stroyan @.***>
wrote:

stroyan left a comment (ValveSoftware/Proton#5295)
https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-4468847653

Just a quick note that I am still seeing that G25 startup crash with
proton 11 after the game's May 14 patch update.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-4468847653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EHFDB47IJLXJNHK6DD43ENETAVCNFSM6AAAAABPS4Q4JCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRYHA2DONRVGM
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID:
@.***>

The game started successfully for me with proton experimental bleeding edge May 15.

thanks for confirming

El dom, 17 may 2026 a la(s) 1:48 p.m., Mike Stroyan (
@.***) escribió:

stroyan left a comment (ValveSoftware/Proton#5295)
https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-4471904951

The game started successfully for me with proton experimental bleeding
edge May 15.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/5295#issuecomment-4471904951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EGV7HIGSIG4LVNQ45D43H3OTAVCNFSM6AAAAABPS4Q4JCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINZRHEYDIOJVGE
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID:
@.***>