v0.1.7

What's new since v0.1.6

Heavy stability release this time, with one big new thing: the Map is here. But honestly, the headline of 0.1.7 might be the freeze fixes — this release kills a small collection of ways the game could hard-lock when the overlay was in use. If you've ever had to force-kill Farever through Task Manager, at least some of those should be gone now.

The big stuff

The Map tab is live. A top-down 2D map of the zone you're in. Drag to pan, scroll to zoom. Points of interest show up as pins grouped by category — orbs, chests, activities, critters, and more — alongside your live position and patrol routes.

It won't spoil you. The map only shows pins, routes, and zones for places you've actually explored. Discovery follows your in-game progress: a zone opens up on the map once you've explored it (usually by lighting its obelisk). Anywhere you haven't been yet stays hidden under fog — and the fog only hides what's there, not the terrain itself, so you can still see the lay of the land. It will never reveal something you haven't found yet.

Still a work in progress. The Map is new and will keep improving. One known gap: the anti-spoiler reveal is a little too eager about dungeons right now — dungeon completion isn't wired into the reveal yet the way the overworld zones are, so a dungeon you've already cleared can still sit under fog. That's a known limitation and it'll be fixed in a follow-up.

Freeze and crash fixes

This release is heavier on stability than any before it. If you've been seeing game freezes in busy areas or after toggling the overlay, this is the batch that addresses them.

• The game no longer locks up when you re-show the overlay. Toggling the overlay back on (Insert / F13) after it had been hidden for a while in a busy area could hard-freeze the whole game — a full Windows "Application Hang" with no crash dialog. Two separate root causes, both fixed: the data probe now fully pauses while the overlay is hidden and restarts cleanly on re-show, and a thread lock-ordering bug between the renderer and the meter pump has been removed.

• The game no longer freezes in crowded zones on long sessions. In busy hubs and large fights with lots of NPCs cycling in and out, the meter's background thread could deadlock against itself and lock the entire game — no crash, no error, just a hang. Fixed. The internal unit-tracking also now expires stale entries after 60 seconds, so it can't grow without bound over a marathon session.

• No more phantom encounters when you zone in or load a character. During the ~40-second window while a character loads, other players' nearby damage could kick off a bogus encounter before you were even live in the world — poisoning the meter before your first real fight. The meter now waits until you are actually in combat before opening an encounter, and buffers any hits that arrive in the meantime so the very first hit of your first fight is still counted.

DPS fixes

• Your party members show up in the meter again. In group play, a teammate's damage could be silently dropped and never counted toward the meter. Fixed at the source so teammates appear — and they now show their real names instead of a raw uid:<number>.

• F10 / [Reset DPS] clears the meter instantly again. Resetting your DPS was silently doing nothing in several out-of-combat situations, leaving stale numbers frozen on screen until the next hit landed. Now it always zeroes every meter and refreshes the display immediately, whatever your combat state.

• The update notice stops crying wolf. The optional update checker was comparing two different ID formats that could never match, so it showed a permanent phantom "new version available" notice. Release builds now compare versions correctly.

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).
• Continued Map polish — the dungeon reveal gap above and general improvements now that it's live.

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

• The shipped build got leaner: removed unused graphics backends, a dead DLL-injector path, and unused dependencies. Smaller, simpler binary.
• The zone-in fix is built on a new "buffer hits until you're resolved, then replay losslessly" path — nothing is lost during the character load window, it just waits for you to actually exist in the world before counting anything.

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.7.zip
Version	0.1.7
Released	2026-06-02
Size	2.96 MB (3,106,709 bytes)
SHA-256 (zip)	b456adfd45d002146f7eeae7790bcc3bb1eb825ea12fa520b067f4872c553898
SHA-256 (dinput8.dll)	daebaca9339323b174e62092062f277c250d47a74db446424e637e67ccf04576

1. Verify the download (the .zip)

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

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

macOS / Linux:

shasum -a 256 farever-companion-v0.1.7.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