I should start by stating that I don't every leave comments. I usually feel it's just not worth my time. I have made an exception this time however. After being out for nearly 6 months there should be no reason for continued dressing room errors at this frequency. I put the game down after the first month because it was impossible to get into an online game. I decided on a whim to retry tonight and after 2 wasted hours I got into 2 "ones" matches and a 6v6 game with uncountable dressing room. Errors in between. The EA Games seem to have had more and more issues over the years. It is at the point where Im about to get rid of this game, and until I have had it confirmed from other people that the games are fixed, i think I will be steering clear if the EA franchises, which is unfortunate, because I can't tell you how many hundreds to thousands of hours I've invested into these games over the years and across multiple platforms. Hopefully in the coming years things can get back on track.
Same here, PS4 update 6.50 broke the dressing rooms for European players tried to get a 6vs6 game 2 days in row for 4-5 hours, no joy. Tested with NAT1 with everyone involved
Dressing Room Error back with a vengeance. After spending the first 2 months of this game's existence messing about to get in a single game I am not dealing with it again. You've lost a customer EA. Bye-bye.
Yes, no club games since 6.50 Playstation update. Seems to affect specific ISP (DNA) in Finland. Sometimes it works if i am only one on dressing room with DNA and others have different ISP.
This is for 6vs6. I don't get DRE everytime, but almost always someone Will and it seems to be always people who have DNA as their ISP.
> @repetius said: > Yes, no club games since 6.50 Playstation update. Seems to affect specific ISP (DNA) in Finland.
Oh no, not again. I have been battling DNA in the past with similar problem.
In my earlier case the traffic did not work between two subnets in DNA's network. You could test it by removing the router and connecting the PC straight to the wall, and it was given a different IP and different subnet than to the router.
And it was specific to couple of subnets, so if you renew enough the router's address it eventually got a address from a another subnet, where everything worked. Another thing you can do is disconnect the router until the DHCP server lease time expires, and hope that next time it gets address from different subnet.
We collected massive amount of evidence for the ISP, but they did not believe it still.
It's not black and white like that. It's just high propability to get dressing room error, for me like 50/50. So in 6vs6 if many have DNA as ISP it's very likely that someone gets the error.
So Im get dressing room errors since the beta.
Over the course of this cycle I have heard many possible work arounds for this.
-Restart game after every game
-Go through chel after every game
-Restart Internet after every game
-Everybody needs to press ready before 20 seconds on the timer.
-Press triangle when match is found.
-Reinstall game
-Reinstall ps4 framework.
I've done all these but maybe the most effecient one is that I restart the game and shouldn't hang out in the dressing room long. Usually I wait until everybody is ready then I enter from chel to the dressing room and right away try to find a game. And everybody presses ready before 20 seconds on thr timer once they found a game. But then again, I'm still continously getting them. I guess 1-3 until a get into a game.
Was there any solutions that worked for you?
Maybe I didn't try something else. Let me know what worked fro you!
> @sawe_FI said: > Today we tested the ISP angle, and it is not from that, we managed to get 2 out of seven searches > without dressing room error.
How have you tested this? You mean that no one had DNA and still you got error 5/7 searches?
My club and many others have tested and noticed that DNA customers are the ones who get error. If only 1 DNA in game (both teams included) error only maybe 1/5. If 2 DNA customers / game our record is something like 0/20 searches since that latest PS4 system update.
> @ahonaattori said: > > @sawe_FI said: > > Today we tested the ISP angle, and it is not from that, we managed to get 2 out of seven searches > > without dressing room error. > > How have you tested this? You mean that no one had DNA and still you got error 5/7 searches? > > My club and many others have tested and noticed that DNA customers are the ones who get error. If only 1 DNA in game (both teams included) error only maybe 1/5. If 2 DNA customers / game our record is something like 0/20 searches since that latest PS4 system update. > >
The one succesful search proved that it is not from DNA, because we had 3 players using that ISP.
The earlier incident prevented all traffic between the two subnets.
> The one succesful search proved that it is not from DNA, because we had 3 players using that ISP. > > The earlier incident prevented all traffic between the two subnets.
Aah, ok... Yeah i also think that it is not impossible to get games going with more than 1 DNA...just almost impossible.
Did you have 6 players when you tried this? Friends played yesterday with 4 DNA user with almost no errors... but they had 2 empty spots in dressing room. It seems to help for some reason.
> @ahonaattori said: > > > The one succesful search proved that it is not from DNA, because we had 3 players using that ISP. > > > > The earlier incident prevented all traffic between the two subnets. > > Aah, ok... Yeah i also think that it is not impossible to get games going with more than 1 DNA...just almost impossible. > > Did you have 6 players when you tried this? Friends played yesterday with 4 DNA user with almost no errors... but they had 2 empty spots in dressing room. It seems to help for some reason.
We usually play with 5 players, sometimes with 4. What we have gathered, is that with 5 or 4 on our side, the game only works against two player teams, sometimes that is.
5vs5 or 4vs4 haven't worked since 6.50 update.
And when we tested the situation, by searching game with only two players, it worked most of the time.
One EA staff member suspected that player gear maybe the issue, and referred that in NBA they had similar situation caused by sweat headband on players. So there is one thing to test, revert all player modifications to default.
> @sawe_FI said: > > @ahonaattori said: > > > > > The one succesful search proved that it is not from DNA, because we had 3 players using that ISP. > > > > > > The earlier incident prevented all traffic between the two subnets. > > > > Aah, ok... Yeah i also think that it is not impossible to get games going with more than 1 DNA...just almost impossible. > > > > Did you have 6 players when you tried this? Friends played yesterday with 4 DNA user with almost no errors... but they had 2 empty spots in dressing room. It seems to help for some reason. > > > We usually play with 5 players, sometimes with 4. What we have gathered, is that with 5 or 4 on our side, the game only works against two player teams, sometimes that is. > > 5vs5 or 4vs4 haven't worked since 6.50 update. > > And when we tested the situation, by searching game with only two players, it worked most of the time. > > One EA staff member suspected that player gear maybe the issue, and referred that in NBA they had similar situation caused by sweat headband on players. So there is one thing to test, revert all player modifications to default.
Yeah, i have heard that NBA thing before.,, But this problem is not about gears... it effects about 100% of dna users.. And that is shown clearly when playing full 6vs6 games.
> @ahonaattori said: > > Yeah, i have heard that NBA thing before.,, But this problem is not about gears... it effects about 100% of dna users.. And that is shown clearly when playing full 6vs6 games.
Well start gathering information then, last time DNA's customer support was hell.
For starters, gather everybodys public IP,Mask and Gateway. After that start testing ping responses across members and traceroutes, all while logging everything. And preferrably conclude possible findings with real servers and traffic so not just ICMP traffic gets used.
> @sawe_FI said: > > @ahonaattori said: > > > > Yeah, i have heard that NBA thing before.,, But this problem is not about gears... it effects about 100% of dna users.. And that is shown clearly when playing full 6vs6 games. > > Well start gathering information then, last time DNA's customer support was hell. > > For starters, gather everybodys public IP,Mask and Gateway. After that start testing ping responses across members and traceroutes, all while logging everything. And preferrably conclude possible findings with real servers and traffic so not just ICMP traffic gets used. > > Happy hunting. >
Hahhah, its not my job and i do not have will or ability to do it. And i don`t think you could find what causes the problem that way, by non PS4 related trafic testing. Problem is on EA side, they have build that dressing room and game launch somehow wrong...and they should fix it!!!
Replies
Sincerely,
No longer a fan.
Error occures almost everytime when dressing room is full. Meaning 6 player in 6s and 4 player in 3s.
Are you doing something to fix this?
This is for 6vs6. I don't get DRE everytime, but almost always someone Will and it seems to be always people who have DNA as their ISP.
> Yes, no club games since 6.50 Playstation update. Seems to affect specific ISP (DNA) in Finland.
Oh no, not again. I have been battling DNA in the past with similar problem.
In my earlier case the traffic did not work between two subnets in DNA's network. You could test it by removing the router and connecting the PC straight to the wall, and it was given a different IP and different subnet than to the router.
And it was specific to couple of subnets, so if you renew enough the router's address it eventually got a address from a another subnet, where everything worked. Another thing you can do is disconnect the router until the DHCP server lease time expires, and hope that next time it gets address from different subnet.
We collected massive amount of evidence for the ISP, but they did not believe it still.
Over the course of this cycle I have heard many possible work arounds for this.
-Restart game after every game
-Go through chel after every game
-Restart Internet after every game
-Everybody needs to press ready before 20 seconds on the timer.
-Press triangle when match is found.
-Reinstall game
-Reinstall ps4 framework.
I've done all these but maybe the most effecient one is that I restart the game and shouldn't hang out in the dressing room long. Usually I wait until everybody is ready then I enter from chel to the dressing room and right away try to find a game. And everybody presses ready before 20 seconds on thr timer once they found a game. But then again, I'm still continously getting them. I guess 1-3 until a get into a game.
Was there any solutions that worked for you?
Maybe I didn't try something else. Let me know what worked fro you!
> Today we tested the ISP angle, and it is not from that, we managed to get 2 out of seven searches
> without dressing room error.
How have you tested this? You mean that no one had DNA and still you got error 5/7 searches?
My club and many others have tested and noticed that DNA customers are the ones who get error. If only 1 DNA in game (both teams included) error only maybe 1/5. If 2 DNA customers / game our record is something like 0/20 searches since that latest PS4 system update.
> > @sawe_FI said:
> > Today we tested the ISP angle, and it is not from that, we managed to get 2 out of seven searches
> > without dressing room error.
>
> How have you tested this? You mean that no one had DNA and still you got error 5/7 searches?
>
> My club and many others have tested and noticed that DNA customers are the ones who get error. If only 1 DNA in game (both teams included) error only maybe 1/5. If 2 DNA customers / game our record is something like 0/20 searches since that latest PS4 system update.
>
>
The one succesful search proved that it is not from DNA, because we had 3 players using that ISP.
The earlier incident prevented all traffic between the two subnets.
>
> The earlier incident prevented all traffic between the two subnets.
Aah, ok... Yeah i also think that it is not impossible to get games going with more than 1 DNA...just almost impossible.
Did you have 6 players when you tried this? Friends played yesterday with 4 DNA user with almost no errors... but they had 2 empty spots in dressing room. It seems to help for some reason.
>
> > The one succesful search proved that it is not from DNA, because we had 3 players using that ISP.
> >
> > The earlier incident prevented all traffic between the two subnets.
>
> Aah, ok... Yeah i also think that it is not impossible to get games going with more than 1 DNA...just almost impossible.
>
> Did you have 6 players when you tried this? Friends played yesterday with 4 DNA user with almost no errors... but they had 2 empty spots in dressing room. It seems to help for some reason.
We usually play with 5 players, sometimes with 4. What we have gathered, is that with 5 or 4 on our side, the game only works against two player teams, sometimes that is.
5vs5 or 4vs4 haven't worked since 6.50 update.
And when we tested the situation, by searching game with only two players, it worked most of the time.
One EA staff member suspected that player gear maybe the issue, and referred that in NBA they had similar situation caused by sweat headband on players. So there is one thing to test, revert all player modifications to default.
> > @ahonaattori said:
> >
> > > The one succesful search proved that it is not from DNA, because we had 3 players using that ISP.
> > >
> > > The earlier incident prevented all traffic between the two subnets.
> >
> > Aah, ok... Yeah i also think that it is not impossible to get games going with more than 1 DNA...just almost impossible.
> >
> > Did you have 6 players when you tried this? Friends played yesterday with 4 DNA user with almost no errors... but they had 2 empty spots in dressing room. It seems to help for some reason.
>
>
> We usually play with 5 players, sometimes with 4. What we have gathered, is that with 5 or 4 on our side, the game only works against two player teams, sometimes that is.
>
> 5vs5 or 4vs4 haven't worked since 6.50 update.
>
> And when we tested the situation, by searching game with only two players, it worked most of the time.
>
> One EA staff member suspected that player gear maybe the issue, and referred that in NBA they had similar situation caused by sweat headband on players. So there is one thing to test, revert all player modifications to default.
Yeah, i have heard that NBA thing before.,, But this problem is not about gears... it effects about 100% of dna users.. And that is shown clearly when playing full 6vs6 games.
>
> Yeah, i have heard that NBA thing before.,, But this problem is not about gears... it effects about 100% of dna users.. And that is shown clearly when playing full 6vs6 games.
Well start gathering information then, last time DNA's customer support was hell.
For starters, gather everybodys public IP,Mask and Gateway. After that start testing ping responses across members and traceroutes, all while logging everything. And preferrably conclude possible findings with real servers and traffic so not just ICMP traffic gets used.
Happy hunting.
> > @ahonaattori said:
> >
> > Yeah, i have heard that NBA thing before.,, But this problem is not about gears... it effects about 100% of dna users.. And that is shown clearly when playing full 6vs6 games.
>
> Well start gathering information then, last time DNA's customer support was hell.
>
> For starters, gather everybodys public IP,Mask and Gateway. After that start testing ping responses across members and traceroutes, all while logging everything. And preferrably conclude possible findings with real servers and traffic so not just ICMP traffic gets used.
>
> Happy hunting.
>
Hahhah, its not my job and i do not have will or ability to do it. And i don`t think you could find what causes the problem that way, by non PS4 related trafic testing. Problem is on EA side, they have build that dressing room and game launch somehow wrong...and they should fix it!!!