Original Post — Direct link
over 4 years ago - /u/ChrisGansler - Direct link

Hey! We've been gathering user accounts to further look into this. We're currently unable to reproduce this in-house and are therefore looking to get more info from you guys.

Please DM me your user account (platform and Ubisoft) and we'll further investigate this.

over 4 years ago - /u/Ubi-Johan - Direct link

Originally posted by Simon-says-what

Come on, stop wasting everyone's time and hope. This issue exists since the first days of TD1 (yeah, I know, not your fault as you weren't there) and will most likely never be fixed.

First you blamed the shooting range, once that bluff got called you blamed it on the connection of players, now it's apparently the accounts .....and this "blame & investigate" game will go on forever and ever with nothing to show for in the end.

We're closing in on 4 years of a shooter game that doesn't register bullets reliably, and we don't even have a shred of an answer on it.

Sorry to hear that you feel we're wasting players time. We are simply asking for the required information in order to investigate potential underlying causes.

The shooting range was a separate issue and not related to what we're seeing in this video.

These sort of issues can be caused by a myriad of potential reasons, including (but not limited to) the game servers themselves, the players connection or the communication between client and server.

With the account information, we can try and nail down what the cause is and if there's anything we can do to fix the issue from our end.

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

Originally posted by Simon-says-what

Sorry to hear that you feel we're wasting players time.

You don't have to be sorry for my feelings, and noone needs a non-apology like this.

You ARE wasting players' time since you apparently will never get this issue under control.

The shooting range was a separate issue and not related to what we're seeing in this video.

No, the shooting range was just the first attempt at deflecting this issue. Unfortunately players didn't swallow the narrative and kept testing. Once it was proven that this does in fact happen a lot outside of the shooting range we got another non-committal "we'll investigate", followed by weeks of silence.

Only because players keep bringing this issue up you are still dealing with this, it was very obvious that internally you guys were hoping we would just forget about it.

These sort of issues can be caused by a myriad of potential reasons, including (but not limited to) the game servers themselves, the players connection or the communication between client and server.

This issue has existed since the Division 1 Beta. It's your engine, and your servers. Both are simply not up to speed for a shooter game but of course you can't admit to that.

So instead of optimizing or changing the engine and simultaneously upgrading your server infrastructure, you will keep beating around the bush on this one, pretending that those are all small scale incidents, related to the player's connection or account.

if there's anything we can do to fix the issue from our end.

Yeah, for the inevitable part 3 of this franchise just use an engine and servers that are fit for a shooter game.

No, the shooting range was just the first attempt at deflecting this issue. Unfortunately players didn't swallow the narrative and kept testing. Once it was proven that this does in fact happen a lot outside of the shooting range we got another non-committal "we'll investigate", followed by weeks of silence.

I'm just going to pick this up because it's the most glaring try to discredit the dev team. The issue in the shooting range was never this extreme as what we're currently seeing. There were some shots not registering.

This situation is way worse, the videos show complete LMG magazines not registering on multiple occasions. So no, it's not the same issue. I understand you're unhappy with the game and that the solution for you lies in the game's engine and server setup. But please don't try to push your agenda by highlighting two different issues and making them seem as the same thing.

Not only does it not help us making the game better but it also just adds confusion for other players experiencing issues like this. It's totally fine not to trust the team here or to be unhappy with the game but please don't spread false information. Thank you.

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

Originally posted by Simon-says-what

I'm just going to pick this up because it's the most glaring try to discredit the dev team. The issue in the shooting range was never this extreme as what we're currently seeing. There were some shots not registering.

And yet, when this issue comes back in more or less extreme forms for almost 4 years it's safe to assume that the root cause here might be similar.

After the lame shooting range excuse people posted all kinds of videos, a lot of them also with full clips not registering, mostly in the DZs, but some also in PVE.

What you are seeing in this clip absolutely isn't a new issue, this has always been around. And the reason why people even noticed this issue in the shooting range is because that's where they decided to test this issue further, after experiencing it during regular gameplay and getting no real acknowledgment from you guys.

And you then just conveniently pretended that this is just an issue in the shooting range, which simply was extremely dishonest and lazy.

I am not on an agenda, I'm just calling you out on excuses and issues that never get resolved.

but please don't spread false information. Thank you.

Kind of a funny spin when it was you folks who blatantly lied to your player base on several occasions.

After the lame shooting range excuse people posted all kinds of videos, a lot of them also with full clips not registering, mostly in the DZs, but some also in PVE.

Can you show me the videos you're referring to that showed entire clips not registering before TU5? It might be very helpful to identify an underlying cause, that you so vehemently claim exists. We made several changes when the shooting range was brought up and I can't recall seeing videos like we're seeing after TU5.

I am not on an agenda, I'm just calling you out on excuses and issues that never get resolved.

I think that describes an agenda pretty well.

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

Originally posted by Simon-says-what

Sure, how about this video? https://www.youtube.com/watch?v=EZA8R3dlVL8

Was also posted as a thread here if I remember correctly.

that you so vehemently claim exists

You gotta be kidding me. First you blame it on the shooting range, didn't fly. Then on the player connections, and even their accounts, which won't fly either. And now you are acting like this is some sort of conspiracy theory?

This issue is very real, and every Division veteran knows about it. Maybe play the game every once in a while to know what people are talking about. I think that would generally be good advice for the whole team, given how the game has turned out.

I think that describes an agenda pretty well.

If you think calling out lies and excuses is an "agenda" and not just something that any person with a somewhat intact moral compass should be doing, then let's just say you're working in the right industry.

  • First clip in the video, there are several damage numbers popping up. Clearly not an entire magazine not registering.
  • Second clip in the video, clearly damage numbers can be seen but the impact is not. Different again from what we're currently seeing, where the damage doesn't even register.

Then a bunch of PvP clips and single Sniper Shots not hitting.

Here are the current reports, just in case you haven't looked at them.

  • The video in this very thread. Full magazine into a NPC, no damage numbers show up at all.

https://www.reddit.com/r/thedivision/comments/cmvkj4/i_mean_come_on/

  • Full magazine again, no damage numbers.

If we want to find a common ground: In both situations no damage is dealt. But the video you linked shows us single shots or some shots not registering. This is not the same as what we're currently seeing where no damage is dealt.

Any other videos you want to share so I can have a look?

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

Originally posted by [deleted]

[deleted]

You're claiming these exist. I'm saying I haven't seen videos from before TU5 that showed entire clips of guns not registering on enemies, specifically not showing any damage numbers on enemies at all.

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

Originally posted by Simon-says-what

Let's turn this one around for a second: You are not a developer, I am not a developer.

How can you say with absolute confidence that some bullets registering has a different root cause as no bullets registering? Just because the magnitude of the symptom is different, how can you know that this isn't the same root cause? Because on a more general level the symptom is the same actually: Bullets not registering.

You know it's very confusing when you pretend to be interested in videos so you can investigate further, and you previously stated that you guys don't know yet what the issue might be so you have to look at it from several different angles (server, player connection, account, etc.), but at the same time you want to tell me with absolute certainty that this isn't the same issue just because the symptoms are more or less extreme?

Sorry but this doesn't add up from any angle.

Either you know what the issue is, then you can say "Nope, this is not it", or you don't know what the issue is, then you have to say "sure, we'll look into it".

But this is exactly what I mean when it comes to the dishonesty in communication in this industry. You love to hide behind your ignorance and pretend you have to investigate first when it's convenient and buys you some time, and on the exact same topic you suddenly flip flop on your stance and claim to know that evidence x,y, or z are unrelated and thus it must be something else.

Let's be real here: What you are doing here has nothing to do with investigating, this is just another attempt at deflecting.

So you don't have a video, right. Yes, I'm not a developer but I'm talking to the dev team every day. When they tell me that this issue is something new and we need more details to figure out what's happening then I'm asking the community.

Your assumption that we're doing this to keep people quiet and not asking more questions doesn't make sense to me and our approach doesn't make sense to you. I think that sums up the discussion.

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

Originally posted by Simon-says-what

See, and this is the perfect example of why communication with a corporate entity is such a fruitless endeavor in most cases.

You ask me to share a video, I comply. Then you pretend to be interested and transparent about an issue but all it took to completely halt the conversation was a single harmless question.

It isn't even a confidential piece of information, at least it doesn't have to be, but you can not even answer what the tick rate of your servers is. Let me guess, your server magicians have come up with some new approach to cut corners on the server costs?

This was a major complaint in TD1 and you promised to improve on that front for TD2.

Have you delivered on that promise? Well, hard to tell as you won't disclose that trivial information. You know pieces of information like that would help a lot to identify this issue or at least ruling out certain things in user tests. But of course giving out this information would also make Massive & Ubisoft somewhat accountable, so you rather just pretend this conversation never happened instead.

Very classy, Chris Gansler, very classy. This is the reason why a lot of people are so fed up with talking to community managers, or whatever the f**k you call the position these days. There just can't be transparency, there just can't be honesty, and every time you pretend there is you're just playing people for PR purposes.

If anything, YOU are on an agenda, quite literally as it's written down in your contract. I am just writing from the perspective of a frustrated player whereas you are doing your job with all the goals, limitations and restrictions that come with that.

I don't have to lie, be it deliberately or by omission. You however, that is literally part of your job as you just demonstrated.

Sorry for the late reply. I'm unable to spend all day on reddit and sometimes my time just runs out before I can reply to everything.

We haven't discussed the tick rate publicly and I'll need to check if we want to. As it hasn't happened yet, I'd say it's unlikely. We had a pretty good podcast about the online structure in The Division though, if you like to hear about that here.

We also explained how the infrastructure will look like in The Division 2 here.

In terms of your video, you provided me with something that didn't reflect the issue we're seeing right now in TU5 at all. I explained why and you ignored that. If you don't want to further discuss this because we're not offering you the level of transparency you want, totally fine.

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

Originally posted by usafwd

/u/ChrisGansler Great community involvement you've got there. You are the perfect example of how NOT to interact with your CUSTOMERS.
I didn't have too strong of an opinion of how Massive was handling things, but after reading your continued lame passive agressive comments towards a customer, I can firmly say that you are a failure at interacting with your games player base. Reading your responses is awful.

Thanks for the feedback.

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

Originally posted by [deleted]

[deleted]

I aksed for videos before TU5 from Simon-says-what because he claimed that it's the same issue. We are very well aware that the bullet registration right now is a big issue for some players. We will likely not need further videos as we're now looking into the specific player accounts and their connection to our servers and other data.

Sorry if that wasn't clear. We know there's an issue now but we think that what Simon-says-what is talking about is a different issue that appeared before TU5 and has since been improved (read: not completely fixed). But there was the notion that it is the same issue, which from the videos doesn't look to be the case.

Thanks for reaching out.