Prior to TU20, the goal replay scene occasionally displayed the opposite direction (180 degrees) and was not a replay scene.
The same issue was confirmed in TU20.
However, in the scene I observed this time, the decisive goal moment was not shown, but the camera was facing an unrelated direction at about 45 degrees, so the timing of the shot could not be confirmed.
If the bug cannot be fixed, why not stop the replay scene?
Ideas
18 Comments
EA_Darko
Was the attached video helpful?
I want it fixed quickly.EA_Darko
I already provided the reproduction video you requested. When will this bug finally be fixed?
You wouldn't say it can't be fixed even with the reproduction video, would you?
EA_DarkoCommunity Manager
For bug reports like this perfectioncat we cannot provide any updates.
Darko
EA_Darko
Does that mean this isn't a bug?- EA_Darko
We don't know if it is or it is not perfectioncat.
We pass it on to the team but as there are so few reports of this and that I am unable to recreate it then it may not be a bug and instead some odd quirk only a couple of people are seeing
Darko
EA_Darko
I don't think the fact that only some people experience it is grounds for saying it's not a bug.
Whether something is a bug depends on whether the phenomenon differs from the creator's intended behavior.
I understand that scene as a design choice to focus attention on the decisive moment of the goal.
However, in the sense that it fails to reproduce that decisive moment, I recognize it as a bug.
All actions freeze at the instant of the shot's impact.
What are the conditions that cause that scene to occur?
If we understand that, I believe it would be possible to increase the reproducibility rate.EA_Darko
I actually suspect it's simply a bug in the calculation algorithm.
I've encountered that phenomenon several times, and most often the camera rotates in the exact opposite direction it should.
This usually happens because it doesn't remember the state of all events.
If it's a simple algorithm bug, wouldn't you be able to get results by creating some basic algorithm verification code and tracing it, without actually playing the game?
I've spent dozens of hours capturing that footage.
I'm reporting only the specific sections where the phenomenon occurs.
I don't want you to dismiss it as a bug just because only a minority of users experience it.
It might carry over into the next product.EA_Darko
I have no basis for this, but could the POV function have been active during the goal replay scene?