insanelyapple.2870

I'm running Lutris almost successfully for more than a month now and I wonder if someone noticed weird mouse and camera behavior while playing among large number of people like squads (joined or not) or world bosses: sometimes camera refuses to stay in place and starts to spin character around either clockwise or counter clockwise, some rubberbanding while moving happens and often skills fails to be executed by keyboard - there's a significant delay but none if I'm operating with mouse (while trying to have camera in place). None of this happen when I'm in less dense populated areas but might happen while doing fractals. I have copied Windows client graphics and audio settings and none of this happens there; issues are present on SSD as well as on HDD. I'm not sure if this is Manjaro GNOME specific behavior related to display server and my GTX 670 or something between Lutris settings: Wine version - lutris-5.7-11-x86_64, DXVK - 1.7.3L-03f11ba. Edit: I forgot about another issue with Bjora Marches map - while swapping between parked characters there, I'm getting OOM errors since last update - I have 8GB of physical RAM and additional 17GB of swap (both as file and partition) since I've experienced OOM freezes during first attempts with launching GW2 with Lutris but even with all of it, Bjora Marches flips running client but any other open world map or instance works properly. So again, has someone experienced similar stuff and knows how to deal with it?

> @"Denpakei.7326" said: > > @"Kraizer.2350" said: > > > @"Denpakei.7326" said: > > > > @"insanelyapple.2870" said: > > > > I'm currently testing launching game with Lutris on my machine (which isn't super fast for today's standards - C2Q, 8GB RAM and GF760) under Manjaro Linux x64 and well... it seems it runs much better under Wine than it does native on Windows 10 - graphics are much better but without burden of frame drops or lagging while turning camera view around. > > > > There's one problem I cannot figure out - game launches only once after initial Lutris setup (tested out after clearing .config folder out of Lutris files) and any subsequent launch ends up with Error Code: 42:0:9001:4457. I tried launching with arguments for different port - no luck. So I wonder, did someone bumped on such problem and found the solution? > > > > > > Hi man. I have same issue today. > > > The most funny thing... Actually i installed gw2 on new hardware, everything fine then... boom! cant log in, im sure its not router problem or firewall. I have gw2 on laptop too, with the same OS, same firewall... and its sound "funny" but on my laptop i have no log in problems. Im confused. > > > I welcome any help btw. > > > > It's possible it's related to the version of Lutris that is being used. I had that issue since the 15th, and I found a solution for myself today - just switch the Lutris version from V6.0 to V5.7-11. You can do this by Right clicking on Gw2 ---> Configure ---> Runner Options ---> Wine Version. > > I don't know why it fixed my problem, but it did. I ran 2 fresh installations, both under V6.0. The moment I rolled back to 5.7, I could log in. > > It works! Really big thank you! > i also switched vulkan ICD loader from amd_icd64.json to radeon_icd.x86_64.json bcs i had black screen and... it works now :) > Thank you! It worked for me as well - thank you for discovering this! Tho, the question remains, why version 6.0 terminates the connection...

I'm currently testing launching game with Lutris on my machine (which isn't super fast for today's standards - C2Q, 8GB RAM and GF760) under Manjaro Linux x64 and well... it seems it runs much better under Wine than it does native on Windows 10 - graphics are much better but without burden of frame drops or lagging while turning camera view around. There's one problem I cannot figure out - game launches only once after initial Lutris setup (tested out after clearing .config folder out of Lutris files) and any subsequent launch ends up with Error Code: 42:0:9001:4457. I tried launching with arguments for different port - no luck. So I wonder, did someone bumped on such problem and found the solution?