Any progress on figuring out why you keep deploying builds with long load times? This is at least the third one in a very short time.
We have an understanding of what can cause it but for example the PTS loading times and the loading times that happened when the game went live had two different causes.
We'll continue to investigate. Thanks for your patience.
But if it is for console, it can wait another month or two, right?
We deploy all of our patches at the same time, doesn't make sense for us to not include fixes for a platform. But it can happen. We didn't wait for PC fixes and the past and sometimes we'll not be able to implement all console changes we want.
Doesn't mean that one platform is worth less to us than others. I understand that there's frustration on the topic of PTS as well and if there was an easy way for us to replicate this platform for consoles and have a lot of participants, we would.
Any chance you can sneak in a fix for the bullet/damage delay on consoles? I know people are really passionate about wanting that fixed so they can come back and play the game again.
We've made improvements yesterday. If it's still happening in the extremes where no bullets or a majority do not register, please feel free to send us some videos of these!
Thanks!
Now, I'm no game developer and can't speak for all the intricacies in detail but I know that just because you create some part of software it doesn't mean that you can predict at all times how this software will behave when you change things around. And change is necessary.
Noone has implied that. But if you are making a game with several teams world wide, and for more than 3 years you can't get certain issues under control, I'd say maybe you are biting off more than you can chew.
But of course that perspective is not very Ubisoft and probably not even a consideration at Massive. Everything always needs to be bigger and bigger, even when that means that the engine slowly but surely falls apart like the Springfield Monorail.
Yes, we are the people that produce it and in the end we have to fix it. It doesn't mean that it's easy or that we put faulty things into the game on purpose.
Again, noone has said or implied that, so can we please stop these straw man arguments?
It essentially boils down to the same message as above, you've created a monster that you just can't control anymore. But instead of letting this be a lesson to you for the next game, I would already bet some money on The Division 3 having the exact same issues again.
The explanation on why some things require more time, like with the Reviver Hive, is meant to illustrate the process and that detailed feedback from players is much appreciated.
Let's be honest, it's PR. Him, you, your community managers, you all communicate with us (or not) because it's your job, and in a corporation like Ubisoft noone goes around and decides "Hey, I feel extra transparent today, and want the players to know a thing or two!" Communication is a part of your marketing strategy, and so was this piece on the reviver hive. By the way we are not only talking about the reviver hive, the support station has had the exact same issue since the launch of the first game.
But let me guess, that's a totally different issue that just looks identical to the uninformed player? Chris, we are talking about almost 3.5 years at this point, when can players of your game expect basic functions like a skill to work reliably? Any ETA on that? Or save it as a selling point for TD3?
In terms of the hit registration issue: We made some improvements with today's maintenance, let us know if you're seeing any more of these extreme circumstances where none of your bullets are registering. We saw that in most videos players also had a poor connection to the host, so if you are seeing that message and the bullet behavior let us know!
I don't play the game anymore, at least not until it's in a fully functional state with all of its flawed systems repaired (i.e. never). I was sticking with you guys for more than 2 years on the first game, offering more than 2k forum posts of feedback and suggestions. I just can't do this shit anymore because it's basically a wasted effort if nothing ever really improves, or if it does, just comes back as yet another regression with the next update.
I doubt that this issue will ever be really fixed or addressed, especially not when you are lowkey blaming it on the player connection.
We can have theoretical discussions around this topic forever. If you're currently not playing that's totally fair. I can't talk about anything 3.5 years ago because I wasn't here and I'm not arguing for people back then, as I don't know what happened.
If you think that the transparent approach to our communication is purely marketing I cannot change your opinion on that, so I won't try.
I understand that a broken game or broken parts of a game can be very frustrating and that disappointment definitely is justified. I'm not trying to claim that we're always able to deliver everything perfectly. But it's also unfair to state
Chris, we are talking about almost 3.5 years at this point, when can players of your game expect basic functions like a skill to work reliably?
when a lot of these systems work and when they don't work it's often times in rare occasions (after we made fixes). We're always going to try to improve and if that's not enough for anybody, that's fine. Take a break...
Read moreYeah, this is weird since some Massive employee commented on reddit, that they didn't have a fix for long loading times yet...?
We actually snuck that one in after the maintenance. It wasn't ready for the main patch and the original plan was to wait for the next patch opportunity. But people were really passionate about trying to improve the situation as fast as possible.
Unfortunately this has been several different issues which made these longer loading times appear.
That may very well be but these issues are not caused by a higher power like a natural disaster that's outside anyone's control.
This is your engine, your game, your code. All of these issues are inherently caused by noone but you guys, regardless of what the root cause eventually turns out to be.
The other day I was reading this heartfelt story about the reviver hive in your forums, which is a bug that's just about as embarrassing as the loading times bug, and just another issue you guys apparently can't get under control since the first game.
The whole thing was written like Ahab fighting Moby Dick but not once did you mention that this white whale was created by you folks.
If you can't get your engine or code under control, then maybe work on smaller scale projects that can be dealt with in a single team. At this point you guys don't even seem to know anymore what was fixed and what wasn't.
Oh, and while we're at it: What's the current status on the missing bullets / hit registration issue? You guys have gone a little silent on that one.
Cheers
If we're looking at software in two states "working" and "not working" it's pretty easy to say "It's not working so let's change it to working". While that's the ideal outcome it's not often that easy. Now, I'm no game developer and can't speak for all the intricacies in detail but I know that just because you create some part of software it doesn't mean that you can predict at all times how this software will behave when you change things around. And change is necessary.
We're not putting the blame on the software though, Yes, we are the people that produce it and in the end we have to fix it. It doesn't mean that it's easy or that we put faulty things into the game on purpose. The explanation on why some things require more time, like with the Reviver Hive, is meant to illustrate the process and that detailed feedback from players is much appreciated.
In terms of the hit registration issue: We made some improvements with today's maintenance, let us know if you're seeing any more ...
Read moreWill this be a permanent fix or should players expect this to come back with every patch now?
Bringing it back once is an honest mistake, twice is an embarrassment.
Hey. We know that it looks like it's the same bug causing the same issue. Unfortunately this has been several different issues which made these longer loading times appear. So while we have fixed the occurrences, we're looking into ways to ensure this does not happen again.
u/ChrisGansler Any update on leaderboards raid completions? since its still not fixed. So completed raid, no leaderboards, log off/on, completed raid again, still no leaderboard completions. I'm doing something wrong? i hope this is one of top priority to be fixed and if needs to deploy hotfix with 1hrs notice for server shutdown. We just would like to have an update please.
Yes. It seems like the fix didn't make it into the patch. We're inquiring what happened. Sorry for the confusion.
In the meantime an official statement about the workaround could help. Alot of us have figured out if you fast travel from the raid back to the BoO, and then fast travel back the keys will be there after reloading in.......its not optimal if you're trying for speed runs, but you can at least get the keys if it glitches out with a simple bit of fast travel trickery.
Hey. We'll add that to the known-issues list, thank you!
Fix. It.
Yes.
Still no startup load time fix? Do we really have to wait weeks for a PC fix because of consoles?
We unfortunately haven't been able to get the fix for this ready. It's a high priority for the team, we understand how frustrating it is. As said before, we had a fix for the long loads on PTS but we encountered a new bug when TU5 was applied to the live servers.
Of course there isn't any fix for it. The bug isn't detrimental to Massive.
If raid bosses dropped 2 keys instead of 1, you can bet your lunch that it will be hot fixed the next day.
We don't have a fix for this ready. We do want to fix the bug though, there really is no reason for us to leave the raid like that.
The Dark Zone Proficiency Caches have a smaller chance to grant an Event Apparel Cache Key. It also is a random chance, so if you're unlucky you'll go some time without a key.
Without seeing the Reviver Hive it's difficult to tell. As someone else suggested, it might've been destroyed by a NPC.
Any chance you could ask your apparel team to separate the outfits into multiple pieces? That would be awesome.
That's probably not going to happen. Outfits are put together as one item, which allows more freedom when designing them. Making them separate would probably decrease the ability to make them look as cool as they are now.
Is the gear something that you may have already farmed? Or is it something special?
It doesn't check on duplicates, no. It's a gear piece per cache that should be around or above your Gear Score.
Funnily enough it's also some other shoes. Let's be honest, what's more tactical than invisibility? :P
I've let our apparel team know that something's borked here. Thanks for the screenshot!
Its been 2 days and we havent been given any update. I have a project that says it unlocks the bench but ive been at WT5 for months now and was told that it would auto unlock. I dont no want to have to do a bunch of work for something that was said to be automatic.
The upgrade being available was meant to be automatic. We did not want to imply that you can automatically get 500 gear without doing anything.
We mentioned this as we talked about the changes since we explained that you will need to deconstruct 490 gear, so that fresh WT5 players wouldn't just be able to craft 500 when arriving there.
We're currently still looking to fix this issue and I don't have an update for you as of now. Some players have reported that re-playing Tidal Basin unlocked the upgrade for them.
Once we have a bug fix we'll let everybody know.
Read moreSo, what qualifies as "Heroic Bosses" now if Missions and CP4s are excluded? Only Bounties?
Missions are the source for exotics. Sorry if I worded that in a way that wasn't clear.
Any news yet? Sorry to bug you about this so much but it's a huge change.
I can say it was an intended change. I haven't received an update on the philosophy behind it.