Quick answer

Patch 1.4 includes a fix intended to address Recon Plane and Flare enemy markers that remain visible on the Tactical Map longer than intended. The developer is monitoring reports after release, so update and retest the current build before calling the issue fixed or broken for everyone.

What the marker problem looks like

This page is for enemy red markers created by a Recon Plane or Signal Flare that remain on the Tactical Map longer than expected. It is different from a player ping, an active marker that is being refreshed by a new event, or a general problem rendering the map.

The symptom was reported by players before Patch 1.4, and Team17 acknowledged that the Recon and VOIP issues were under investigation. That older report helps identify the symptom, but it is not evidence about the current build. Use the dated patch status below for the current answer.

What Patch 1.4 changed

Patch statusWhat it means for your test
Patch 1.3 identified one cause under investigationA pre-1.4 screenshot or guide can be stale
Patch 1.4 implemented a fix for markers lasting too longThe first step is to update and reproduce the same event on the current build
The developer will monitor reports after releaseA remaining case should be recorded and reported; do not promise that every map or server case is gone

The official wording is intentionally cautious: the fix is expected to address the issue, and post-release reports will confirm whether it behaves as intended. That is why this page gives a retest procedure rather than claiming a guaranteed client-side setting.

How to retest after Patch 1.4

  1. Finish the game update, restart the client and note the platform and current build. A test on an older client cannot confirm the patch result.
  2. Join a live match where a Recon Plane or Signal Flare can create the relevant enemy markers. Record the map and game mode before testing.
  3. Open the Tactical Map after the event and note which markers appeared. Keep separate notes for Recon Plane markers and Flare markers when possible.
  4. Observe whether an old marker remains after the event has ended. Do not treat a newly refreshed marker as the same stale marker.
  5. Repeat the observation with another event on the same match if the situation allows. One confusing map view is weaker evidence than the same behavior reproduced twice.
  6. If the marker still remains too long, capture a screenshot or short recording and write down the platform, build, map, mode, server, event type and approximate time.
  7. Compare the result with the full Patch 1.4 notes and keep the report tied to the current version.

There is no supported menu toggle on this page that can delete a server-side or game-state marker. Avoid changing unrelated graphics, controls or voice settings while testing; that makes the report harder to reproduce.

If Recon or Flare markers still remain

What you observeHow to interpret itWhat to record
The same old markers remain after the eventThis may be a current reproduction of the reported issueEvent type, map, mode, platform, build and a screenshot
Only one map or server shows itIt is not enough to call the problem globalServer name or context, map, time and whether a second match differs
New markers appear while the map is openA fresh event may be adding valid markers rather than preserving old onesWhich marker existed first and when the later event occurred
The marker disappears after a fresh matchThe original report may not reproduce under the same conditionsVersion, map and event details so the result can be compared later

When reporting, use the official support or community channel and include the evidence above. A short report with a reproduction path is more useful than only saying that the map is covered in red dots. Do not present a player report as an official confirmation.

What not to use as a fix

  • Do not claim that reinstalling the game, changing DLSS or resetting keybinds removes a persistent Tactical Map marker; no source here supports that as a fix.
  • Do not use a pre-Patch 1.4 article to conclude that the issue is definitely still open.
  • Do not assume that every red dot has the same source. Separate Recon Plane markers, Flare markers, player pings and any active tactical marker before comparing results.
  • Do not change several game systems at once. A clean before-and-after observation is more valuable than an unrepeatable list of tweaks.

For graphics problems, use the DLSS 4.5 settings guide. For a broader list of current changes, use the Patch 1.4 notes. For map context and terrain routes, see the maps list and guide.

Quick answers

Is the Recon Flare marker bug fixed?

Patch 1.4 includes a fix intended to address markers remaining visible longer than intended. The developer is monitoring post-update reports, so the accurate answer is to retest the current build and report a repeatable failure rather than promise that every case is resolved.

How long should a Flare marker stay on the map?

The official notes describe the problem as markers remaining longer than intended but do not establish a universal duration in the source used here. Do not invent a timer; record the event and observed behavior instead.

What details should I include in a report?

Include the current build, platform, map, mode, server context, Recon Plane or Flare event, approximate time, what remained visible and a screenshot or recording if possible. Those details separate a stale marker from a newly refreshed event.