Hi all,
I wanted to add to the above mentioned problem. First of, I can also say that everything worked fine before Friday and since then the game showed the rendering issues mentioned above. I can also reproduce that switching out of the steam beta makes the game run again.
After failing to get it to run under steam with different proton versions I tried to install the game via Lutris and this also failed.
Interestingly the client crashed under Lutris (also tried different runners) and returned always the following error message:
*--> Crash <--*
Assertion: Launcher: Browser crashed
File: D:\Perforce\Live\NAEU\v2\Code\Gw2\Game\Launcher\LauncherCoherent.cpp(2559)
App: Gw2-64.exe
Pid: 704
BaseAddr: 0000000140000000
ProgramId: 101
Build: 136147
When: 2022-10-24T15:48:20Z 2022-10-24T17:48:20+02:00
Uptime: 0 days 0:00:03
Flags: 0
[...]
*--> Error Logs <--*
15:48:18Z Failed to open GFE XML: 2
15:48:20Z Browser view crashed
Crashed at 15:48:20Z
Some thoughts on this:
I assume `LauncherCoherent.cpp` shows that it is a problem with `CoherentUI`?
Before switching to steam I did install GW2 via Lutris. I would say seeing that the game is still broken on Lutris indicates that just switching off from steam-beta is not actually solving this new problem. Especially since it did previously run even under the steam beta. I would like to know if the Lutris version of the game was also working until around friday? Can anyone confirm or deny this?
I also noticed the falsely rendered UI only shows up under (Gnome) Xorg while running (Gnome) Wayland does not show the falsely rendered UI and just gets the launcher stuck on "initializing".
I can also confirm that after logging into the falsely rendered UI by just pressing a few times 'Enter' and/or 'Tab' the game actually launches without problems. I can open the inventory and also other menus in the game without problems the only window that does not render right is the trading post.
Some further information:
At first I thought there might be a problem with my gpu drivers (AMD + mesa: 22.2.1-1) but given that other people report the same problem with nvidia I assume this also falls flat.
Hi all, I wanted to add to the above mentioned problem. First of, I can also say that everything worked fine before Friday and since then the game showed the rendering issues mentioned above. I can also reproduce that switching out of the steam beta makes the game run again. After failing to get it to run under steam with different proton versions I tried to install the game via Lutris and this also failed. Interestingly the client crashed under Lutris (also tried different runners) and returned always the following error message: *--> Crash <--* Assertion: Launcher: Browser crashed File: D:\Perforce\Live\NAEU\v2\Code\Gw2\Game\Launcher\LauncherCoherent.cpp(2559) App: Gw2-64.exe Pid: 704 BaseAddr: 0000000140000000 ProgramId: 101 Build: 136147 When: 2022-10-24T15:48:20Z 2022-10-24T17:48:20+02:00 Uptime: 0 days 0:00:03 Flags: 0 [...] *--> Error Logs <--* 15:48:18Z Failed to open GFE XML: 2 15:48:20Z Browser view crashed Crashed at 15:48:20Z Some thoughts on this: I assume `LauncherCoherent.cpp` shows that it is a problem with `CoherentUI`? Before switching to steam I did install GW2 via Lutris. I would say seeing that the game is still broken on Lutris indicates that just switching off from steam-beta is not actually solving this new problem. Especially since it did previously run even under the steam beta. I would like to know if the Lutris version of the game was also working until around friday? Can anyone confirm or deny this? I also noticed the falsely rendered UI only shows up under (Gnome) Xorg while running (Gnome) Wayland does not show the falsely rendered UI and just gets the launcher stuck on "initializing". I can also confirm that after logging into the falsely rendered UI by just pressing a few times 'Enter' and/or 'Tab' the game actually launches without problems. I can open the inventory and also other menus in the game without problems the only window that does not render right is the trading post. Some further information: At first I thought there might be a problem with my gpu drivers (AMD + mesa: 22.2.1-1) but given that other people report the same problem with nvidia I assume this also falls flat.
