Unique unit description popup stayed visible when a ranked match was found

:arrow_forward: GAME INFORMATION

  • GAME BUILD #: 125283
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

:point_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.

I was in the ranked queue and was checking out the new civ selection menu and noticed there are now description/stats popups/tooltips for the unique units. While I had a popup up a match was found and the civ selection dialog disappeared, but the unique unit tooltip (Flaming Camels, in this case) stayed up and nothing I could do could make it go away. Even after the match started it still stayed up blocking a portion of the minimap.

Disclaimer: I have only encountered this bug once so far, but the nature of the bug is such that I do not wish to investigate further myself.

:arrow_forward: FREQUENCY OF ISSUE

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

  • 100% of the time, but it only happened once so far.

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

  1. Click “find match” in ranked
  2. Open the civ selection dialog
  3. Select a civ (keeping the dialog up) and hover over a unique unit icon.
  4. Wait until a match is found

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?

The unit tooltip should disappear along with the civ selection dialog when a match is found. (It should also disappear when the game begins).

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

Hi @Thire7

Thanks for reporting this issue. I already let the team know about it and we are investigating it.