Thank you.
The first bug fix didn't work, which is why it didn't make it into 5.2. We now have one that is going into Episode 2 / TU6 that has fixed it in our tests.
Thank you.
The first bug fix didn't work, which is why it didn't make it into 5.2. We now have one that is going into Episode 2 / TU6 that has fixed it in our tests.
Read moreThanks for responding Chris because I do want continue this discussion with you. So what your telling is content wise for episode 2 cant be communicated because not ready? But you guys have been hyping it up going on 2 weeks now. Do you guys really need to have a developer in the room for them to repeat the same information that been posted on the subreddit and the official forum. 5 hours is stretching it, only way it would take that long if you guys keep repeating information that is already know which you guys currently do with the current run time of stog. People just want to know the content that you guys have been hyping up all the way up until now. No one expecting you guys to drop information of when survival or underground is coming to division 2 they want to know what coming in episode 2. Which then you guys get everyone expectations up only for it followed with disappointment. I am sorry I just don't see the challenges you guys are facing, indie studios smaller then you d...
indie studios smaller then you do not have this much trouble with communication
I think this perfectly sums up the situation and what causes frustration. We are not an indie studio so our communication goes through way more internal channels. That also means we sometimes are less flexible than we want to be and it can show.
Really how many teams do you guys need to announce (example)the 3 missions are coming in the next update?
Without presenting the details, more than you think. We have to make sure everybody who's going to use this information agrees on when it's used. We have to make sure we present the content in the best possible way and also consider it to be localized. It's not as simple as me going to the guy who developed (this is extremely simplified, please don't believe one guy makes a mission) the mission and ask him if it's ok to show it on State of the Game.
It boils down to us not ...
Read moreespecially when they can feel lackluster even if we try.
Sorry but how exactly are you "trying"? While your player base was eroding you guys just went on summer vacation for 6 weeks, then canceled the first SotG after the vacation was supposed to be over, and now you're not even sticking to the roadmap of announcments you've laid out yourself.
If that's your definition of trying, please stop.
"Do, or do not. There is no try"
Only Siths deal in absolutes. We try and we'll continue to try. I understand it's frustrating at times but we will do better.
Again, the return was cancelled to me being out sick. If I had a choice in it I wouldn't have been lying in my bed trying to stop the room from spinning but it's not always a possibility even with meds.
And we're working on a live game which means sometimes things shift around. It makes working on the communication more challenging and sometimes we just make mistakes. Doesn't mean we don't get frustrated by that or just brush it off.
be fixed finally?
I'll double check, I think it is in TU6. Thanks for sending it over again.
Read moreI'm just gonna leave this here: https://i.imgur.com/8SCqdLh.png
Hey, Chris, look, we get it, designing video games are hard, communicating with the fan base is hard, but when your own people provide information like this, and don't follow through, the player base doesn't care about how hard it is to communicate things. You say you're gonna talk about the future of the game on September 25th, that's what everyone expects. This is exactly what was communicated to us for several weeks now, and to come on stream and not talk about the future of the game, at such a pivotal time, unacceptable. And even Hamish could've said at the start of the stream that future content talk will be at a later dat...
I think there's some fair feedback here. We did talk about Episode 2 coming out mid October and that we'll talk about the narrative content and the new Specialization in the upcoming weeks. It did fall flat and we'll be more careful with timelines in the future, especially when they can feel lackluster even if we try.
In terms of the Twitch chat, I think it's difficult to read chat sometimes when you don't know the person. We had answered the question about new content a bunch of times and I didn't want to sound sarcastic when I told you to have a good day. I was under the assumption that you really just wanted to know if there was no new content presented and could move on. Basically we both didn't do a good job interpreting each others chats, sorry about that from my side.
Don't let it get to you. He doesn't represent the player base. Most of us are grown up adults and can wait. GG for your professionalism and patience. I'm looking forward to TU6.
I've been in the industry for a long time and I know that we're not doing everything right and it causes frustrations. I don't take any of that personal but I appreciate you're taking the time reaching out!
Cool Cool
:)
Thanks for answer. Really appreciate it.
I can totally accept and i agree with the fact that an entire and large update needs to be presented, tested and discussed. And i'm, somehow i'm disappointed at the moment, excited to look for more and have Episode 2 between my hands.
But, please, keep in mind that i'm (and i'm probably not the only one) worried about the future of The Division 2 and we need some news about what we can expect in the coming month. Not only about Episode 2 and Episode 3 but some small news with what we can expect in Year 2 will be appreciate as 2020 will certainly be a great year in Video Game industry.
Appreciate the feedback. We'll talk to the teams here and look what we can do better in the future.
Just make STOG longer. I dont see the issue with that isn't that you guys job to communicate with the community? Just label it as special STOG where talk about everything coming in title update 6, content, balances, and patches. Then you can have normal state of the games to go into more detail about certain topic of the patch.You guys can come up with excuses quickly of why you cant do something but never come up with the actual answer. Make me wonder do you guys see how bad the situation your game is in right now when it comes to player wise? Borderlands just drop and has content coming out next month, destiny is fin to drop shadow keep next month as well. Time to stop with all the secrets and living in a fantasy world where division fun for the whole entire family.
We're splitting up the content and started with the gameplay updates as these were ready to be communicated on and were also something many agents in the community have asked about. Just making it a 5 hour State of the Game doesn't solve all challenges in announcing a new update. In an ideal scenario everybody gets every piece of content they are looking for whenever they are looking for it.
It's not something we can deliver every time (maybe never?) and if our current communication is frustrating for some players we apologize. Again, we work with several teams and announcing any new content is a larger challenge than it might look like from the outside. That doesn't help with the frustration but I do want to mention it.
WAT? Barret's vest was awesome for a Tactician seeker/turret build.
Before the nerf, Barrett's was the bee's knees for sure.
Not easy ? Is this a joke ? You had an entier month to do so. And more, you mess with your player base by cancelling the first SOTG of the month and take another step back in your roadmap that you release in March. All of this, was just a waste of time.
As a Division fan, i'm really sick and tired of all of this crap.
I swear, TU6 better be good.
Agreed, the cancellation of the first State of the Game was not great and I can personally apologize for that. Me being out sick meant we couldn't do the show and run the ETF at the same time.
Communicating on new content doesn't only happen on State of the Game and it's an effort we need to align on with other teams. Sometimes we'll focus on new content, this time we focused on the game updates.
I understand that new content is really important and we will talk about Episode 2 content not only on State of the Game. That being said, the updates to the gameplay and the improvements coming in TU6 are also vast and we do want to present and discuss them with you.
With all due respect that's a bit of a mis-step, a lot of us are screaming for new content and you guys just don't seem to want to talk about it until just before it drops!
Announcing new content is something we're excited about and it's something we talk about on State of the Game. Episode 2 is a large update and many players wanted to see and talk about improvements to the current game, balance and how we plan to make the overall experience better.
We can't tackle everything in one show, so we decided to first address the updates to the gameplay in the first weeks after our break and we tried to show you this by providing a schedule beforehand. We will talk about content later on and we'll show off what's coming in terms of content with Episode 2.
It's definitely not easy to communicate on a large patch like this and we're sorry if we have some shows that don't offer something for everybody.
It'd be cool to get some gameplay footage of future content. Massive can really pull the players back in with a really good SOTG today.
We'll be talking about new content in the upcoming weeks and will have visuals as well.
"Should" be fixed when TU6 goes live in October, come on man, how about "will" be fixed. It's enough the community is QAing the game they paid for at the moment.
I don't have full visibility right now on the process so I don't want to say "will" when there's still a likelihood that we can't fix it. Communication like this is weird as I'm certain we will fix it by TU6 but I also don't know it will be.
I get your point though and we agree, this can't be in TU6 when it goes live.
Hey everyone,
Could you confirm me restarting the client fixed the issue?
Thank you!