Open diraven opened 6 years ago
@AsciiWolf You sir are a genius. Its the image roller on the launcher.
To put this in perspective, by closing the launcher, my FPS went from 10-25 to 60.
I've found performance dips when moving on Nvidia when "allow flipping" is ticked, unfortunately if I untick it video playback in browsers seem to be at half refresh rate.
Tried closing the launcher but had no effect.
@AsciiWolf You sir are a genius. Its the image roller on the launcher.
To put this in perspective, by closing the launcher, my FPS went from 10-25 to 60.
Can we write a replacement script for the launcher, similar to the open source launcher script built here https://gitlab.com/GloriousEggroll/warframe-linux? Does anyone knows about the legalities or EULA/ TOS limitations behind this?
Play
button in the Steam client is sufficient.The launcher sometimes crashes. Simply starting it a second time helps. As mentioned before by @AsciiWolf , minimizing/closing the launcher after the game started improves performance and fixes the issue with the stuttering of game and desktop every few seconds (my desktop is KDE on X.org). Another thing about the stuttering: I had no stuttering with opened launcher on Proton 3.16 Beta, Proton 4.2 introduced that issue for me. As mentioned, closing/minimizing the launcher fixes it.
Hello @buschmann23, with Proton 4.2-1, please add PROTON_LOG=1 %command%
to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
@kisak-valve The log file of starting the game, waiting for the stuttering, and closing the game is 6.9 MiB. Should I really post it here into the comments?
Drag and dropping the file into the comment box should add it as an attachment. As you expected, I'm not interested in a wall of text in a comment.
Log of game stuttering while launcher is opened/not minimized on Proton 4.2-1: steam-306130.log
My systeminfo gist
I've just installed ESO using proton (3.16-8 Beta) via steam and it worked disabling esync (didn't try with esync enabled). However, the next time I tried to run the game, after pressing start in the launcher, I only got a black screen with sound in the background. I tried to reboot the computer and always the same issue, I also tried using proton 4.2-1 and the same thing. Any idea on how to fix this? Thanks
System Information
GPU: GTX 1060
Driver: 410.104-1
Distro version: Debian testing with KDE plasma
Proton version: 4.2-1 and 3.16-8 Beta
@MrPaj I usually find blackscreens to be a driver issue. You could also try upgrading your driver version to 418.xx for your GTX 1060.
@kisak-valve: would adding proton_log=1 help identify my crashes even if I suspect them not to be related to the launcher itself, but some different ingame issues?
Hello @Enteneller2017, definitely wouldn't hurt to have more information.
@Enteneller2017, eventfd: Too many open files
in your log indicates that your max file limit is too low for esync. Please run ulimit -Hn
and confirm it is a high value and not 4096.
Thanks so much for looking into the log. That was exactly the issue, I was able to fix it through the default esync readme. I seem to have overlooked this was a requirement to running Proton properly. I'm playing over an hour now and no crashes as of yet. Much love Valve. Really, thanks kisak!
I have noticed one small bug. When using non-English (Czech) locale and keyboard, some characters in the action bar are missing:
The Elder Scrolls Online (306130) Framerate drops to unplayable levels.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/2587. @dziad-cmentarny posted on 2019-04-22T15:41:15:
The game launches and runs fine without any tinkering. My problem is that after just few minutes my framerate falls to a stable 10(ten)fps. I have tried turning off esync, tried different settings within the game and by editing settings file. Also checked all Proton versions available via Steam Play. Nothing prevents the framerate degradation except relaunching the game. I have no addons, it's a clean installation. Additionally no other game I play exhibits such behavior.
Proton:4.2-3 Distro:Ubuntu 18.10 Kernel:4.18.0-16-generic RAM:8 GB
GPU Driver:NVIDIA 418.56 GPU:NVIDIA GeForce GTX 950M CPU:Intel Core i5-6300HQ @ 2.30GHz
@AsciiWolf You sir are a genius. Its the image roller on the launcher. To put this in perspective, by closing the launcher, my FPS went from 10-25 to 60.
Can we write a replacement script for the launcher, similar to the open source launcher script built here https://gitlab.com/GloriousEggroll/warframe-linux? Does anyone knows about the legalities or EULA/ TOS limitations behind this?
This is a grey area so I won't say too much, but I poked around a bit and found the following:
I kinda gave up.
I just tested the Elsweyr closed beta and everything worked fine (with Proton 4.2-3)! The only issue I had was with the game launcher making my computer unusable while downloading the closed beta client, but that was easy to workaround by minimizing the game launcher to tray.
Launchers with transparency now have a blank window with a WM Bar and don't show launcher.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3062. @ronlaws86 posted on 2019-09-15T18:39:05:
[*] that I haven't found an existing compatibility report for this game.
[*] that I have checked whether there are updates for my system available.
Since latest update that pushed out for Proton, launchers (Possibly ones that use transparency) fail to set the window size correctly and have now gained a window title bar where they previously did not exhibit this behaviour.
Ensure latest proton is in use Click launch. Minimise launcher then bring back to focus.
Launchers with transparency now have a blank window with a WM Bar and don't show launcher.
Issue transferred from #3062. @ronlaws86 posted on 2019-09-15T18:39:05:
Compatibility Report
* Name of the game with compatibility issues: Elder Scrolls Online * Steam AppID of the game: 306130
System Information
* GPU: nVidia GTX 1070 * Driver/LLVM version: 435.21 * Kernel version: 5.0.0-27 * Link to full system information report as [Gist](https://gist.github.com/ronlaws86/a845a559894131b1077b6c004fa89f62): * Proton version: 4.11-4
I confirm:
* [*] that I haven't found an existing compatibility report for this game. * [*] that I have checked whether there are updates for my system available.
Symptoms
Since latest update that pushed out for Proton, launchers (Possibly ones that use transparency) fail to set the window size correctly and have now gained a window title bar where they previously did not exhibit this behaviour.
Reproduction
Ensure latest proton is in use Click launch. Minimise launcher then bring back to focus.
Yes confirmed here also in Gnome.
Thanks for reporting. This was caused by ValveSoftware/Wine@1d1d317f3849c8a9475d9932654298cbada6e47a. We're working on a fix.
@fls2018 I can confirm this bug affect Cinnamon DE and also affects Uplay launcher
The problem with the semi-transparent launcher is understood and a fix will be in the next release.
Hello, 4.11-5 was released today and contains a fix for the launcher problem. Please retest!
Please include this patch in Proton that is designed specifically for this game when using wined3d
Please include this patch in Proton that is designed specifically for this game when using wined3d
Is this patch needed? I've not forced D3D and left it to use Vulkan through proton, and have been seeing framerates of 60-100, is there a benefit to forcing OpenGL D3D?
Well, not all GPUs can use Vulkan and D3D can be used as an alternative backend for debugging purposes. We can't just suddenly ditch D3D in favor of Vulkan without a transitional period.
OK so only if Vulkan is not supported on the host, got it. That answered that question. :o)
As for the latest update; I can confirm the window decoration issue has gone, however I've also seen a slight decrease in overall performance. some areas where i'd see 50+ are now hovering around to 37fps mark and the frame-rate swings are much more vast once again.
Overall game playability is still good, though Ultra settings can be touch and go, this may be down to the age of my machine so it could be a mileage may vary thing.
I ran a nCR Trial last night and the main boss fight saw me drop to 20 or less, had to dive in and turn shadow quality from ultra to low, which helped a lot.
Hello @Saroufim, previously discussed at https://github.com/ValveSoftware/Proton/pull/1749#issuecomment-489606572, using wined3d for DirectX 10/11 games is not considered supported in Proton. The patch in question should be evaluated upstream and make its way into upstream wine. From there it will end up in downstream projects as they move forward.
Well, not all GPUs can use Vulkan and D3D can be used as an alternative backend for debugging purposes. We can't just suddenly ditch D3D in favor of Vulkan without a transitional period.
Linux doesn't have native D3D support.
They were pretty obviously talking about wined3d. Not sure if you are being pedantic or genuinely uncertain about what is being discussed.
I had this working just fine for more than a year.. but since the last steam UI update and proton update is not working :(
why? [edit] works like before if I force to use proton 4.2.9
@ReK2Fernandez On latest Beta client with Proton 4.11-7 game works fine for me, are you sure you didn't mess up proton updating the wineprefix by accident? It happens if you close the "preparing to launch your game" window the first time running with a new proton version. If that's the case either go to an older version, launch the game, go to a newer version, launch the game. Or just delete the wineprefix and let proton remake it $STEAMLIBRARY/steamapps/compatdata/306130/pfx
I have encountered a strange rendering issue in ESO on Proton. Please see the following image: System Specs: AMD 5700 Manjaro w/ kernel 5.4.2-1-MANJARO Latest Vulkan (1.1.107), Mesa (19.2.7), DXVK (1.4.4) etc. on Manjaro Testing (also happens on Stable) Proton 4.11-9
Running with "PROTON_NO_ESYNC=1" does not change anything. Running with "PROTON_USE_WINED3D=1" renders more normally, but has many textures completely missing. Running with "PROTON_LOG=1" shows many lines with fixme:file:K32GetMappedFileNameA
, referencing various memory addresses. Running with "PROTON_DUMP_DEBUG_COMMANDS=1", then running in the winedbg_run script, doesn't show anything in the debugger.
I have tried updating to mesa-git on the AUR with no change. I've tried kernel 5.3 with no change. I've tried Proton versions 4.2-9 and 3.16-9 with little change (sometimes the color scheme is not a "negative", but is still a strange rendered cloud like shown above).
Any help is greatly appreciated. This issue does not appear on any other games I have played, whether using Proton or otherwise.
EDIT- I should add that the game runs fine when I change out my AMD 5700 for an AMD 460. The fixme:file:K32GetMappedFileNameA
lines also occur in the logs when running with the AMD 460.
~Hello @WaterWhorl, if possible, please retest with mesa 19.3.0-rc6+.~
I reproduced the issue with mesa-git a few days ago. DXVK_HUD listed mesa as 19.99.99 (I think it was 20.0-devel).
EDIT- Problem persists with Proton 4.11-10 and Mesa 19.3.0. Problem persists with RADV_PERFTEST=aco. Please let me know if there is any other info that can be helpful.
EDIT- Problem persists with Proton 4.11-11, Mesa 19.3.1, DXVK 1.5-16, kernel 5.5rc.
@WaterWhorl Can you please re-test? One user reported that the issue seems fixed with RADV/Navi. Thanks!
Hello, I have updated to the latest Manjaro Unstable and retested. DXVK_HUD shows the following: Kernel 5.4.7-1 Proton 4.11-11 DXVK 1.5-16 Mesa 19.3.1 LLVM 9.0.0
The problem persists for these settings. The problem persists with and without aco. What settings were successful?
One new development seems to be that when using 4.2-9 with and without aco, the game renders almost correctly, albeit with a lower framerate (~35 FPS) even than on my 460 (45-75 FPS). The main issue I notice for this combination is un-rendered textures as shown above.
Hello @WaterWhorl, looks like the request is referring to https://gitlab.freedesktop.org/mesa/mesa/issues/2047#note_374016, which should need mesa git 824bd08 or newer to test. This commit is also lined up for mesa 19.3.2 when it comes out.
Thank you. I will retest when Mesa 19.3.2 is released and post an update with the results.
While waiting for Mesa 19.3.2, I have downloaded and compiled Mesa-git on my own. Before I used the AUR. In this case, I installed it in a separate build/install
directory in order to avoid changing the system installation. How do I start steam with this install?
LD_LIBRARY_PATH='/home/$USER/mesa/build/install:$LD_LIBRARY_PATH' LIBGL_DRIVERS_PATH='/home/$USER/mesa/build/install:$LIBGL_DRIVERS_PATH' steam
fails to start.
Similarly, adding these variables to the launch options of ESO does not work.
I have tested on Mesa 19.3.2. It appears to be working normally. The only bug I notice now is an occasional screen stutter where a thin horizontal bar (~3-5% of the screen) fails to render for a frame or two. This seems unrelated to the original bug.
How do you actually install this?
Running the installer with -i GUI
doesn't finish properly.
It closes the installer while "installing uninstaller" and my system makes a sound indicating that a new window opened, but nothing happens.
Tried Proton 4.11-12, 5.0-3 and 5.0-GE-2.
I cannot find anything helpful in the log.
steam-306130.log
There is two people on ProtonDB with the same problem. Doesn't work with and without esync.
The Elder Scrolls Online (306130)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3572. @manaog posted on 2020-02-26T10:39:30:
GPU: GTX 1060
Driver/LLVM version: nvidia 440
Kernel version: 5.4
Link to full system information report as Gist: cant copy it steam-306130.log
Proton version: 5.0-3 / 4.2-9 / 4.11-12 / 3.7-8 / 3.16-9
Installation hangs at 97%~ - Installing Uninstaller ergo i cant play at all :(
at every launch of the game.
EDIT here is my GIST System information : https://gist.github.com/manaog/2ffb1e6cdeee5cc853db88579647278f /EDIT
@jug007 i could install it now. you have to go to your steam settings -> account -> opt in for beta. then restart steam and there you go, the bug is fixed.
Doesn't work on my system. I was already opted into steam client beta. Tried without steam client beta - didn't work Opted back into steam client beta - game still didn't work
Doesn't work on my system. I was already opted into steam client beta. Tried without steam client beta - didn't work Opted back into steam client beta - game still didn't work
Did you install the game on an NTFS partition?
No I installed it on a BTRFS partition, like all my other games. I just tried redownloading the game from steam, restarting the steam client and installing it again. The installer looks slightly different now and there is an additional language to choose from, but it still doesn't complete.
Elder Scrolls Online FPS dropdown
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3821. @MadMagnetic posted on 2020-05-01T22:25:28:
System: Host: madmagnetic-lp Kernel: 5.6.2-pf x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.18.4
tk: Qt 5.14.2 info: latte-dock wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Laptop System: ASUSTeK product: TUF Gaming FX705DY_FX705DY v: 1.0 serial: <filter>
Mobo: ASUSTeK model: FX705DY v: 1.0 serial: <filter> UEFI: American Megatrends v: FX705DY.315 date: 03/09/2020
Battery: ID-1: BAT0 charge: 57.1 Wh condition: 60.0/64.0 Wh (94%) volts: 15.6/15.6 model: ASUSTeK ASUS Battery type: Li-ion
serial: <filter> status: Not charging
CPU: Topology: Quad Core model: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen+ rev: 1
L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 33535
Speed: 399 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 1: 399 2: 399 3: 399 4: 399 5: 399 6: 399
7: 399 8: 399
Graphics: Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] vendor: ASUSTeK driver: amdgpu
v: kernel bus ID: 01:00.0 chip ID: 1002:67ef
Device-2: Advanced Micro Devices [AMD/ATI] Picasso vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 04:00.0
chip ID: 1002:15d8
Display: x11 server: X.Org 1.20.8 driver: amdgpu FAILED: ati unloaded: modesetting alternate: fbdev,vesa
compositor: kwin_x11 resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RAVEN (DRM 3.36.0 5.6.2-pf LLVM 10.0.0) v: 4.6 Mesa 20.0.5 direct render: Yes
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:15de
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 04:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k5.6.2-pf
Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave driver: rtl8821ce v: N/A
port: e000 bus ID: 02:00.0 chip ID: 10ec:c821
IF: wlp2s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: d000
bus ID: 03:00.0 chip ID: 10ec:8168
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 931.51 GiB used: 243.70 GiB (26.2%)
ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB speed: 6.0 Gb/s rotation: 5400 rpm
serial: <filter> rev: 0J scheme: GPT
Partition: ID-1: / size: 388.11 GiB used: 243.66 GiB (62.8%) fs: ext4 dev: /dev/sda6
Sensors: System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 40 C device: amdgpu temp: 40 C
Info: Processes: 305 Uptime: 24m Memory: 15.52 GiB used: 4.41 GiB (28.5%) Init: systemd v: 244 Compilers: gcc: 9.3.0
clang: 10.0.0 Shell: fish v: 3.1.0 running in: yakuake inxi: 3.0.37
Logfile has 84.6 Mb weight, so I can't attach it here.
All were fine before I updated Proton from 5.0-6 to 5.0-7 - after that update fps drops down to ~10 before update it was stable ~50fps. Is there any way to downgrade Proton back to 5.0-6?
The game was working for me very nicely but since yesterday it won't start anymore. Launcher gets stuck on "Loading..." and nothing seems to help. Tried reinstalling the game, removing compatdata, starting the game from clean user account. Downgrading proton to 4.* makes launcher crash instead.
System Information GPU: AMD Fury Driver/LLVM version: Mesa 20.1.0/LLVM 10.0.0 Kernel version: 5.6.13
% uname -a Linux 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1 (2018-07-20) x86_64 GNU/Linux
Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz
Video Card: Driver: NVIDIA Corporation GeForce GTX 970/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 390.77
Installs fine, then freezes after "Bethesda" logo.