FC 27 Screen Freeze: A UX-Informed Bug Report
The opponent can take the ball during the freeze, so it reads as a difficulty spike rather than a bug.
Context
I'm a paying customer (I recently bought FC 26) who trial-tested FC 27. I recorded two sessions and logged every freeze I could. This write-up organizes those notes into a report a development team could act on, and adds the UX cost for the player.
Summary
The screen freezes briefly during live play, usually as possession changes or a scoring chance develops. During the freeze the opposing team can take control of the ball, and the on-screen player triangles lag, stick on the previous player, or land on the wrong one. In Video 2 a freeze also hit an offside stoppage, leaving a player and manager discussion stuck in the background. It returns whenever I replay with the exact same team.
Steps to reproduce
- On PS5, start a Kick Off game (Classic Match, Semi-pro) as Real Madrid vs. Premier League All Stars.
- Play normally, for example dribbling side to side for several seconds.
- Approach the goal to shoot, or win or lose the ball near either goal area.
- The screen freezes, and the opponent may take the ball during it.
- Replay with the exact same team. The freeze happens again.
Expected vs. actual
Expected: gameplay, input, and stoppage cutscenes stay responsive through possession changes, shots, tackles, and offside calls, including on replays.
Actual: the screen freezes, indicators lag or misplace, and a stoppage cutscene rendered incorrectly. It recurs on every replay with the same team.
Why it matters to the player
- Lost agency at key moments. Freezes land on shots, interceptions, and tackles, exactly when control matters most.
- Unfair-feeling losses. The opponent can take the ball during the freeze, so it reads as a difficulty spike rather than a bug.
- Unclear control. The red indicator flickered or appeared on the wrong player (for example Mbappé, in under a second), which was confusing and unnerving.
- Broken-looking stoppages. The offside cutscene froze mid-scene.
- No workaround. Replaying the same team doesn't help.
- Retention risk. I went back to FC 26 because of it, then hit the same freeze there (see Cross-version check below).
Evidence log
Both videos show the in-game match clock, which is the time used in the tables. Video time is given in the captions.
Video 1
Video 2
| Time | What happened | Trigger |
|---|---|---|
| 51:24 | I recovered the ball at the edge of my goal area; an opponent took control during the freeze. My most common pain point. | Possession change, near own goal |
| 53:05 | Opponent passed to a teammate on his right. | Opponent pass |
| ~54:45 | Freeze during a stoppage cutscene (context not yet recorded). | Stoppage |
| 56:54 | I was about to retake possession. | Possession contest |
| ~59:10 | Vinícius Jr. missed a goal that was ruled offside; the screen froze with a player and manager discussion in the background. | Offside stoppage; UI rendering |
| 61:31 | My forward pass was met by an intercepting opponent. At ~62:11 my red triangle flickered as another midfielder neared the ball. | Interception; visual glitch |
Video 2 shows six freezes in 2:35, roughly one every 25 seconds.
Logged after Video 2 ends
These were logged later in the same match, after the recording stops at 62:27, so the videos don't show them.
| Time | What happened | Trigger |
|---|---|---|
| 64:02 | Opposing midfielder regained the ball, then froze as my attacker tried to win it back. Both triangles stuck on the previous players; the red one took under a second to appear on Mbappé. | Possession contest; indicator lag |
| 66:38 | My attacker passed forward toward the right, then got stuck briefly. | Attacking play, right |
| 68:57 | My player was about to get a yellow card. | Disciplinary event |
| 69:58 | Opponent about to take a throw-in. | Dead ball |
| 74:48 | Opponent won the ball and was about to pass sideways. | Opponent pass |
| 77:11 | Opponent intercepted at the edge of my goal area. | Possession change, near own goal |
| 79:06 | My player passed and was about to shoot. | Goal attempt |
Other observations
- After I intercepted from the left just past the center-circle line and kicked toward Valverde, Yaya Touré intercepted and the screen froze.
- It happens each time I'm about to score after dribbling left and right for a few seconds.
- It happens near the goalkeeper or goalpost, especially from the right.
- It happens when my defender wins the ball near my own goal.
- It also happened as the opponent dragged the ball toward my goal and shot from distance.
Observed pattern (hypotheses, not confirmed)
- State changes. Freezes cluster around possession changes, interceptions, shot or pass initiation near goal, and stoppages (cards, throw-ins, offside). Control handoff, indicator updates, and event or cutscene triggers may be worth checking.
- Stoppage rendering. The stalled offside scene suggests cutscene rendering may play a part, not only live-play input.
- Replay dependence. Recurrence with the same team may point to team or squad data, or state carried over from the previous match. The FC 26 freeze happened against a different opponent (CA Osasuna), which makes team data a less likely cause.
- Shared across versions. The same freeze also happens in FC 26. Either the cause sits in code the two games share, or it's my console rather than the game (see Console condition below).
Cross-version check: FC 26
On 10/6/2026 I played FC 26 (full game) on the same PS5 against CA Osasuna, a different opponent from the FC 27 match, and the same freeze happened. FC 26 isn't a clean fallback. I'm filing a separate FC 26 report so each version's team gets its own ticket.
Console condition
Both games ran on the same console: an original-model PS5 lying horizontally. Dust and lint have built up along the edges of the white side panels and around the vents. Two games freezing the same way on one console makes a hardware cause, such as overheating, worth ruling out before blaming the game. I haven't confirmed this.
To rule it out: power off and unplug the console, clean the dust from the panels and vents, leave clear space around it for airflow, then replay the same match and compare. A different demanding game on the same console, or FC on a second PS5, would also separate a console problem from a game problem.
Secondary issue: opponent mirroring
After restarting a match with a team, the opposing side appeared to mirror and mimic my team's movements (Video 2). This should be filed separately, since it may or may not share a cause with the freeze.
My intuition, not a finding. Watching it, my gut feeling is that the opponents behave like bots mirroring my moves, driven by some probabilistic AI layer underneath the game. This is an impression from play, not a statement of fact. I haven't verified how FC 27's opponent AI works, and I can't establish the cause from the recordings. Identical behavior after every restart could just as well point to reused state or a fixed random seed.
To test it: restart the same match several times and log whether the opponent's opening movements are identical, repeat with a different team, and compare a menu restart with a pause-menu restart.
Open questions
- Game build number, PS5 model number, and system software version are still missing.
- Do the freezes stop after cleaning the console, and do other games freeze on it?
- What was happening during the three Video 1 freezes and the ~54:45 stoppage freeze in Video 2.
- Does it happen on first play, or only on replays? (The original report title mentioned restarting.)
- Does it happen with other teams in FC 27? (In FC 26 it also happened against CA Osasuna.)
- What kind of trial is this, and does it differ from the full release?
- Does the whole game freeze or only player and input state? How long does each freeze last, and how does it recover?
- Freezes seemed absent when the opponent neared scoring, yet one occurred during an opponent's long-range shot. Which is accurate?
- Does the opposing team also freeze? (See 64:02.)
- FC 26 has it too. Do its freezes follow the same triggers (possession changes, shots, stoppages), and do they happen in the same mode and with the same teams?
Reported by an end user and paying customer on PS5. Findings reflect two recordings from 9/28/2026 and an FC 26 check on 10/6/2026, and are not confirmed by EA.
Notes like this: system-thinking exercises and the UX fails I QA-test in the wild land roughly every two months. Subscribe to the newsletter ↓