PC - Gameplay Slow Motion During Matches (High FPS, Menus Normal)
Hello,
I would like to report a serious gameplay issue on PC that appears to be affecting multiple users.
Problem description:
The game runs in slow motion ONLY during matches.
Menus, navigation, Ultimate Team screens and cutscenes run perfectly normal.
During gameplay:
• FPS remains stable and high
• No visible stuttering
• No frame drops
• GPU usage appears normal
• Temperatures are normal
• Other games run perfectly fine on the same system
However, the gameplay speed is clearly reduced, as if the match is not running at real-time speed. Player movements, ball physics and overall match tempo feel slowed down, even though performance metrics indicate everything is stable.
System information:
GPU: RTX 4050 Laptop
Driver: 595.71
CPU: (Intel Core i7-12650hx)
RAM: 16GB
Storage: SSD
OS: Windows 11
Power mode: Performance
Troubleshooting steps already attempted:
• Enabled and disabled V-Sync
• Limited FPS to 60 and 120
• Disabled Dynamic Resolution
• Switched between Fullscreen and Borderless
• Disabled G-Sync
• Forced High Performance GPU
• Verified game files
• Reinstalled the game
• Updated drivers
• Disabled overlays (EA App, NVIDIA, etc.)
• Lowered and raised graphics settings
• Ensured laptop is in performance mode
None of the above resolved the issue.
Community reports:
After researching on EA Forums and Reddit, I found MANY PC users reporting the exact same behavior:
• Gameplay in slow motion only during matches
• Menus working normally
• High FPS but reduced match speed
• Happens both offline and online
• Occurs even on high-end hardware
• Persists across different driver versions
This strongly suggests the issue may be related to engine synchronization, match simulation timing, or interaction between the game engine and PC hardware/drivers rather than individual system configuration.
This problem makes the game effectively unplayable and is extremely frustrating for paying customers.
Could you please confirm:
1. Is this issue currently under investigation?
2. Has it been internally reproduced?
3. Is a fix being planned in an upcoming patch?
Thank you.
