Proton
Proton copied to clipboard
ValveSoftware
Planetside 2 (218230)
Compatibility Report
- Name of the game with compatibility issues: PlanetSide 2
- Steam AppID of the game: 218230
System Information
- GPU: RTX 2070
- Driver/LLVM version: NVIDIA 495.44
- Kernel version: 5.14
- Link to full system information report as Gist: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e
- Proton version: Proton Experimental (bleeding-edge branch)
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
The launcher for this game does not render correctly, and first spawns a black and then white window. You can still interact with what should be on the window.
Looking in the proton log shows multiple instances of eglCreateWindowSurface failed with error EGL_BAD_ALLOC.
Running this with Proton-6.20-GE-1 fixes rendering issues with the launcher, so there is a patch-set out there that fixes this. Which one is beyond me.. Launching the game itself is futile however, due to how Battleye support has been implemented.
Once logged in launch the game with Proton Experimental while running the Steam Client beta and ensuring the Battleye Runtime is installed. Click where the 'Play Now' button should be and the game seems to launch.
Plays well with average slowdown. Haven't seen any graphical glitches in game.
Reproduction
- Launch the game using Proton Experimental while running the Steam Client beta and ensuring the Battleye Runtime is installed.
- Observe the rendering issues with the launcher, rendering the game unplayable without using a custom build of proton to login.
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.
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
- Have a Freesync monitor with LFC
- Start game
- Log in and launch using the workaround described in https://github.com/ValveSoftware/Proton/issues/5295
- Select a character and press play
- Have a framerate greater than monitor refresh rate
- 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.
@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:
- Launch game through launcher
- Press exit when in the character selection screen
- 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
.
Hello @cardpuncher, looking at your system information, your Beema chipset is part of AMD's Sea Islands (CIK) generation. The linux kernel uses the radeon kernel by default with this generation, but the radeon kernel module is not compatible with Vulkan. Please give https://github.com/ValveSoftware/Proton/wiki/For-AMD-users-having-issues-with-non-OpenGL-games a read.
Additionally, it appears that the 64 bit variant of the vulkan driver for your GPU is missing. Please check that the mesa-vulkan-drivers system package is installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386 and install it with sudo apt install mesa-vulkan-drivers.
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.