Guild Wars 2

Takagi Chrome.4619:

Well, the pips that I earned prior to hopping maps didn’t register to the new reward (Wood). So after coming to a new map, I had to start back with 0 pips when I should have been halfway to finishing Silver.

Yeah, that is how this would present. The issue here is that the pips didn’t reset when they were originally supposed to so they got put into the pre-reset version and then when you switched maps it reset correctly.

Did you happen to join WvW immediately after reset?

Thanks for the additional information. I think I now know what this is and it should fix itself the next time you change between WvW maps if I am correct. I believe the case that is occurring is that your pips failed to reset when entering WvW for the first time after reset.

Sorry for the inconvenience, but I should now be able to get this fixed properly in a future release due to the additional information.

Could you please post more information about this? Are you still earning the chests even though the pips don’t appear in the UI? A screenshot of the second tab of the WvW panel would be quite helpful in determining what exactly this is.

Also, is there anything else not updating? For example, are you also lacking the time until skirmish ends timer?

This has been resolved.

We’re aware of the issue and are working on fixing it.

Uh. That doesn’t look right.

I’ll look into this.

Do the scoreboard or other maps function at all while this isn’t working? I’m trying to establish if your client is losing a connection to all of the WvW data, or only pieces of it. If only pieces you may still be able to see changes to other maps or your scoreboard.

The next time you see this bug could you please try swapping maps or logging out and back in again to see how this affects the bug? The rarity of this bug leads me to believe that this is your connection to the server that is storing the data used for rendering onto the map and so restarting that connection may fix the bug.

Please reply with or message me the results as that would help a whole lot with investigating this further.

Before posting about new crashes please read the rest of the thread to see if your crash is one that has already been addressed.

Zachary Stiers.1879:

msalakka.4653:

Assertion: index < m_count
File: p:\code\gw2\game\content\CnUtil.h(99)
App: Gw2-64.exe

I can reproduce this as many times as you want by going to WvW and hovering mouse over the reward track chest icon atop the minimap.

Thank you for the additional information. I’ve now found the offending code and am looking into potential fixes.

Here is a temporary work-around until the real fix is released:

1. Open your World vs World panel
2. Go to the reward track tab
3. Activate a track

This is happening because you currently have no track actively able to receive points and that case was not properly handled.

msalakka.4653:

Assertion: index < m_count
File: p:\code\gw2\game\content\CnUtil.h(99)
App: Gw2-64.exe

I can reproduce this as many times as you want by going to WvW and hovering mouse over the reward track chest icon atop the minimap.

Thank you for the additional information. I’ve now found the offending code and am looking into potential fixes.

Tyrx.2471:

All my crashes in WvW have the same wording for the assertion, file and app lines.

—> Crash <—
Assertion: (m_sphereRadius + TOLERANCE >= m_boxExtent.x) || (m_sphereRadius + TOLERANCE >= m_boxExtent.y) || (m_sphereRadius + TOLERANCE >= m_boxExtent.z)
File: ..\..\..\Engine\Gr\GrBound.cpp(94)
App: Gw2-64.exe

This is another game-wide crash dealing with parts of the rendering pipeline. We are aware one is bad throughout the whole game.

Aileras.9460:

—> Crash <—
OOM: Heap, bytes=8389088,
App: Gw2.exe
Pid: 5692
Cmdline: -perf -windowed
BaseAddr: 00400000
ProgramId: 101
Build: 64926
When: 2016-08-03T02:20:51Z 2016-08-02T19:20:51-07:00
Uptime: 0 days 1:30:20
Flags: 0

think mine is running out of memory.. but just in case

You are running out of memory. If you are able to run it I would suggest using the 64-bit client as it should not suffer so badly from this problem.

smid.3418:

Here’s the crash I just had:

—> Crash <—
Assertion: MathIsUnitVector(forward, 0.01f)
File: ..\..\..\Game\AgentView\AvUtil.cpp(286)
App: Gw2-64.exe

This particular crash is not specific to WvW but it is being investigated.

If you are continuing to get these please reply with a copy of the top section of the crash report. It will be formatted similar to the following:

*-- Crash --*
Assertion: ...
File: ...
App: ...

If you send me those three lines it would help immensely with establishing exactly what crashes these are and whether or not they are limited to WvW. If these crashes are not related to WvW but just happen to also occur in WvW I will have this thread moved to the generic bug subforum.

This should only be a cross-map visual bug. This means that some of the information you see from a different map might be wrong, but while playing on the map the objective is actually on information should all be correct. If this turns out to not be the case in any situation please let me know.

Thank you for bringing this to our attention and I apologize for the inconvenience.

Note: Because the external WvW API should still be function correctly websites that display information from there should still be working.

Arrow carts have a special type of line-of-sight calculation. This type of calculation allows for shooting from the top of walls to the bottom of walls, even from farther back on the walls. This is because in standard line of sight you would have to build the arrow cart right up on the edge of the wall which makes the arrow cart effectively worthless as targeting them down is trivial.

Sidenote: This is true for all of WvW and is unrelated to the new maps. You will see the same thing in Eternal Battlegrounds.

Ameepa.6793:

Thanks for the answer.

Is there any chances for the cap to rise? 1000 is very low cap considering the huge size of the halls. Ours still feels almost empty at cap and we don’t even have the lvl 40 exploration yet.

1000 would be fine for a hall 1/10 of current size.

I did not write this code so I unfortunately do not have a definite answer to this, but I think this number is based on a technical constraint.

Xanthia.7209:

I do want to discuss that there is discrepancy between what is being stated as the actual intended cap for decorations. Two say it is 2000. One says it is 1000. They are both recent statements that were made by official employees of Anet. I am just pointing out the conflicting statement and hoping someone here (an employee with the codes in front of them) can recheck and confirm what it is. I am pretty sure that is a reasonable request.

I checked the code before I posted my original reply.

The maximum number of decorations is 1000.

Dawdler.8521:

So out of curiousity, are the these going to be global changes or WvW specific?

I mean come on. At least share the WvW love with PvE.

The rally and resurrection rules are WvW specific and only apply to players.

Dream In A Dream.7213:

How is ppk counted if players from 2 servers contributed damage?
Both get a point?

Both teams would get a point. This question was asked in greater detail one of the previous times PPK was turned on and the answer is still accurate.

Some clarification on a bit of confusion I saw:

• When a dolyak reaches its destination it contributes to the upgrades of both the objective it is reaching and the camp it started at.
• Rally order is closest-first. Combined with the rally limit of one this means that only the nearest downed player will rally off an enemy death.
• Resurrecting the dead cannot be started in combat, but entering combat while already resurrecting someone will not force you to stop.

The next patch will contain adjustments to arrow cart line of sight calculations to address this problem. Due to feedback the new calculation will give advantage to defenders by being forgiving when the arrow cart is being fired from higher ground to lower ground.

This is a complex problem. The intention was to make it harder to fire from the ground onto and over walls while still being able to fire from walls downward, but trying to get such behavior is not simple. I do agree that the cases displayed in the screenshots are not great though.

This is an idea we had during development and was cut during investigation due to technical and messaging problems in both of the ways it could be implemented.

• If it worked by consuming the upgrade immediately then you may have spent an upgrade that you not only never got to use, but may have never even started building.This would be a likely case as objectives are not always held long enough to get all the way through every tier.
• If it worked instead by not consuming the upgrade until the tier became available it ran into potential problems with coordination across multiple maps. Because your guild can hold one objective per map your guild could now easily be in a state of reserving more of an upgrade than your guild actually owns.

With Heart of Thorns the exotic equipment purchased with gold and Badges of Honor will become salvageable. Salvaging a piece of this gear returns only the upgrades that were applied and some Badges of Honor.

The change I mentioned previously is multi-part. The change that makes all arrow carts use line-of-sight did indeed go out today, but the second part about the arrow cart line-of-sight checks being too forgiving was not part of today’s build. The changes to the way arrow cart line-of-sight is calculated is set for an upcoming patch.

slingblade.1437:

slingblade.1437:

Jayne.9251:

Just hope he means both ways. Cos if they are limiting from behind walls only .. well, lol. (Behind implies being inside a structure, not outside).

I think he means both ways. I suspect the term “behind” is meant to refer strictly to the relationship between the AC and the target, i.e., any situation where the there is a wall between the AC and the target.

This explanation is what I meant. I was using the word “behind” to refer to the target being on the opposite side of an obstacle. Sorry for the confusion as I could have been clearer originally.

An upcoming patch will contain changes to how line of sight is calculate for arrow carts. Some of the arrow cart skills ignored line of sight and the rest were too forgiving with their line of sight calculations. Both of these issues allowed players with modified cameras to shoot an arrow cart from behind walls to locations they shouldn’t have even been able to see, much less fire at. In the future arrow cart skills will use a special type of line of sight checking specifically designed to reduce this problem while still making the allowed target areas feel reasonable.

1. 1 point goes to World 1.
2. Nothing.
3. 1 point goes to World 2.
4. 1 point goes to World 3.
5. Nothing.
6. Nothing.
7. 1 point goes to World 1 and 1 point goes to World 2.
8. There is not enough context to answer this question.

Each team containing a player that contributed to killing another player gets a single point for that player’s death. This means if anyone dies to only NPCs no points are awarded to any teams. If multiple people from the same team contributed to killing a player only point is awarded to their team. If multiple teams contributed to killing the same player then each contributing team gets a point.