John403 wrote: »
@EA_Roger when is this supposed fix that you guys are working on for the DRE supposed to drop? This is absolutely ridiculous that I still can’t play EASHL.
NHL_ONL_Producer wrote: »
We certainly hoped that the dressing room errors were going to be reduced but after reviewing the data, unfortunately, there has been no change. In the latest patch we have added additional information that can be turned on via gameplay tuner set, so we have a change that will likely go out tomorrow that enables that extra info. It will be another day or two of analyzing that data to determine where in code the errors are occurring. When I have more info to share out with you, I'll be posting to this main thread.
The Full Session issue - We hope to have out soon, but not ETA at this very moment. Stress Testing has been completed but we are waiting on the results and the go ahead before we schedule the deploy to the retail servers.
It looks like you're new here. Sign in or register to get started.
They have no idea. They don't have a fix. Currently I'm sure they are in all out panic mode because the "fix" they released to us did NOTHING (they will say it cut back on errors a lot, it probably didn't.) So now they are all freaking out trying to come up with the next story they can tell us about how well the patch worked and how we are on the right path, and they are working on a permanent fix.
So before the it went like this:
First game (could be succesful or could be DRE) -> restart game -> Get in successfully -> restart game -> get in succesfully etc.
Sometimes it would just throw the error on the whole team and no one gets in.
We played last night and now it goes like this the whole time:
First game (same as before) -> restart game -> DRE -> restart game -> Get in successfully -> restart game -> DRE -> restart game -> Get in successfully -> restart game -> DRE -> restart game -> Get in successfully etc.
So now it takes twice as long to get back in to the game. Having to constantly restart this was already frustrating enough.
Edited to remove suggested swearing. - EA_Cian
My previous post was deleted and I was warned because I called out an EA employee instead of discussing the topic at hand.
I believe that I *was* discussing the topic at hand. You are doing a good job at managing the community, and I did not call you out on that. But the topic at hand is shifting towards the bug that has persisted since the beta to how it’s being handeled.
You (EA) have had ample of time to diagnose and solve this issue since the beta and post launch. I believe that topic is now equally concerning how you are organised to solve this issue and it is worth pointing out here to draw your attention to what is becoming a core issue on this topic.
I would be interested in what concrete measures are being taken to solve this and what your timeline and roadmap looks like.
Again, there’s no ill will towards you or any employee, only towards the issue at hand.