search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.07k stars 1.05k forks source link

Guild Wars 2 (1284210) #6547

Open nyannyankas opened 1 year ago

nyannyankas commented 1 year ago

Compatibility Report

System Information

I've been able to reproduce the problem on two separate systems:

1.

2.

I confirm:

Proton Log with the issue: steam-1284210.log Proton Log from a few days ago, when the game was working fine: steam-1284210.log

Symptoms

The game doesn't launch anymore. It's shown as running in Steam, but the launcher never appears. This issue has only appeared in the bleeding edge-branch a few days ago, but is now also occuring in the regular Proton Experimental-branch.

The line 00c0:00c4:err:sync:RtlLeaveCriticalSection section 00007FF941E4CA60 is not acquired is repeating in the logs, so I guess that has something to do with it.

Reproduction

  1. Launch the game
  2. Nothing happens
rjchaves commented 1 year ago

I can confirm, the game appears as running on steam but the launcher never appears. It was introduced in a recent update of proton experimental. The problem does not occur in proton 7.0-6 nor in proton hotfix

Here is the system info

Iglu47 commented 1 year ago

I confirm, but it should by fixed on https://github.com/ValveSoftware/wine/releases/tag/experimental-wine-7.0-20230220b please try with this version

LingMan commented 1 year ago

Can confirm, the launcher starts again with the latest Proton experimental (which is presumably the version linked above).

There are two other bugs with GW2, which were originally filed against upstream wine before GW2 was on Steam, but deserve a mention here since they also show up on Proton:

nyannyankas commented 1 year ago

Can confirm that the game runs again with the current bleeding edge version. Thanks! :)

I've come across this issue a few times, but I'm not sure if Proton can fix it. It exists because the ^-key is handled as a dead key in your keyboard layout. You can work around this issue by choosing German (no dead keys) as a keyboard layout in your system settings.

LingMan commented 1 year ago

GW2 works just fine with dead keys on Windows, so I don't immediately see why Proton would be unable to fix it. Switching to German (no dead keys) is an interesting workaround I wasn't aware of, but unfortunately it breaks, you know... typing. Gonna stick to my current workaround of binding weapon swap to Q instead.

ahjolinna commented 1 year ago

for me GW2 launcher gets stuck at "Initializing..." -phase, with both version of proton (7.0-6 and experimental-bleeding)

here is the log steam-1284210.log

my system spec:


             .;ldkO0000Okdl;.                
         .;d00xl:^''''''^:ok00d;.            OS: openSUSE MicroOS
       .d00l'                'o00d.          Kernel: x86_64 Linux 6.1.12-1-default
     .d0K^'  Okxoc;:,.          ^O0d.        Uptime: 3h 21m
    .OVVAK0kOKKKKKKKKKKOxo:,      lKO.       Packages: Unknown
   ,0VVAKKKKKKKKKKKKK0P^,,,^dx:    ;00,      Shell: bash 5.2.15
  .OVVAKKKKKKKKKKKKKk'.oOPPb.'0k.   cKO.     Resolution: 3072x1728
  :KVAKKKKKKKKKKKKKK: kKx..dd lKd   'OK:     DE: KDE 5.103.0 / Plasma 5.27.0
  lKlKKKKKKKKKOx0KKKd ^0KKKO' kKKc   lKl     WM: KWin_wayland
  lKlKKKKKKKKKK;.;oOKx,..^..;kKKK0.  lKl     GTK Theme: Breeze [GTK2],  [GTK3]
  :KAlKKKKKKKKK0o;...^cdxxOK0O/^^'  .0K:     Icon Theme: Papirus-Dark
   kKAVKKKKKKKKKKKK0x;,,......,;od  lKP      Disk: 16T / 21T (75%)
   '0KAVKKKKKKKKKKKKKKKKKK00KKOo^  c00'      CPU: AMD Ryzen 7 5700G with Radeon Graphics @ 16x 4.3GHz
    'kKAVOxddxkOO00000Okxoc;''   .dKV'       GPU: NVIDIA GeForce RTX 3060 Ti
      l0Ko.                    .c00l'        RAM: 5594MiB / 15779MiB
       'l0Kk:.              .;xK0l'         
          'lkK0xc;:,,,,:;odO0kl'            
              '^:ldxkkkkxdl:^'
rjchaves commented 1 year ago

This also happens with an ANSI keyboard on Portuguese (english int layout) locale, my workaround is to switch to english.

Smoukus commented 1 year ago

I have the issue that every time I launch the game, I get the Processing Vulkan shaders window: image

It happens literally after every start of the game, and lasts for around a min. I know that that window should pop up after gpu driver update, but it keeps appearing every single time even when I haven't updated my drivers.

I use Proton Experimental Bleeding Edge, Mesa-git

                     ./o.                   smokus@smokus-linux
                   ./sssso-                 -------------------
                 `:osssssss+-               OS: EndeavourOS x86_64
               `:+sssssssssso/.             Host: MS-7C91 (2.0)
             `-/ossssssssssssso/.           Kernel: 6.3.0-rc3-273-tkg-cfs
           `-/+sssssssssssssssso+:`         Uptime: 12 hours, 20 mins
         `-:/+sssssssssssssssssso+/.        Packages: 1516 (pacman)
       `.://osssssssssssssssssssso++-       Shell: zsh 5.9
      .://+ssssssssssssssssssssssso++:      Display 1: 1920x1080 @ 144Hz
    .:///ossssssssssssssssssssssssso++:     Display 2: 2560x1440 @ 170Hz
  `:////ssssssssssssssssssssssssssso+++.    DE: KDE Plasma 5.27.3
`-////+ssssssssssssssssssssssssssso++++-    WM: KWin (Wayland)
 `..-+oosssssssssssssssssssssssso+++++/`    WM Theme: Breeze
   ./++++++++++++++++++++++++++++++/:.      Theme: Breeze (Dark) [QT], Breeze [GTK3/4]
    `:::::::::::::::::::::::::------``      Icons: breeze-dark [QT], breeze-dark [GTK2/3/4]
                                            Font: Cantarell (11pt) [QT], Cantarell (11pt) [GTK2/3/4]
                                            Cursor: Bibata-Modern-Ice (24px)
                                            Terminal: konsole 22.12.3
                                            Terminal Font: MesloLGS NF (12pt)
                                            CPU: AMD Ryzen 9 5900X (24) @ 4.950195 GHz
                                            GPU: AMD Radeon RX 6800 XT
                                            Memory: 7.50 GiB / 31.19 GiB (24%)
                                            Disk (/): 916 GiB / 1 TiB (67%)
                                            Disk (/mnt/ExternalHDD): 1 TiB / 4 TiB (30%) [Removable]
                                            Locale: en_US.UTF-8
LingMan commented 1 year ago

Edit: Nevermind, game bug that happens when shadow quality is set to ultra.

Got some misrendering in one specific location. It's a dark room with a light in the middle. Supposed to look like this: Screenshot from 2023-04-08 23-36-30

For me the lighted area is very blocky instead of being a nice circle: Screenshot from 2023-04-08 23-48-01

Location: Super Adventure Box: World 2 Zone 1: Hidden Room 7 (Associate of Secrets, World 2: Does the log have other secrets?). Using Proton Experimental (non-BE) with Mesa 23.0.1 on an AMD R9 390. DX9 renderer: broken with dxvk; broken with wined3d DX11 renderer: broken with dxvk; game crashes on start with wined3d

My attempts to create an apitrace haven't been fruitful since it's impossible to get there with 6fps. Maybe someone with more powerful hardware has better luck. Can anybody try to reproduce on Windows to rule out a game bug? A textual guide on how to get there: https://wiki.guildwars2.com/wiki/Rapids#Checkpoint_7_to_Checkpoint_8 Video guide on how to get there: https://youtu.be/UWyjrPp3KN8?t=610

Unfortunately Super Adventure Box is a seasonal festival and will only be available until April 18 this year (10 days from now).

kisak-valve commented 1 year ago

Hello @LingMan, you might have better luck getting a renderdoc capture instead of an apitrace and file a bug report with mesa for the video driver devs to ponder.

LingMan commented 1 year ago

Thanks for the pointer, @kisak-valve. Had a nice testing session with @Blisto91. Turns out to be a game bug that happens when shadows are set to ultra. Same behaviour on Windows.

ahjolinna commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6547#issuecomment-1439552278

okay I found the solution for my MicroOS issue or more exact SELinux issue

apparently I need to run this command: sudo setsebool selinuxuser_execmod 1 to get the game run and other (mmo) games that had the same issue

more about it here: https://en.opensuse.org/Portal:MicroOS/Desktop#Steam_Proton,_Bottles,_WINE,_Lutris,_Android_Studio_emulator_not_working_from_flatpaks

svin24 commented 1 year ago

There is this odd issue were the game client seems to stop downloading randomly image

LingMan commented 1 year ago

@SViN24 I've seen that only once and it was shortly after a patch release (just like it is right now), so that's probably a server issue on Anets end.

gozes commented 1 year ago

So I think i have come across another small compatibility issue but only on the steam deck . Sometimes an input will get stock and keep repeating over and over again blocking any other aside from movement from taking palace. For example sometimes it will be one of the skills for example 1 you will see the skill flashing like if you where tapping on the key but not actually being executed in the game. Only way I have found to get back to normal is to return to the chart selection screen and goo back in. I'm running it on proton 8.1 on the steam deck. I have yet to try experimental.

Sorry if this not the best place to report this issue.

garpu commented 1 year ago

Should Guild Wars 2 be processing vulkan shaders every time it loads? Or is this the processing shaders bug? (On proton 8.02)

nyannyankas commented 11 months ago

This game's launcher always acted up on Steam Deck, but I feel like it has gotten worse over the last few months:

System Information

Symptoms

Displaying the launcher, which isn't very demanding, causes massive stuttering, especially when it's idle (not downloading patches). The stutter is system-wide, it's almost impossible to open up the Steam menu or even just move the cursor. After the game client has been launched, the stutter is gone. The issue seems to only exist in gaming mode, so it might be an issue related to gamescope?

I've created a proton log in which I've only started the launcher without launching the game itself: steam-1284210.log.

Reproduction

  1. Launch the game on Steam Deck in Gaming Mode
  2. (optional) Wait for updates to finish; the problem becomes far worse once the launcher is idle
  3. Take a look at your FPS graph, as it rather shows seconds per frame instead of frames per second
Kagukara commented 10 months ago

I'm unable to login to the launcher on the Steam Deck, as it loses fps and then freezes up and requires a hard reset. steam-1284210.log

The launcher runs perfectly fine on my desktop (archlinux, swaywm) in and out of gamescope. No issues. Only getting the problem on the Steam Deck.

The issue happens in both Stable and Beta channels, in Preview I can login and get past the launcher, but the fps is ~10fps. I'm unable to use the Preview channel as it likes locks my GPU frequency to 200MHz and a max of 1040MHz (doesn't scale how it should).

Steam Deck Information

UPDATE: Steam Deck just got an update, it no longer needs a hard reset but the fps is basically 0 and very very unresponsive (May as well hard set instead of waiting for it to load, its that slow). This effects the entire system unless the launcher is closed. If I enabled the box for auto-play in the launcher it launches the game. The game seems to run fine but the memory clocks like to stay at 200MHz and a max of 1040MHz now.

If it fails to -autologin I'm unable to press "Login".

Steam Deck Information

LingMan commented 9 months ago

1. Launcher takes 1m20s to show up with Proton 8

This is regressed between Proton 7 and Proton 8. On Proton 7 it takes ~20s for the launcher to appear and be interactable. On Proton 8 this takes 1m20s on my system. I noticed when Proton 8 came out originally but pinned Guild Wars 2 to Proton 7 and forgot about it. Confirmed still present on the current Proton Experimental. Vanilla Wine 8.21 (with or without dxvk) does NOT have this problem.

Similar to other reports above there's system-wide stuttering while waiting for the launcher to appear. Although that briefly happens with Proton 7 and vanilla Wine as well, just not as long.

steam-1284210.log.zip

2. Can't set personal marker on the mini map

Alt + Left clicking on the mini map should place a personal waypoint (20px-Personal_waypoint_(map_icon)) on the map. Instead nothing happens. Tested with Proton 7 and with Proton 8 Experimental. The marker does appear correctly with vanilla Wine 8.21.

Edit 2024-02-07: Turns out the marker appears just fine in a KDE session, but doesn't work in my standard Cinnamon session.

System Information: https://gist.github.com/LingMan/45ed43ceee831550c604dfb583219c75 Steam Runtime Diagnostics: https://gist.github.com/LingMan/af1852e3d7d66ef56e9f2207dcff0ada

kisak-valve commented 9 months ago

Hello @LingMan, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

LingMan commented 9 months ago

@kisak-valve Right, sorry for not including that in the first place. I've edited my earlier post to include all of that info.

alasky17 commented 9 months ago

@LingMan I'm getting the same launch time on Proton 7.0 and Proton 8.0 -- I'm assuming you are timing the time from clicking Play on Steam to the launcher appearing and the "Play" button being usable and purple? I let the game finish downloading completely before testing the launch times as I'm assuming you have the game fully downloaded?

Could you please get a log from the Proton 7.0 launch for us to compare to the 8.0 log?

LingMan commented 9 months ago

@alasky17 Thank you for looking into it! Yes, I'm timing from clicking the Play button in Steam to the launcher being fully loaded. The Play button in the launcher being purple is a good enough approximation for "fully loaded" as I've ignored any attempts that would process Vulkan shaders or download an update.

There are really only two phases that take a long time.

  1. There's no window at all for the first 50-60s with Proton 8. This phase takes ~20s on Proton 7.
  2. Then there's a short phase where the laucher checks for updates to itself. There's a relatively empty launcher window with only the text "Downloading 0%" or something to that effect. That only lasts maybe 1-2s on both Proton 7 and 8.
  3. Then the launcher shows an empty window with the text "Initializing...". This takes about ~20s on Proton 8 but only 2-3s on Proton 7. Screenshot from 2023-12-15 17-02-38

proton7-steam-1284210.log.zip

alasky17 commented 9 months ago

@LingMan Thanks for the quick response! As a heads up, it may be a bit before we get a chance to look at this 😅

LingMan commented 9 months ago

That's fine, pinning to Proton 7 has been a good enough workaround for the better part of the last year (😅) and continues be one for now. And with the holidays coming up: Merry Wintersday! :christmas_tree:

Kagukara commented 9 months ago

I was going to test GW2 again, with gamescope being updated to 3.13.19-1 for this bug, but when I went to go launch GW2 with gamescope the launcher loads but then hangs indefinitely on "initialising..." with btop showing this:

capture_2023-12-21_00-06-43

I have tried with different proton compatibility and its the same result all round when launching with gamescope.

The game launches fine without using gamescope and other games launch fine using gamescope.

I'm not sure when this started as I haven't played GW2 in a while.

System Information

EDIT: I've tried running Gw2-64.exe inside a gaming bottle in bottles using wine-ge-proton8-25, "Gamescope" enabled with the same resolution settings and fullscreen, but I get the same result.

EDIT-2: This also happens on the Steam Deck. Making GW2 unplayable unless you "Switch to Desktop" and launch without gamescope.

Kagukara commented 9 months ago

Gamescope is now working with GW2 on both my desktop and Steam Deck.

Used GE-Proton8-25 and Proton Experimental.

Desktop System Information

Steam Deck System Information

Kagukara commented 9 months ago

Never mind just ran into the same problem again, seems like it happens infrequently.

garpu commented 9 months ago

Has the 6.6 kernel changed how memory and vram is handled? I'm having a strange issue with swap for the past few weeks. With the holidays and infrequently gaming during them, I'm not exactly sure when it started happening.

System Information

If I play for a long time (about an hour or so), I noticed when I load a different area or exit, my swap usage will go up, while I'll still have 6-7GB of system RAM available. Eventually if I don't clear the swap and restart the game, it will slow things down and keep eating swap. (I don't think I've noticed it beyond 1GB swap.)

I've noticed this with other games using dxvk (Fallout New Vegas), but to a lesser extent. I can play Vampire survivors while watching youtube videos and no problems.

I started a discussion over on LQN with the slackware forum, in case it was a regression there: https://www.linuxquestions.org/questions/slackware-14/maybe-issue-with-swap-and-the-6-6-kernel-4175732315/ (It has more details about memory useage and an nvidia-smi dump while it was happening.)

garpu commented 8 months ago

OK...little more testing. I don't see it on anything other than dxvk games through proton. (I can watch youtube videos and play Vampire Survivors at the same time.) I tried the beta steam client, and it still happens. I've also tried Proton-GE. I've upgraded my kernel to 6.6.9. I don't know if this is specifically a Guild Wars 2 issue, though. Should I report it on the steam for linux github, instead? I noticed today that my swap went up when loading a new area, and I still had roughly 2GB of VRAM left and 6-7 system RAM. Any ideas what I should try next? (I even cleaned the dust out of my computer, in case that were impeding performance.)

ETA: adjusting vm_swappiness seems to have fixed the issue for now. I'm still unclear as to what changed to produce this.

LingMan commented 6 months ago

1. Launcher takes 1m20s to show up with Proton 8

@alasky17: Tried the Proton 9 beta and the startup time has vastly improved. Still takes 3-4 seconds longer for the window to appear at all, but for the most part we're back to Proton 7 performance.

2. Can't set personal marker on the mini map

Already added a note to my original report and mentioned it to someone on Discord, but just calling it out here as well: It turns out the marker does appear as expected in a Plasma session, but does not appear in my standard Cinnamon session.

3. Autologin sometimes fails

A new report although as best as I can tell not a regression. The steam version of GW2 should automatically login to the respective account on the side of ArenaNet when the launcher starts. However, something like 10% of the time it doesn't look like it even attempts to login. If that happens, manually clicking the login button logs you in without problems. It just doesn't appear to get triggered automatically even though it should.

(Same for the standalone launcher for which you can pass the -autologin flag.)

Here's a screenshot of the steam launcher where it just stayed logged out: Screenshot from 2024-03-05 02-12-03

Proton logs, one where it logged in fine and one where it didn't: autologin-proton-log.zip

4. Opening an interface with its keybinding sometimes enables autowalk if you haven't moved since starting the game

Reproduction steps:

  1. Start the game and load into a character. Don't move yet.
  2. Press i on the keyboard to open the inventory. Others like h for the Hero Panel or m for the map work as well.
  3. Your character sometimes but not always starts walking forward.

When I was still on Windows this never happened. With vanilla Wine it happens almost every time, with Proton only sometimes. So far I've been unable to reproduce on Plasma, but it's unclear if that was just (bad) luck. Reproducible on at least Cinnamon, Plasma x11, and Plasma Wayland.

Here are two Proton logs. One where autowalk got enabled after pressing a keybinding and one where it didn't activate: autowalk-proton-logs.zip

System information: https://gist.github.com/LingMan/21f5dc07fdb3d45ffba9e1ef96552962 Steam Runtime System Information: https://gist.github.com/LingMan/b07f1b173051f65b34e0132a962c47e7

alasky17 commented 6 months ago

@LingMan I'm glad to hear the startup time has improved with Proton 9.0-x. Thank you for the update! Regarding the remaining bugs, I can't promise anything. Unfortunately 2) and 4) are issues with a very sensitive and complex area of Wine, especially if they are specific to certain WMs :(

Zikkson commented 6 months ago

I have a problem running GW2 on Steam Deck. Everything was ok 3 months ago, but i guess once some update came it bring the problems.

My specs: Steam Deck LCD 256GB SteamOS 3.6 Tried various Proton versions from 7 to 9 Beta

Problem: 9 of 10 starts end in black screen and whole Steam Deck restart. GW2 launcher works, but once i click on “Play” i just got black screen and few seconds later system restarts. The problem occures only in Steam Game Mode so it could be related to performance overlay with gamescope etc. When i start GW2 from desktop mode it works great, but gamescope and performance overlay is missing there.

Could it be a problem with Proton?

nyannyankas commented 6 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/6547#issuecomment-2003168760

I think it's a problem with the current "Main" OS Update Channel. I've reported this bug here a while ago, but it's not fixed as of now.

You should be able to work around it by choosing the "Beta" or "Stable" OS Update Channel (should be OS Version 3.5.17 or lower right now).

nyannyankas commented 5 months ago

The performance issues with the launcher seem to have been fixed in one of the latest bleeding edge versions of Proton Experimental. I've tested this on my Desktop as well as on my Steam Deck and both have no issues rendering the launcher anymore. This was an annoying problem for years. Many thanks to whoever fixed it! :)

kisak-valve commented 4 months ago

Weird timestamp in GuildWars 2

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7699. @Coolgeek789 posted on 2024-05-04T18:38:46:

My system : OS : Archlinux CPU : Intel 13900KF GC : RTX 4080 (driver nvidia 550.78) Kernel : 6.8.9-arch1-1 Desktop : KDE 6 Language : French (fr_FR.UTF-8)

Since Proton 8 (still the case in Proton 9 and current git), I have a weird issue in Guildwars 2 (AppID : 1284210). In the chat, I have the timestamp displayed in a weird way (the part in gray, at the beginning of the line):

GW2 after (translation : 7h22 of the afternoon)

In Proton 7 (the way it is on Windows) :

GW2 before

I tried to set LC_TIME=C and LC_ALL=C in the launch command in Steam but there was no change. Current launch command : DXVK_ASYNC=1 %command% -ignorecoherentgpucrash -provider Portal

I tracked down the commit that does it : https://github.com/ValveSoftware/Proton/commit/2b95bc1771194a59204104ddc475739858fe5cb3

Removing it does the trick.

Is there a way to fix this ?

Thanks

LingMan commented 4 months ago

4. Opening an interface with its keybinding sometimes enables autowalk if you haven't moved since starting the game

Just an update that this issue is not WM specific after all. It reproduces on Plasma (both x11 and Wayland) as well as Cinnamon.

BetterToAutomateTheWorld commented 4 months ago

4. Opening an interface with its keybinding sometimes enables autowalk if you haven't moved since starting the game

Just an update that this issue is not WM specific after all. It reproduces on Plasma (both x11 and Wayland) as well as Cinnamon.

I have this exact same issue, Gnome3 X11, and it's not happening always, as initially described I tried a 'xset r off' out of curiosity before launching the game and it didn't help

Coolgeek789 commented 2 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/6547#issuecomment-2094346806

Fixed in proton experimental. Thanks !

zookee1 commented 1 month ago

Janthir Wilds just dropped and now the game won't launch for me anymore.

I am using a portal account on Steam, running the game in Proton Experimental bleeding edge and I have used the following launch paramenters: -provider Portal +log_verbosity 4 +log_WriteToFileVerbosity 4 +sys_dump_type 3

This is the content of the debug.log:

[0820/185228.659:ERROR:network_change_notifier_win.cc(225)] WSALookupServiceBegin failed with: 0
[0820/185228.673:ERROR:dxva_video_decode_accelerator_win.cc(1457)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)
[0820/185233.427:WARNING:cert_verify_proc_win.cc(89)] Unknown error -2146762482 mapped to net::ERR_FAILED

My system: Kernel: 6.10.5-arch1-1 CPU: 12th Gen Intel i5-12600K GPU: NVIDIA GeForce RTX 3070 Ti

Can anyone confirm this?

LingMan commented 1 month ago

Still launches for me with Proton Experimental (non-BE). Running through Steam with -provider Portal just like you. AMD 7800X3D + Radeon R9 390. EndeavourOS with the same kernel.

Do you maybe have some thrid-party addon installed? I've had e.g. Arcdps cause crashes after a game update before. Not this time though, it just doesn't show any info.

nyannyankas commented 1 month ago

I have the same issue with bleeding edge, but I think it isn't caused by the Expansion's release. For me, this beta branch has already been broken for a few days in GW2. Proton Experimental with no beta branch selected works fine, though, I'd recommend using that for the time being.

zookee1 commented 1 month ago

Running EndeavourOS as well. I just did a clean install and tried again to no avail.

What did work was not choosing a beta branch as @nyannyankas pointed out. This makes the game playable for me. Since another game I currently play still needs the experimental branch, I'll just have to juggle the beta versions between sessions.

Thanks for the help!

Blisto91 commented 1 month ago

Thank you for the reports. It should now work again with a up to date Bleeding Edge too.

nyannyankas commented 1 month ago

Unfortunately the game still doesn't seem to work with bleeding edge. Same error:

[0821/024306.894:ERROR:network_change_notifier_win.cc(225)] WSALookupServiceBegin failed with: 0
[0821/024307.230:ERROR:dxva_video_decode_accelerator_win.cc(1457)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)
[0821/024307.456:ERROR:network_change_notifier_win.cc(225)] WSALookupServiceBegin failed with: 0
[0821/024310.321:WARNING:cert_verify_proc_win.cc(89)] Unknown error -2146762482 mapped to net::ERR_FAILED

Note, that this error only occurs after hitting Play in the launcher.

Blisto91 commented 1 month ago

@nyannyankas Those errors always appear for me even when the game works fine. Can you post a Proton log from bleeding edge where the game crashes?

nyannyankas commented 1 month ago

@Blisto91 Yes, you're right, these errors seem to always be there. Sorry for not catching that.

I've attached the Proton log here: steam-1284210.log. I've also copied the error message from GW2's error reporting tool. Maybe it can be helpful as well: gw2_error.txt.

Thanks for your help. :)

Blisto91 commented 1 month ago

@nyannyankas I've switched to a Nvidia GPU but i haven't been able to reproduce yet. Which distro/desktop environment do you use?

nyannyankas commented 1 month ago

@Blisto91 Manjaro using Kernel 6.10.5-1 with Gnome. The Nvidia driver is at version 550.107.02, if that helps. No special modifications or anything.

Blisto91 commented 1 month ago

@nyannyankas Does it make a difference if you launch with PROTON_DISABLE_NVAPI=1 %command%