Open ProjectSynchro opened 3 years ago
mikedebian
commented
2 years ago 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).
HenrikDK2
commented
2 years ago 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.
Atemu
commented
2 years ago 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.
Atemu
commented
2 years ago 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:
Atemu/Nixpkgs@f8e92efb576a88d9b687499425cb0ac3cf170a62 Atemu/nixos-config@d7066af064997845240f63f469552faabfd04951
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.
ProjectSynchro
commented
2 years ago 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).
Atemu
commented
2 years ago 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?
ProjectSynchro
commented
2 years ago 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
Atemu
commented
2 years ago Thank you!
LFC smells like the most likely culprit then. Could anyone with an LFC-capable monitor chime in?
jarrard
commented
2 years ago 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.
GloriousEggroll
commented
2 years ago With proton-ge 6.21, if you remove your prefix, then run the game, the launcher renders fine. i tested it yesterday.
jarrard
commented
2 years ago 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)
GloriousEggroll
commented
2 years ago 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.
jarrard
commented
2 years ago I was simply pointing out that a fix existed as far back as ProtonGE6.8
Atemu
commented
2 years ago @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?
rupansh
commented
2 years ago 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
Djhg2000
commented
2 years ago 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_FAILEDThe 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).
Atemu
commented
2 years ago What happens when your FPS are greater than your refresh rate in-game? (not loading screens!)
Djhg2000
commented
2 years ago 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.
Atemu
commented
2 years ago 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:
Djhg2000
commented
2 years ago @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.
daufinsyd
commented
2 years ago According to a user on protondb, adding --disable-gpu solved the launcher issue.
cardpuncher
commented
2 years ago Here's the Proton log: steam-218230.log.gz
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.
Launch the game, log in then wait
.
kisak-valve
commented
2 years ago 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.
cardpuncher
commented
2 years ago 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.
eiglow
commented
2 years ago 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.
PlatanusO
commented
2 years ago
- 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.
Atemu
commented
2 years ago @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.
HolySoap
commented
2 years ago 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
aeikum
commented
2 years ago @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?
HolySoap
commented
2 years ago @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.
aeikum
commented
2 years ago 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.
HolySoap
commented
2 years ago 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).
Atemu
commented
2 years ago @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
HolySoap
commented
2 years ago @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.
Atemu
commented
2 years ago I don't. All I'm saying is that it works on my machine.
HolySoap
commented
2 years ago That's why I provided two different logs so someone smart can figure out what's wrong. :)
h8672
commented
2 years ago 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 MBAlright two updates:
ProjectSynchro
commented
2 years ago 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.
f-fusco
commented
2 years ago 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.
MagicD3VIL
commented
2 years ago 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
eiglow
commented
2 years ago 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 ????.
Tabascl
commented
2 years ago 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.
Djhg2000
commented
2 years ago 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.
jarrard
commented
2 years ago Perhaps try GE and see what happens.
Atemu
commented
2 years ago @Djhg2000 try Proton 6.3-8
Djhg2000
commented
2 years ago 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).
Atemu
commented
2 years ago @Djhg2000 try resetting your Proton prefix.
Djhg2000
commented
2 years ago @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.
Djhg2000
commented
2 years ago 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.
Compatibility Report
System Information
I confirm:
steam-218230.log
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