Guild Wars 2

Forum bug, on a thread about a WvW bug…maybe posting in bug forum section will fix it right?

Sometimes disbanding and remaking squad helps fix this issue. Also if anyone uses tonics or does certain things with their legendary armor it can increase waiting time at a waypoint. Also I noticed when someone moves claims around and are waypointing this may be an issue too.

UPDATE – another hint for developers: I have the bug only when the graphics preset “Best Appearance” is used. Changing this to “Autodetect” causes the problem to disappear entirely, so it probably has something to do with the settings for Environment, Textures, Shaders, or Hi-Res Character Textures. Will experiment with these to see if I can narrow it down.

I was routinely experiencing ~2 min load times in WvW, switched my graphics settings to auto-detect and it’s totally fixed, down to ~10 seconds every time. That’s with a GTX 1070, so it’s not like I just have a slow computer. One other piece of advice to to add “-maploadinfo” to your GW2 startup shortcut options, that will show the loading percentage. This is not a hardware issue, it’s a bug in the engine code that loads textures.

I can now report that it is happening to me in PvE as well. I’m working on map completion (ugh….) to make a legendary and I have to relog approximately 3 times per map now.

In my case the screen always takes 121 seconds (in PvE and in WvW). I’ve always had -maploadinfo so I can see exactly how long it takes and I also see that it continues to reload the same assets over and over again for the entire time.

We should find some way to duplicate this issue in a Raid. It’d get fixed lickety split.

Anyone having crashing issues along with this? Any screen flickering when clicking on a WP or when opening any panel like, inventory?

Chris Barrett.3280:

We’re aware of a bug where loading screens can sometimes take 2+ minutes to complete; more often after playing in WvW for a while than elsewhere in GW2. We’re working on a fix in such a way that it can be selectively tested on Live, since it affects a vital area of GW2 behavior (loading screen timing), and is rare/difficult to reproduce in a testing environment.

In the meantime, if there aren’t queues in the maps you’re playing in, there’s a possible work-around. Switching maps— either by exiting WvW or just moving to a different WvW map momentarily— appears to get your client “unstuck” from the long loading screen behavior.

hello Chris it’s good you acknowledge this.

As i seen the long loading screens appear also when the the game behaves erratically:

• NPCs models aren’t shown. Lords, guards only show the name tag but the model is not there. Still are affected by weapons and damage.

• Players models go back to default models. Some backpacks are still shown but any other detail dissapear.

• Self skills and most effects are not shown in game. For example ancestral grace animation changes to the player to run really fast.

• This always happens after some time of gameplay. It may be because some windows memory operations (defragmenting, compressing or freeing space)

My take on this is the game at some point mess up with the graphics library allocation and it takes that longer to load because it can’t find such graphics\models. As such it takes longer because it waits for each loading object to retrieve the error loading\not found code.

If that is the issue at hand should be enough if this error is detected to rebuild\reload the graphic\models library on the fly instead trying to load something is not there. It will take long once but after that it should go back to normal.

hope this gets fixed because when we need to defend if a map and u have to wait for 2 minutes, you then lose such structure.

It’s been quite a while, would be nice to have an update from Chris.

Sovereign.1093:

hope this gets fixed because when we need to defend if a map and u have to wait for 2 minutes, you then lose such structure.

Whoa whats the rush? Give them some time to properly narrow down the problem first.

This is a 6 year process that anet sometimes manages to do within 3 years. Its only been a mere 5 months since they admitted its an issue.

chicken nuggets