Guild Wars 2

@Squall – I understand that it’s on mumble’s end that you have to use -nopatchui. However, it’s a change on GW2’s end that broke the workaround. I was merely asking if this was intended and if anet could help provide a solution. Your examples are a electronic storefront anet has partnered with and a shareware-like utility program that indiscriminately applies itself to any application. Mumble is attempting to respect the users wishes on what programs it applies itself to. Obviously there’s a solution here, but your comparison isn’t apples to apples.

@Parrin – Hmmm. I have not tried this myself. I will have to just to be sure. Makes me wonder why I would have to though. I mean what changed on GW2’s end that requires full access to your machine just because you’re bypassing the login screen? On voicechat programs I always assumed that it was an issue with hardware access/keyboard bindings. I’ve never had to give mumble this access though. /shrug.

Over a month ago the wiki had a solution for getting mumble overlay to work which entailed using the -nopatchui switch as well as the login credentials. This worked (security concerns aside) but as of the latest patch (11/15) this causes an issue with the TP and the wiki has been updated since then not to include this workaround. I’m sure this was an unintended change/collateral damage. Any solutions or is mumble overlay a casualty for now?

I’m assuming the heart of the problem is that the launcher isn’t a 3D application itself that mumble can apply it’s overlay to? It appears I was wrong and it’s the opposite. The launcher is creating a D3D device which mumble attempts to create it’s overlay on and never sees the D3D device for the game proper (according to mumble bug list). In an ideal world there would be some way of getting it to work without bypassing the launcher so that patches and support for the authenticator isn’t lost in the future.

TL:DR – Is support for the -Nopatchui commandline switch being deprecated in lieu of issues like the one I linked above? Is there any chance that an olive branch could be extended to the mumble guys to find a solution to their overlay bug? A cleaner solution would be nice for everyone. I miss my overlay. :’’(

Thanks in advance for any info.

Update2: Ok, I solved it. I was using command line options to bypass the launcher for the mumble overlay support. Once I logged in normally with my unaltered shortcut the error went away. Tbh I should have thought of this sooner as this is login related, but I’ve had this working for weeks and the latest patch apparently broke it.

Incidentally, can anyone at areanet comment on any plans to make mumble overlay support a little more secure? I imagine the google authenticator support is out the window if you bypass the GW2 launcher as well?

TL:DR – Solution: Make sure you don’t bypass the launcher for any reason.

Do you not get any search results at all? Or do you get stuck with an endless wait icon? If it’s the later and you just can’t click on any of the results (because it’s endlessly searching) then the solution I’ve found is not using the autocomplete dropdown. That is when you type in a search term do not arrow down or click on any of the suggested searches that appear. If you type everything by hand and hit enter you’ll get your search results without an endless wait state. This has been an issue since I started playing the game.

Update: Made sure everything was updated, rebooted, solved an unrelated firefox issue with it’s bootstrap app. Issue persists. Disabled local firewall temporarily to make sure update there didn’t cause issue. No dice.

Getting this too as of the patch (even the second one that corrected achievements). Nothing else has changed. Before I got the error above I noticed that I couldn’t sell anything. When I clicked on an item the transaction details would not display. I also noticed a bit of lag on certain UI screens displaying so I tried updating my video driver. Obviously this error suggests it’s a connectivity issue. Anyway to determine if this is a temporary routing issue? Tho if this is literally the login server I don’t know how I’m able to login at all if it’s a routing issue.