tails.4209

Account: tails.4209 From: Sorrow's Furnace Current Team: First Haven Expected Team: Seven Pines WvW Guild: MODE I had to leave my regular WvW guild JADE to join our guild's alliance guild (for the love of God, give us a guild slot). Selected MODE as my WvW guild last night before the deadline but it still showed pending. Today, didn't seem like it put me with guildies in the MODE alliance guild. Edit: Forgot to update. Not sure if was moved manually, but I logged on on Saturday to check and I was moved to the right team!

Skill lag is still pretty bad in FA/DH/FC matchup FCBL (ip: 50.16.132.167) on reset night.

Maybe Anet's vision for WvW is just lag optimized builds 111-ing.

For WvW, they really should address the server lag before anything else. They can give us shiny new skills or gameplay, but it's kind of useless if it takes 30 seconds to cast everything.

Do we need to start a GoFundMe for WvW server scaling? Seems like the budget was spent for the WvW beta.

It seems like the WvW Guild selection was reset or not remembered at some point during the first week of the beta. It was selected prior to the start of the first week of the beta. Guildie mentioned it in our Discord but I didn't see the message until today. The UI on the WvW window to select WvW guild doesn't work and the UI in the Guild window to set WvW guild also doesn't work. It seems guild selection is already locked for the second week of the beta. Praying that it's just a UI bug so I can still be in the same team as my guild. It seems like we can't trust GW2 to remember our guild selection week to week even though the guild selection from previous betas seem to be retained. This is like pre-Alpha quality...

I finally bit the bullet and installed lutris and its dependencies instead of running my system wine natively. I used the lutris install script from lutris.net, interrupted the install and in the wine prefix, symlinked my already installed and fully patched GW2 (I dual-booted into Windows briefly to run raids). Things seem to be working well so far...Even trading post and guild panel seems to work... Lutris: lutris-0.5.10.1 Wine Version: lutris-GE-Proton7-1-x86_64 Video drivers: nvidia-drivers-510.73.05-r1 Using DX11

Had a working setup with wine-staging-6.16 and dxvk-1.10.1. However, with the latest patch, the game crashes on login screen. I see this in the console window when this happens: Not sure if this is what's causing the crash with CoherentUI, but maybe something along the lines of CoherentUI change causing the Vulkan translation in dxvk to use an unimplemented rendering feature in wine. CoherentUI didn't like that it failed and crashes, maybe? I found a reference to this wine bug but can't try the patch at the moment: https://bugs.winehq.org/show_bug.cgi?id=45277 Without dxvk, I was able to log in and play. It's not using the dxvk vulkan translation, so it doesn't require child window rendering. Obviously performance took a nosedive without dxvk. Edit: Looks like a patch to implement child window rendering was included in wine-ge-custom. So that probably addresses one of the issues...

I've had pretty good performance with DX9, wine-staging, and dxvk even in huge WvW zerg fights. However. when I moved from wine-staging-6.9 to wine-staging-7.2, performance takes a huge dive during the same fights. I've seen FPS drop to 1fps. This aligns with a huge ping spike. It's probably a long shot, but does anyone know what might affect performance between the 2 wine versions? Is there an option I can try?

It's more than that just Dragonstorm. There's been more occurrences of inconsistent rendering since EoD launch even with DX9. Some AoEs (e.g. vomit under giants in Harvest Temple and field underneath Ankaa in Junkyard) and telegraph circles (e.g. slam/wave attack during Dragon's End meta) won't render the first time they hit. I have a feeling it's probably to do with asset loading performance. Is your gw2.dat file on an SSD? I'm still running into the same issues with an SSD but I feel the frequency is less compared to my mechanical drive friends.

I thought I ran into the same problem too, but after opening all the bouncy chests on the bottom right, I got the achievement. I right-clicked all my bouncy chests though to skip the dialog showing contents.

For some maps like Queensdale, there are many places where the skiff can easily run aground when following water. I don't know if it's worth making those areas deeper, but it's pretty annoying trying to go down certain rivers. For example, sailing from Western Divinity Dam to Lake Delavan to Eastern Divinity Dam in Queensdale is difficult if not impossible.

I got the badge from the Champion Sarin event in Old Kaineng City.

I just got the Badge of the WIllbender drop from the Champion Sarin event in New Kaineng City. It was around "Field Notes 3" in Old Kaineng. Time to get your weapon. 🙂 https://cdn.discordapp.com/attachments/140245369224298496/952431791787089920/unknown.png

As far as I can tell, the bot only triggers on items coming into your inventory. If you have junk items already in your inventory, the bot won't work on them.

I can confirm that it's working again. Just got 2 jade slivers and the message in chat "your jade bot recycled some junk."

Can anyone confirm if the bot is working again?

Has there been any official communication on disabling the recycler? Should we just remove the module and use something else in the meantime to at least get some QoL out of the jade bot slot?

1) It is entirely possible that it's the same issue but some were lucky to not get hit by it in beta 2 but unlucky in beta 3. 2) We're not entitled to any explanation, though I would be very interested in a postmortem. It could very well be the same cause but they are now embarrassed to admit it. I'm concerned if they are just shooting off betas to meet some schedule set by management for betas instead of actually taking the time to develop a beta worth testing. Releasing a known buggy beta to the masses just wastes developer time. I wouldn't be annoyed if it was opt-in and there's an option for users to go back to the old system. Maybe they don't want to invest in parallel WvW infrastructure for beta testing. However, if WvW is in long-term beta status like you implied, then it would be a pretty easy cost to justify.

1. Considering the wrong team bug affects the experience of users for a core feature without any sort of workaround, I would argue it's high severity. And it does affect some number of users. A high severity bug affecting a fair number of users should be a release blocker for betas. They had a chance in beta 2 to fix it and add enough debug info to verify it's been fixed. Most of the issues were found in beta 1. We're at beta 3 and the same bugs are still showing up. 2. That reasoning is acceptable for beta 1. Probably acceptable for beta 2. By beta 3, they should have identified the gaps in their test coverage. Space out the time between beta more if more time and investment is needed to get test coverage in place.

"Ship a beta to test basic functionality that continues to be broken from previous betas." Nah, bruh. That's not how development works.

Yeah, like the basic feature. And this is just players who care enough to complain. I know others who just took a break from the game for a week.

I think the same logic that excuses issues with the beta can excuse any issues caused by attempted fixes with a tool. It's a beta.

Is server militia still a thing? I can't imagine how that would work with alliances.

If you get hit by the wrong team issue, it doesn't matter what guild you select.