Yes
No
This doesn't seem like an unreasonable request. It's already progressed far beyond reasonable for players to continue to play under these conditions. This is not an acceptable situation to continue with no real solution or response from Ubi/Massive. Apologies for inconvenience are not enough. It's time for compensation.
It is absolutely unbelievable that a bug of this severity is nowhere to be found in press coverage of this game. There are plenty of articles that talk about what is coming next, etc. but not one word about this. Which is why I really don't take gaming journalists very seriously anyways.
What I can't quite get my head around, is how it happens to begin with. Disclaimer, I have been a professional developer but not in the gaming industry. How does a studio take a game from being solid, and turn it into this? It is an absolute release management failure. I have 3 players and 3 rigs in the house, and every single one of them will exhibit this issue. Maybe not today, but if not today then tomorrow.
And each of these rigs is under my own personal management, and another disclaimer.... I've managed a few PC's in my day. Actually... I've managed 26,000 of them for one place I worked. So I know a little bit about change and configuration management. I cannot be convinced that the issue I can see across my rigs is not a widespread issue, or that I am in the minority. The posts in this forum certainly indicate it is a widespread issue.
So how it wasn't caught during testing is beyond me. That it did get through to production tells me there is much to be unscrewed at Massive. I am guessing the snowdrop engine doesn't provide a rich set of features for testing as say, Unreal Engine. Or probably any of the other 7 (last I counted) in-house game engines that Ubisoft pays people to develop and support. My educated guess is that the game engine simply doesn't facilitate producing games that are end-to-end testable. That is problem #1.
Problem #2 is, they do not have enough human testers which would be required given the game engine (I'm speculating) doesn't foster automated testing.
Problem #3 is, they simply don't hire people that have decades of experience with IT service management. Anyone that has that background is going to be a little bit older than the age range they will hire.
"Boss, if you want me to rebuild the unit, stop sending me $%^& kids!"
Ok, I might have changed a word in that quote to make a point.
LucasFilms should be very, very afraid right now. Because in my view, this Star Wars game runs a very high risk of being next years Cyberpunk 2077.
Rest assured that the team is looking at this on a daily basis to try and determine the cause and find a solution.
Please check in on our support thread for any updates and steps on how you can aid us in our investigation.
We acknowledged his issue in our messaging in mid February where we spoke about there being upcoming content to The Division 2; and we hoped to fix this issue with our March 9th maintenance but found that our players continued to experience crashing to desktop post maintenance.
We appreciate your patience in the meantime and please forward us any files, clips or steps that might prove useful to our investigation.![]()
It’s not just the PC players that are crashing!
PS4 and now the PS5 are crashing more than ever now, you can’t even play the game 10 mins and you get a crash!
I played yesterday on PS5 and crashed 5 times in the first hour alone!
Looks like your competing against anthem cyberpunk!
Its your ubisoft connect which got updated and what is causing this latest issue. Ive never had any problems sans some dx12 waaaay back but after todays "patch" its 5 mins and BOOM game crashes. Have tried everything but clean win10 install and not gonna do that for sure.Originally Posted by Ubi-Lucipus Go to original post
What are you talking about on a daily basis?
IT JUST HAPPENED THIS AFTERNOON!
Whatever they just did to Connect this last update is what's screwing up TD2! There is no since February for most of the people posting about crashing today. IT'S A BRAND NEW FREAKING BUG!
Holy crap they have no clue...