PC Players Report MyPLAYER Moving Without Input After December Update

Players on PC flagged a recurring control issue on December 26, 2025 that causes MyPLAYER characters to move autonomously and sometimes become lodged in arena corners. Reports describe the problem happening with multiple controllers, including PS4 and Xbox One pads, and surviving common resets such as reconnecting the controller and toggling Steam Input.

The pattern emerged as a cluster of posts over the holiday window, with multiple community members sharing similar symptoms and troubleshooting attempts. The original poster said the issue did not resolve after reconnecting the controller or disabling Steam Input, suggesting the problem is not limited to a single controller, cable, or a simple Steam configuration toggle.

Community responders offered practical troubleshooting steps aimed at isolating controller and input-mapping conflicts. Suggestions included using a wired controller with native XInput support, disabling conflicting inputs, and reviewing Steam Input settings. Those steps reflect common fixes for Windows controller compatibility issues, where native XInput devices like Xbox controllers often behave more reliably than wrapped or emulated controllers.

For PC players encountering the bug, try a quick sequence of checks to narrow the cause: switch to a wired controller that supports XInput natively, replug into a different USB port, and temporarily disable or reset any controller-mapping software you run alongside Steam. If you use a DualShock or other non-XInput pad, test with an Xbox-style controller to see whether the behavior persists. Community advice also stresses checking Steam Input settings and any third-party mapping utilities as they can introduce conflicting input signals.

The practical impact is immediate for anyone playing MyCAREER or online modes where uncontrolled movement can break plays, get players stuck in the arena, or force restarts. Because multiple users reported the problem across different devices, the issue appears to be affecting a subset of PC builds rather than isolated controllers.

If you encounter the bug, document the behavior and share details with support channels and community forums, including controller model, whether the pad was wired or wireless, USB port used, and any input-mapping software active at the time. That information helps the community refine troubleshooting and can speed identification of root causes for developers working on a fix.