Original Post — Direct link

Not sure if they’re actually the same bug or not but I’ve been noticing them a lot more lately.

External link →
over 5 years ago - /u/ChrisGansler - Direct link

We'll look into this asap. As we're trying to find out what caused this to come back, can you let us know what activities this is happening the most? I played a bunch of challenging missions on the weekend and it only occurred in those for me, other activities were as expected. Let us know what your experience is like.

Sorry for the inconvenience, we're pretty unhappy that this has resurfaced.

over 5 years ago - /u/ChrisGansler - Direct link

Originally posted by KevlarD-

It would be really nice if you guys/gals play the game a bit more tbh so that you too can see the problems we are having. I'm just glad you actually play. "Right anthem? "

But on the issue at hand... it's literally everything. Freeroam, dz, raid, every mission every everything.

Really glad to see you guys posting it keeps my hopes up for the game and future content.

Just to clarify, we have a bunch of people playing The Division 2 in their free time and also people at work playing it (Quality Assurance / testers, etc.). But our experience is not 100% the same as the experience of all other players out there.

Like, I played Open World on the weekend, WT5 and I had no issues with rushers at all. But that doesn't mean that it's not happening. This is why we speak to you guys whenever we can, so we get a better picture of what you're experiencing and how it differs to what we're seeing.

over 5 years ago - /u/ChrisGansler - Direct link

Originally posted by gX-kiD

Come on Chris, aren't we past that?

You guys played this broken record for almost 3 years in The Division 1, and eventually you guys have never really fixed this issue.

Are we really supposed to have the exact same conversations again for the next 3 years?

I was not here for The Division, so I can't comment on that. From what I understand, and what the community on reddit is telling me, this was already fixed prior to Title Update 3. If you think this has always been broken, between TU2 and TU3, let me know and we can further look into it.