v0.1.6

What's new since v0.1.5

Bigger release this time. Three headline wins: a crash inside the meter no longer takes the game down with it, a new Encounter DPS tab that shows your output over the whole fight instead of just the time you were swinging, and the overlay can now tell you when a new version is out (opt-in, off until you say so). Plus a stack of DPS and stability fixes — including one that was quietly dropping your own party members from the meter mid-session.

The big stuff

A crash in the meter no longer takes the game down with it. Every risky piece of the overlay — the calls in and out of the game, each rendered frame, the background pump, the name resolvers, and every individual tab — now runs inside a supervisor that catches crashes. If something inside the meter blows up, that one piece gets caught and sidelined instead of dumping you to desktop; the game and the rest of the overlay keep going. A tab that fell over shows a small placeholder with a Restart button instead of taking everything down with it. Anything that trips is parked for a few seconds and then quietly tries again on its own; if it keeps failing (three times in a minute) it stays parked until you hit "Restart addon" in Settings. It's the kind of fix you hopefully never notice.

A new Encounter DPS tab. The DPS panel now has two tabs that measure the same fight two different ways. Active DPS — what you had before — divides your damage by the time you were actually dealing it, so the clock effectively pauses during lulls; it answers "how hard do I hit when I'm on the target." The new Encounter DPS tab divides by the full length of the fight, idle gaps and all, matching the encounter timer on screen; it answers "what did I really put out over the whole pull." Burst builds will show a big Active number and a lower Encounter one — the gap between the two is your downtime. Both update live as you fight.

The overlay can tell you when there's an update. It's opt-in — the first time you run this build it asks once, "Check for Farever Companion updates?", with a plain yes/no. Say yes and it checks farevercompanion.com quietly in the background (about once an hour) and pops a small notice when a newer build is out, so you're not finding out weeks later that you're behind. Say no and it never phones home — and you can flip it either way afterwards under Settings → Updates. The notice shows what you're on next to what's latest (version, build hash, and date for each), and it'll even nudge you if you're running a rebuilt copy of the same version number — handy when a build gets re-cut without bumping the version. Nothing leaves your machine until you opt in.

Solo players get the per-skill breakdown for free. Playing alone, with no party? Your own row now expands to its per-skill breakdown automatically, instead of making you hold the modifier and click yourself every session. Group up and rows go back to behaving normally.

DPS and stability fixes

• Your party members stop vanishing from the meter mid-session. The 60-second name-cache cleanup added in 0.1.5 turned out to be a little too eager — it could evict your own party members, not just the random mobs you'd fought once. Party members are now exempt from the sweep and stick around for the whole session, the way they should.
• The meter picks itself back up instead of going dark. If the part that processes hits hit a snag and bailed, it used to stay dead until you restarted the game — the panel would just freeze on you. Now it restarts itself and keeps counting.
• Skill names land on the right rows. Name lookup was reading more of the game's data than it needed to, which could occasionally pull the wrong label onto a skill. It's now scoped to just the skill sheet.
• Solo auto-expand only fires when you're actually solo. An early cut of the feature above could trigger at the wrong moment; it's now tied to your real party size and reset per session.
• Tidied a doubled-up readout in the toolbar. The total DPS and encounter timer were showing twice along the top; the redundant copy is gone now that the tabs carry it.

Verifying your download

The download page now shows two hashes, not one. You get a SHA-256 for the .zip you download and a separate SHA-256 for the dinput8.dll inside it, each with its own copy button and a ready-made certutil / sha256sum command. The DLL hash is the one the overlay checks against itself, so it's the one that matters if you want to be certain the file running in your game is the real thing.

Heads up if you grabbed an older build: the packaging for v0.1.3 through v0.1.5 had a quiet bug where the download was a zip wrapped inside another zip. It still worked once you dug the real files out, but it was confusing. The release tooling now unpacks and inspects every artifact before it ships and refuses to publish a double-zipped one, so 0.1.6 onward is clean.

Known issues

• Nvidia Smooth Motion still breaks the overlay. No change here — turn it off in the Nvidia control panel until proper support lands.
• Combat log format is still preview. Full hero metadata and the on-disk shape are still moving; don't build tooling against the current schema yet.

What's being worked on

• Proper Nvidia Smooth Motion support (still the blank-overlay issue).
• Locking down the combat log schema and full hero metadata.
• Teammate weapons on rows (plumbing done, render side is the holdup).
• A map view for completionists — fog-of-war reveal of the zones you've visited so you can spot what you haven't found yet. Still on the list.

Behind-the-scenes stuff (probably don't care, but for completeness)

• The crash protection is a new supervisor layer that wraps every FFI export, render frame, worker tick, and tab body in a panic-catching guard, so a crash is contained to the smallest possible unit instead of unwinding all the way into the game.
• The combat-log writer moved into its own crate and now runs off the hot path on a dedicated thread, fed by a new internal event bus instead of being called directly for each plugin. Pausing tracking is render-only now — the pump keeps draining in the background, so nothing piles up while the display is frozen and the numbers are right the moment you unpause.
• Trimmed dead weight from the per-tick path — a leftover event queue, a couple of redundant locks, some no-op subscribers — which keeps frame timing steadier during long fights.
• New test coverage for the update checker, the combat-log writer's lifecycle (including crash-and-respawn), and the pump's pause/drain ordering — the bits most likely to regress.

Thanks as always for testing this in the wild — the bug reports are what keep it honest.

---

Download & verify

Only download from farevercompanion.com. Anything claiming to be Farever Companion that doesn't match the SHA-256 hashes below is not ours — don't run it.

There are two hashes: one for the .zip you download, and one for the dinput8.dll you copy into your game folder. The dll hash also ships inside the zip as a current-hash file.

Asset	farever-companion-v0.1.6.zip
Version	0.1.6
Released	2026-06-01
Size	2.78 MB (2,910,623 bytes)
SHA-256 (zip)	e0095a5535cab422c5fe88ef4dfb17dafd8721e4209e7998bd02d5c6d443ca00
SHA-256 (dinput8.dll)	6681e97da42b2484e507ac73b3a4b00313149c0c3b32559cad22206ec5b3ece9

1. Verify the download (the .zip)

Windows (PowerShell), run in the folder where you saved the file:

Get-FileHash .\farever-companion-v0.1.6.zip -Algorithm SHA256

macOS / Linux:

shasum -a 256 farever-companion-v0.1.6.zip

The output's Hash value must match SHA-256 (zip) above, character for character. If it doesn't, delete the file.

2. Verify the binary (dinput8.dll) after extracting

Once you've extracted the zip, verify dinput8.dll before copying it into your Farever folder. Run this in the extracted folder:

Get-FileHash .\dinput8.dll -Algorithm SHA256

macOS / Linux:

shasum -a 256 dinput8.dll

The output must match SHA-256 (dinput8.dll) above — which is also the value in the bundled current-hash file. If it doesn't, don't run it.

Windows users — please do this before extracting

Right-click the downloaded .zip → Properties → tick the Unblock checkbox at the bottom of the General tab → OK. Then extract. If you skip this step, Windows may falsely demand admin rights when you copy dinput8.dll into your Farever folder, and even granting admin can fail with an "unspecified error". Already extracted and stuck? Either delete and re-extract after unblocking, or open PowerShell in the extracted folder and run:

Get-ChildItem -Recurse | Unblock-File