Everything to know before you install

System requirements Compatibility Installing & updating Troubleshooting What it does Beta & limitations Risk Access

System requirements

Compatibility

Why won't it run on X11?

By design, and this will not change. On X11 any application can read and capture any other window, so the overlay would be plainly visible to anything that looks, including the game. Wayland isolates clients from each other, which is exactly what keeps the overlay out of the game's view. Running on X11 would throw that away, so the overlay refuses to start there rather than give you a false sense of what is on screen. X11 is out permanently; Wayland is the whole point.

Why does GNOME not work?

The overlay draws itself using a Wayland protocol called wlr-layer-shell. That is the only way to put a see-through window above a fullscreen game while still letting your clicks pass through to it. It is the same mechanism desktop panels use. KDE Plasma, COSMIC, sway and Hyprland all implement it. GNOME's compositor, Mutter, does not, and has declined to for years, so there is no way for the overlay to appear on top of the game there. This is a GNOME limitation, not something ArcVision can work around. GNOME will not be supported until Mutter adopts wlr-layer-shell. Until then, use KDE Plasma, COSMIC, sway or Hyprland.

Will there be a Windows version?

No. There is no Windows build, and there never will be one. The same goes for macOS. This is a Linux tool.

Why does system Steam get blocked?

The Flatpak sandbox is part of how the overlay stays out of the game's view. Running the game outside it removes that separation, so the launcher refuses.

Do I need to disable Secure Boot or install a driver?

No. There is no kernel module and no driver. The overlay is an ordinary user process that reads memory, granted by a one-time capability the installer sets on the binary.

Installing and updating

How do I install it?

One command on the target machine. It installs prerequisites, builds, grants the capability and adds a launcher to your application menu. Your access is set up by the installer itself, so there is nothing for you to copy in or configure.

How do updates work?

Automatically. Every launch fetches the latest version, fast-forwards and rebuilds before starting. Nothing to schedule, nothing to click.

Where are my settings kept?

~/.config/arcvision/settings.conf, written when you close the settings panel (INSERT) and on exit. They survive updates and restarts.

The overlay did not appear.

Check ~/arcvision-launch.log. The usual causes: the game was not running yet, system Steam was running, or the session is X11 rather than Wayland.

Troubleshooting

Most problems are one of three things: not on a Wayland session, system Steam installed instead of the Flatpak, or the capability not set. Work through these, and if you're still stuck, send a diagnostic report (below) and ask in #help on Discord.

The overlay doesn't show over the game.

Confirm you're on a Plasma (Wayland) session: run echo $XDG_SESSION_TYPE — it must print wayland. If it says x11, log out and pick Plasma (Wayland) at the login screen. Also make sure the game is running and that you started it through Flatpak Steam or Flatpak Heroic.

It says system Steam is running, or refuses to launch.

Only the Flatpak Steam is supported (or Flatpak Heroic for the Epic Games version). Remove the system package (sudo apt remove steam on Kubuntu, or the equivalent) or at least never run it, then relaunch. The installer sets up Flatpak Steam for you.

Names or entities don't show, or it says the world is invalid.

Usually a game update moved things. Updates apply automatically on launch, so relaunch once. If it persists, send a report and mention it in #help — a new build may need its offsets refreshed.

How do I send a diagnostic report?

If the app crashes or setup fails, a technical report is sent automatically so we can help. You can also send one any time by running ~/ArcVision/arc-report.sh. It contains system info, session and GPU, Steam state, memory and a crash check, and the tail of your launch log. If the overlay itself aborted, the report also includes its own error output and a crash backtrace (function names only) — no personal files and no credentials. A copy is saved to ~/arcvision-report-*.txt so you can also drag it into Discord.

Can I turn automatic reports off?

Yes. Add reportDiagnostics=off to ~/.config/arcvision/settings.conf. Running arc-report.sh yourself still works.

An item or container has the wrong name. Can I fix it?

Yes. Open Settings (Insert) and go to Names. It lists what is around you, closest first, with names we haven't verified marked "?". Pick or type the right name and Save, and it changes in the raid straight away. Your names are kept across updates. "Rename for me" changes a verified name for your own build only. Send my corrections (two clicks, never automatic) shares only your corrections with the maintainer; personal renames never leave your PC.

What it does and does not do

What is actually shown?

Players (boxes, skeletons, names, health, shields, squad number and color), ARC by type, containers and ground loot colored by rarity with a search filter, a radar, and a full overlay on the in-game map.

Is there an aimbot?

No, and there will not be. No aim assistance, no triggerbot, no recoil control, no movement changes, no unlocks, no spoofing, no network manipulation. ArcVision is ESP and nothing else.

Does it modify the game?

No. It never writes to the game's memory, never injects code, never hooks anything, and never touches network traffic. It reads, and it draws on top.

Beta status and limitations

How stable is it?

It works very well, but it is still in early stages. If you hit an issue, open a ticket in our Discord. It will be looked at as soon as possible, and if it turns out to be a genuine issue you can be given additional usage once it is resolved.

What happens when the game updates?

Expect breakage. The tool locates objects by their memory layout, and a patch reshuffles that layout. After an update, features misbehave or disappear until the offsets are found again, typically the core ESP survives and the map or a specific label goes first. Fixes come after the patch, not before it. Expect roughly a day of downtime following a game update while it is put back together.

What is known to be imperfect right now?

• GNOME is unsupported (its compositor lacks wlr-layer-shell). KDE Plasma, COSMIC, sway and Hyprland are supported; multi-monitor auto-pins the overlay to whichever screen the game is on.
• After a raid or zone change the map overlay needs a moment to re-locate the game's map widget.
• Weapon rarity comes from a hand-maintained table, new weapons appear without a rarity color until it is updated.
• Run the game in Borderless or Windowed mode. In exclusive Fullscreen the overlay can end up behind the game.
• Hurricane / First Wave caches only show within about 250 m; the game doesn't send farther ones.
• A few items still show rough names. Fix them yourself in Settings → Names and send your corrections from there, or report them with the 🏷️ button in #bug-reports on Discord.
• On handhelds the settings panel is small for a touchscreen; a larger handheld layout is planned.

Risk

Will I get banned?

Unlikely, but nobody can promise it, including us. ArcVision is built to stay out of the game's view. The game runs inside a Flatpak sandbox (Steam or Heroic), which hides other programs' processes and windows from it. ArcVision is a separate program outside that sandbox that only reads memory: no injection, no hooks, no writes.

Why is that not reassuring?

Anti-cheat bans are commonly issued in waves, applied retroactively to activity from weeks earlier. “Nobody has been banned yet” and “this is safe” are different claims, and only the first one is knowable. A read-only external tool avoids the loudest signals, no injection, no hooks, no writes, but quieter is not invisible, and detection changes over time.

What is Embark's anti-cheat policy?

Embark posted it on Sept 30, 2026 (read it here):

• Permanent bans for any account caught cheating. No warnings, no second chances.
• License restrictions: a banned copy of the game can't be used with another account, and any account ever linked to a banned copy is banned too.
• Hardware bans: the game is stopped from running on that machine at all. The threshold was recently lowered, and wider coverage is planned for later this year.
• Detection uses Denuvo, Anybrain and Embark's own machine-learning models, with a human reviewing appeals.

So what should I do?

Assume a ban costs you the copy of the game and the ability to play on that PC, not just one account. A second account on the same copy or the same machine is not a safety net. If that would genuinely upset you, do not use this. Using it also violates the game's terms of service, which is your decision to make with the real risk in front of you.

What about hardware spoofers?

Spoofers are tools that disguise a PC's hardware so a hardware ban doesn't recognise it. They can work, but ArcVision doesn't include them, support them or condone using them, and we won't help with them. They come from third parties, and using one is entirely your own risk.

Access

Where do I get help?

In our Discord. Bugs go in #bug-reports (members only, one post per bug), install and setup questions in #help or #support, and access requests in #request-access.

How do I get it?

Invite only.

Can access be taken away?

Yes. Access is granted per person and checked at launch, so a revoked user stops working on their next start. If the check cannot reach the server it allows a short offline grace period, then stops.

Can I share it?

No. Access is per person and revocable per person.