After the update, my stadium appearance changes every time (when I play at home). One time it's blue lines and pink goals or a different ball, then again white lines and purple goals. Even though I haven't added any colors to the lines and goal nets, so it's just white. The home crowd also wears the opponent's shirt. Please fix this; it is very annoying and distracts from the game and the enjoyment of playing.
Same here on PS5
Same. Just played a match and the goal posts were red. Other matches the ball is different, my fans wearing the away top at home matches and quick sub is on which I have turned off!
Here too. The away stadium settings appear when we play at home, and ours appear when we play away. Makes no sense at all. 🤦🏻🤦🏻🤦🏻
Community ManagerHey all, thanks for taking the time to post and share your feedback.
We have passed this on to the FC team to look into.
Would it be possible to grab us some screenshots or a video showing the issue as you are seeing it?
Is it with all teams or only select ones?
The more info that we have to share with the team the better.
Darko
Hi. In Ultimate Team, when we play at home, the opponent's stadium settings, such as the net, ball, and others, appear for us. When we play away, our own settings appear.
Community ManagerCan you grab us a screenshot or video of what you are seeing jonata_nonato?
Testing here and not seeing such an issue so the more info we have the better.
Darko
Here is a picture of it happaning to me. I’m the home team (In the red top) but look at the crowd. Blue nets and posts and yellow lines. All should be white. Same as the ball which has changed. It’s random aswell. Next match may be OK but the one after will be all random colours again.
Hi, any news? Today while playing it seemed to have gone back to normal, but then it bugged again 🤦🏻
"I am still experiencing the issue where the game forces me to use my opponent's ball and pitch line colors instead of my own settings. This makes the game unplayable in certain matches. Please fix this bug!"!!!!
Hello, is there an estimated time for a solution to this problem? We've had a few updates since the bug started, but none have fixed it.
