Ranked benchmark test does not guarantee smooth gameplay

:arrow_forward: GAME INFORMATION

:point_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME BUILD #: 50700
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

The benchmark test doesn’t prohibid people form causing massive lag/griefing.

In ranked games people have the yellow clock from dark age onwards, indicating that their pc is struggeling to run the game, and that the lag will show up for all participants of the game.

The game becomes unplayable at later stages.
This is because of multiple reasons, e.g.:

  • It is possible to change mods and the video resolution, without having to rerun the benchmark test.
  • The benchmark test is usually run with all other apps closed. When people later play, they use voip and their webbrowser. The benchmark does not have overhead to compensate for that.

:arrow_forward: FREQUENCY OF ISSUE

:point_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • 50% of the time / matches I play (FREQUENTLY)

:arrow_forward: REPRODUCTION STEPS

:point_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:
Note that this is highly dependend on the leaderboard position.
If you have a high rank, the game participants do also likely have a high rank and theirfore a good computer.

  1. Play 4v4 ranked rm.
  2. Everytime someone has the yellow clock, when all players are in dark age, the game is affected.

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?
The benchmark test should guarantee that nobody has the yellow clock that early, at least before there are 200 units on the field.

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.

:arrow_forward: GAME FILES (SAVE / RECORDING)

:point_down: 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.