Dr Kahn Task Force Crashes
By
mereman,
Posted on: 2012-03-26 16:27 in ALL ACCESS Gameplay Technical Issues Bugs
i think someone on victory ran one of those a few nights ago and i was hearing reports of the same problem in global channel (wasnt actually on the tf, but i figured i would chime in since this is relevant problem)
Quote:
Getting near -any- troop portal in Khan will crash everyone on the map.
|
Originally Posted by Victorious
Was running the Blue Side Reichsman Task Force, full team of 8, and the entire team has now crashed 3 times in the first two missions. If it was just 1 or 2 random players I could write it off as coincidence but, all 8 of us seems like something wrong with that Task Force.
|
Triumph: White Succubus: 50 Ill/Emp/PF Snow Globe: 50 Ice/FF/Ice Strobe: 50 PB Shi Otomi: 50 Ninja/Ninjistu/GW Stalker My other characters
Also, maybe hold off on summoning the leprechaun pet if any of you have it. If you do, at least summon him after the 2nd or so spawn of enemies go down.
That leprechaun is causing a crash after it is summoned first thing entering a mission, and it is not limited to the leprechaun owner.
Edit:
Actually, the owner didn't crash.
It was also fine after reentering the mission witht he leprechaun still out. You just have to deal with the initial crash.
On Defiant Sunday night we also gave up on a Kahn after 4 full team DCs in the first 2 missions. It was completely unplayable.
Also a team running a Barracuda sf hit a similar problem.
Happy to be on Defiant.
Global name @mereman
Member of P.E.R.C. Representing Defiant
Alts http://cit.cohtitan.com/profile/4488
CoH faces http://faces.cohtitan.com/profile/mereman
it happened twice to us , 8 man team and racked up at least 15 crashes in first 2 missions between us, it was reported and the response was the normal go check ur pc even tho it was clearly stated that it was NOT 8 pc's fault and allso mentioned at 3 of the 8 lived in the uk, austrailia and the us....
re - did it again the day after with another full team, got the same crashes once a portal was touched , updated the ticket to explain it was when a portal was touched and again all 8 had crashed during the first 2 missions...same response ...go check ur pc.....
nothing more to be said....
babe pink 50 scrapper
Quote:
1) Support will always try to do 2 things:|
Originally Posted by nightbabe
it was reported and the response was the normal go check ur pc even tho it was clearly stated that it was NOT 8 pc's fault and allso mentioned at 3 of the 8 lived in the uk, austrailia and the us....
|
A) Assume the specific reporter is the only person having the issue and that their end is at fault to remove that variable and because it is likely simplest to deal with.
B) Blame the user to shift blame away from the company and probable customer discontent while saving the company work if the customer finds "a work-around to the known issue".
If you keep the customer thinking it is their problem then it is much less work for the company running the game.
2) I don't think support has that much knowledge of how the game works and why problems could arise. They also don't have much communication with those who can and will have to fix the issues.
(Edit: Many of them likely don't even play the game to see and learn the issues that we as players do. They would have a better idea of the cause of a problem if they did play the game and experience it.)
So, you get the standard "blame it on the user" response until they just hit the limit of that line of thinking and say "this must be a bug, we will pass it along to the next person...", and the issue either stays in varying degrees of severity or eventually gets solved(and often comes back if they change something with that system again).
Its enough to make somebody swear off of ever discussing reports, just automatically filing them.
Was running the Blue Side Reichsman Task Force, full team of 8, and the entire team has now crashed 3 times in the first two missions. If it was just 1 or 2 random players I could write it off as coincidence but, all 8 of us seems like something wrong with that Task Force.