\n
<\/br><\/code><\/p>\n\nLast week, EA\u2019s battle royale shooter Apex Legends<\/em> launched a \u201ccollection event,\u201d which is shorthand for a limited-time setup that is mostly about players buying a bunch of cosmetic items from the in-game store. The only problem is that this time, the massive update has made the game nearly unplayable for many people on consoles. <\/p>\nWithout warning, the battle royale shooter\u2019s usually tight and responsive controls \u2014 a known quantity for Respawn Entertainment games since Titanfall <\/em>and a reflection of its Call of Duty<\/em> heritage \u2014 have become slow, laggy, and frequently unresponsive. Even worse, simply playing the game can make your control inputs feel altered even in the dashboard and while using other games; restarting the console seems to fix this issue.<\/p>\n\n\n\nWe are continuing to investigate reports of input delay some Xbox players are experiencing. Thank you for your patience while we work to resolve this.<\/p>\n
\u2014 Respawn (@Respawn) June 27, 2022<\/a>\n<\/p><\/blockquote>\n<\/div>\n<\/div>\nPlayers on Xbox Series X consoles appear to be complaining the most, especially when paired with one of Microsoft\u2019s Elite gamepads. Without any specific information about what the problem is, I can only describe what I\u2019ve experienced, which is a combination of lag, as well as failed input detection that can make it hard to do things like use burst fire weapons, change directions, or even pick up items from the ground. After trying it out a bit over the weekend, I noticed input lag as an issue the most while playing on Xbox Series X and Series S, using both an Elite 2 gamepad, as well as newer Xbox Series gamepads that include the share button.<\/p>\n
Acknowledgment of the problem by developers has been limited to a couple<\/a> of reply tweets last week<\/a> and one Monday afternoon saying the team is continuing to investigate<\/a>. However, not everyone who plays the game follows its official Twitter account or dug into replies to find the initial statements, leaving many players in the dark about what might be going on while they try to play a competitive shooter using controls that just don\u2019t work. <\/p>\n\n\n\n @linkavich001<\/a> <\/p>\nI’ve said it a lot but I really love Apex, it has elements to it that keep bringing me back, but I’m just about done. Respawn doesn’t show any interest in listening to the majority of its player base, only high profile streamers or “pros” get their voices heard & the changes they cry for aren’t what is best for the Apex Community. I know I can’t be alone with this sentiment. #Apex<\/a> #apexisdying<\/a> #devsdontcare<\/a> #xbox<\/a><\/p>\n \u266c original sound – Linkavich<\/a> <\/section>\n<\/blockquote>\n<\/div>\n<\/div>\nAs it is, people who play the game have been left to discover the problem on their own and pass around possible solutions. I tried some of them, like updating the controller firmware or not updating it or plugging the pad in with USB instead of playing wirelessly. One suggestion I haven\u2019t been able to try is using an older Xbox One controller. Of those, plugging the gamepad in seemed to help a bit, but it still wasn\u2019t as responsive as it used to be. What I saw was consistent with some reports posted on Reddit<\/a>, where plugging in seemed to fix the failed input detection issue without resolving the lag and stuttering. This post highlights<\/a> how, after playing Apex<\/em>, they experienced input lag system-wide on the dashboard and in other games, which I also noticed. <\/p>\nOddly, this may not be the only game with this issue on Xbox, as MLB The Show 22<\/em> players have complained about similar problems<\/a>, but it was one that didn\u2019t exist within Apex Legends<\/em> prior to last week\u2019s update.<\/p>\n
![\"\"](\"https:\/\/cdn.vox-cdn.com\/thumbor\/xXfl4RWgLphJhbPsKM_8BcMqxMI=\/0x0:1456x819\/320x0\/filters:focal(0x0:1456x819):format(webp):no_upscale()\/cdn.vox-cdn.com\/uploads\/chorus_asset\/file\/23656414\/apex_legends_screenshots_s13_e01_awakening_lifelinetakeover_01_clean.png.adapt.1456w.jpg)
<\/p>\n