GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: 153638 and prior
- GAME PLATFORM: Xbox / PlayStation?
- OPERATING SYSTEM: N/A
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
In multiplayer, when a player uses unit commands or selects UI elements on any selection wheel in a quick succession, the game has a chance to instantly crash and prompt a disconnect. Here’s a shortlist of commands that are more likely to cause crashes than others, but it seems to be every function that is unique to the controller input. From testing, these are the most common:
- B + d/pad down or up with units selected
- Select building/ all buildings with UI selection wheel
- Select all military of a type (archer class, cavalry etc)
- Control groups with UI selection wheel
To use some inputs/commands “safely”, players must lower their actions per minute, as to allow the game to process each action and avoid a crash.
This bug has been present for many game versions and it is difficult to pinpoint a starting date. A lot of controller players may not have had the APM necessary to trigger a crash years ago, or it may have been introduced in some of the many UI changes in earlier Xbox game patches.
Nonetheless, this issue poses a big problem in raising the controller player’s skill ceiling. Players are forced to limit, or avoid some commands in high level/high speed play. The controller community hopes to see a fix soon! 
FREQUENCY OF ISSUE
How often does the issue occur? CHOSE ONE; DELETE THE REST!
- Less than 25% of the time / matches I play (RARELY)
REPRODUCTION STEPS
List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!
The crashing issues with the high-speed use of the above commands seem to be related. But, there must be another variable influencing the crashes, because it can’t be replicated all the time. It has occurred at all game stages, early game with minimal units, and late game with max populations and hundreds of onscreen projectiles; 1v1 games and team games; high and low quality graphic settings; cross-play and controller only.
The most common freeze occurs with B + d-pad down, that is, deselecting one unit at a time command.
It has occurred most commonly with fast castle build. The fastest way to do the build order is to take 3 villagers right when feudal age is researched, have all 3 build a market and then deselect 2 so that the remaining 1 can be tasked to a second building. This involves 2 uses of d-pad down and bringing up the building UI wheel twice in quick succession; almost a guaranteed crash if done fast enough.
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
If the crash occurs, players will experience 3-4 seconds of a frozen game screen on the frame during which the “crashing input” was used, and then the game closes.
If not, happy days!
IMAGE
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
Unfortunately, due to the nature of this issue, it is impossible to screen grab or capture an image during a game crash on Xbox. Any game recordings produced after a crash show no evidence, as the inputs that cause the crash are not simulation-changing commands.
GAME FILES (SAVE / RECORDING)
Attach a SAVE GAME (.aoe2spgame) or GAME RECORDING (.aoe2record) of the match where you encountered the issue. Link it below if using an external file service.
*
Attempts at creating a save file or link to the game from the most recent crash were unsuccessful (Xbox game issue?). Here’s the match ID number instead: #416495727