Agent 64 Fixes & Performance: EAC Stutter, Crashes, Steam Deck & Controller Settings

Quick Answer: If Agent 64 stutters, launch it without Easy Anti-Cheat before changing any setting — three players independently report the stutter disappearing entirely, one of them at a locked 60 FPS, and the developer's own first question was whether it persisted without EAC. The catch: online co-op and Arena require EAC, local split-screen does not. If you need EAC on, the second thing to check is that Windows is running the game on your dedicated GPU. If you crashed in Online Arena or near the mission 1 helicopter, update: ten builds shipped in the first four days.

Version note: Current for v1032 (August 17, 2026). Patch contents are quoted from the developer's own Steam announcements; everything else comes from forum threads, several of which the developer answered directly. Single reports are labelled as such. The game is seven days old and shipping roughly a build a day.

The Hotfix Timeline

Replicant D6 is a solo developer and shipped ten builds plus three status posts in the first four days. What changed:

If you bounced off the game on launch day because of a crash, the build you played is several versions old. Two of these are worth knowing about specifically:

• The helicopter crash (fixed in v1011). On mission 1, one player crashed when throwing a tracker near the helicopter; another could not approach it at all on the second and third difficulty tiers. The developer replied "I'm on it" and then "Fixed now in v1011."
• The double-bind crash (fixed in v1017). If you had mapped two buttons to gadget selection, the first mission's tutorial prompt crashed the game. Worth knowing if you rebound controls before your first run and concluded the game was broken.
• The Temple water pit (fixed in v1020). The room before the Temple's final room had no barrier on its left side; fall in and you could not climb out, and the same gap existed in the following mission where the stage runs in reverse. The developer's reply was blunt — "Yeah it was an oversight. Will be fixed in tonight's patch" — and it shipped the same night. If you are on an older build and stuck in that water, reloading the checkpoint is the only way out.
• The empty lobby browser (fixed in v1026). For part of August 14, lobby search showed nothing at all — every lobby was invisible. If you tried to find an online game that day and concluded nobody was playing, look again.

v1020 also does something patches rarely do: it hands back achievements you already earned. The note reads "Made a few Achievements retroactive in case you missed those before their fix." Load the game once and check your list before you replay anything for a missing unlock — see the Achievements Guide.

v1028 fixes a mission-blocker you may have blamed on yourself. The note reads "Changed the way character pathing is updated, likely fixing the sometimes failing of the Dana event in Castle." If a scripted moment in Castle never triggered and you replayed the level assuming you had missed a step, you had not — and the developer's own hedge, likely, is worth keeping. Replay Castle on the current build before reporting it again. The same build stops melee disarm from crashing the game against bots, which is the other thing on that list you can actually run into.

v1031 (August 16) closes a second Dana-related crash, this one in co-op. The note names it precisely: "Fixed a crash for when the host dies in Coop missions with Dana." That combination — host death, co-op, a Dana mission — is a specific enough shape that if your co-op sessions kept ending in the same place, this was probably why. The same build made the Gilded Weapon show up in cutscenes, where it had been rendering as the default model.

Decision rule for both: the Dana missions are where this game's scripted-event bugs have clustered across three patches. If a co-op run breaks near one, update and retry before you write it up — two of the three fixes shipped in the last 48 hours.

v1032 (August 17) closes the delayed-unlock bug for good. This one had a history: rewards you had genuinely earned would not appear until you left the menu and came back, the developer acknowledged it, v1020 attempted a fix, and the original reporter said afterwards that it was not fully fixed. v1032's note is broader than the earlier attempt — "Fixed some mission unlocks not happening right away when unlocked (Gilded Character Skin for instance)" — and it changes what a missing unlock means. On the current build, an unlock that is not there is not there. Report it rather than waiting for it to surface.

The same build adds a small quality-of-life fix controller players had been asking for indirectly: pressing Fire while cycling weapons now steps back through the wheel, so overshooting your weapon no longer means a full loop.

v1024's Act-unlock change is the one to reload for. "Slight balance changes and clarifications for Story mode Act unlocks" is the developer's only public description, with no numbers attached — but it is the system that generated most of the launch-week complaints. If you stopped playing because an Act gate looked unreasonable, check what it asks for now before you decide. The missions and Cyphers guide covers how the gate works.

Frametime Stutter: Check EAC First

Symptom: the frame counter looks fine — one player reports never dropping below 60 FPS — but the game hitches constantly.

Finding: it tracks with Easy Anti-Cheat. In the stutter thread, the developer's first reply was to ask whether it happened without EAC. Three separate players answered:

• "Nope, not a single stutter without EAC on. That's the fix for now."
• "Also been having the same problem, without EAC works perfectly fine."
• "I'm having the same stuttering issue on my system even with my mouse polling set to 1000hz. With EAC off it has 0 issues. I've tried different framerates and nothing seems to fix it."

What to do: launch the non-EAC option for single-player and local split-screen. Accept EAC for online play, or stay offline until the developer resolves it. This is a workaround players found, not a fix the developer has shipped, and he has not stated a cause.

If you need EAC on, check which GPU Windows is giving the game — but do not expect it to hold. One player found Windows running Agent64.exe on the integrated GPU rather than the dedicated card and set it to High Performance in Windows Settings → Display → Graphics, which helped noticeably with EAC still enabled. It is a free check and worth doing. What happened next is the part to know: the same player later reported still stuttering constantly on mouse afterwards, and a second player who tried it wrote that it "worked initially, but began stuttering again." Treat it as a partial, temporary improvement rather than the answer.

Mouse is consistently worse than controller. The player above stutters constantly on mouse at 1000 Hz polling and calls the game much more playable on a pad with EAC on. If you are keyboard-and-mouse and need EAC, that is the closest thing to a working compromise.

Mouse polling rate is a separate, smaller factor. The developer had previously pointed at polling rates above 1000 Hz. One player reports gameplay improving after setting polling to 1000 Hz but stutter still present — so try it, but do not expect it to be the whole answer.

GPU vendor does not explain it. One player on an RX 7900 XT stutters with EAC while a friend on an RTX 2060 Super does not, which read like an AMD driver problem until a third player on an RTX 3090 with current drivers reported the same constant stutter. Both vendors are represented; nothing has converged.

The Steam Deck comparison is the most useful data point on the thread. The RTX 3090 player ran the game on their own Deck for comparison and got "not a single stutter" — on hardware an order of magnitude weaker. That points at a software interaction rather than raw performance, and it is worth mentioning if you file a report. One other Deck player contradicts it, reporting stutter with EAC on in single-player, so do not read it as "Decks are immune."

One report of a post-v1018 regression. A player who had no issues before the August 12 update now reports stutter with EAC both on and off. Single source, and it contradicts everyone else in the thread — noted so you know it is on the board, not as an established pattern. If the EAC workaround stops working for you after updating, say so on that thread.

One case resolved itself through Windows Update, and that is worth a check before anything else. The RX 7900 XT player above — the one whose case made this look like an AMD driver problem — came back four days later with: "After a windows update yesterday, the issue is completely gone. I didn't do anything else." One person, no diagnosis, and he had already noted his setup dislikes certain Unity games with a second monitor plugged in. But installing pending Windows and GPU driver updates costs you nothing and is the only step on this page that has taken someone from constant stutter to none. Do it before you start swapping settings.

Where this stands after four days: turning EAC off is still the only workaround that has worked for multiple people. Everything else is partial — the GPU assignment check helps some and stops helping, a Windows update cleared one case, controller beats mouse consistently, and one player with an i9-13900K and an RTX 3090 has tried all of it and still stutters on mouse.

One player reports a possible memory leak — performance degrading as they progressed through a level — and the developer replied "I see. I'll be looking into it." The same player later said the slowdowns happened at varying points rather than always worsening, so the leak reading is unconfirmed. Single source, developer aware. The same player also reports each patch running worse than the last and calls the original demo flawless, which nobody else on the thread has echoed.

Have these four answers ready before you post about stutter. The developer's opening questions on that thread are the same every time, and a report without them goes nowhere: is V-Sync on or off, do you have a G-Sync monitor, what framerate are you getting, and is it one stutter occasionally or something more regular. A fifth data point worth adding if you have it: a Steam Deck player reports occasional dips from 60 to about 40 FPS that feel random, which is a milder shape than the constant hitching described elsewhere.

Crashes the Developer Wants Logs For

Two level-specific crash-to-desktop reports arrived after v1024, both showing a brief error message before the game dies: one on the Castle outro cutscene (Secret Agent difficulty, Xbox controller, integrated graphics laptop) and one a few minutes into the Tower level (Ryzen 5 2600X, RTX 2060, Xbox controller, Steam controller support disabled). Each is a single report.

The developer's answer to both was the same and it is the actionable part: he needs a log, and he asks people to join the Discord channel from inside the game's menu and file the bug report there. Steam threads are where he sees the symptom; Discord is where the log gets to him. If you hit a crash on a specific level, capture it and go there — a description on its own has not moved either of these forward.

Online Arena Crashes and Desync

Status: actively changing. The original bug crashed players when someone joined an active lobby. After three attempts across launch day, the developer took the direct route in v1015:

"instead of joining matches mid-game, the game will make you queue for the next session instead. This is temporary solution while I find the cause of the live joining bug."

So mid-match joining is gone for now by design, not broken. If your lobby will not let a friend drop in, that is the current intended behaviour.

Two further crash reports exist with no replies yet, both single-source: a Unity error crashing the game during multiplayer Arena (a "null instance not set to object" message flashes at the top of the screen, then the game closes, reportedly every session), and the EAC-free offline version crashing two to three minutes into the storyline on any difficulty. The second one matters if you adopted the EAC workaround above: that player reports the executable being deleted by the crash, so Steam cannot find it next launch and re-downloads it. If the non-EAC launch option does that to you, you are stuck between the two problems and it is worth posting your specs and the tail of your Player.log. That player's log ends on a save-file write, and the crash lands at no consistent point in the run. Do not read the missing executable as a corrupt install or an antivirus quarantine before you check whether the crash came first.

EAC, Co-op and What Requires What

Online co-op requires EAC. Local split-screen co-op does not. That answer came from a player in the co-op thread rather than from the developer, but it is consistent with everything else on the board, and one player decided against buying on the strength of it.

Combined with the stutter finding, that produces a clean rule:

• Solo or couch co-op → launch without EAC, get smooth frametimes.
• Online co-op or Arena → EAC required, accept the stutter for now.

"Please unload msio64.sys before starting the game" — solved, and the culprit is named. This EAC message blocks launch outright. The player who hit it traced it to ASUS Aura, the RGB lighting utility, via other games' threads on the same driver, and uninstalling Aura let the game start. They did not test whether reinstalling Aura brings it back. If you get this message, close or uninstall your ASUS system utilities before troubleshooting anything else — msio64.sys is a hardware-access driver and anti-cheat refuses to run alongside it.

Steam Deck

Players are running the game on Deck, and the reports so far are mixed rather than bad:

• Frame dips from 60 to around 40 FPS, described as intermittent.
• A Deck player getting stutter in single-player with EAC enabled, who then planned to test without it — the same pattern as desktop.
• A texture bug on the Castle level, one report, no replies. Note the developer separately fixed a "borked Castle map" in Arena in v1004, which may or may not be the same asset.

There is no official Deck compatibility rating discussion from the developer as of August 14. One desktop player who also owns a Deck reports the Deck running the game without a single stutter while their RTX 3090 desktop stutters constantly with EAC on.

Controller: Working, But Under-Configured

The game ships full controller support including DualShock and DualSense, and this is a game people specifically want to play on a pad. Two gaps are drawing crowds:

No separate aim-mode sensitivity for controller. Ten players in one thread report the same problem: the sensitivity setting applies to mouse, so on a pad general turning is too slow while aim mode is too twitchy. Requests include a separate slider and control over the reticle bounding box before the view starts moving. The developer had not replied as of August 14.

No native N64 controller support. Unsurprising, but this is a GoldenEye homage and people are trying. What the thread established:

• A player published a Steam Input layout for the NSO N64 controller to the community page, mapping A/B to A/B, X and Y to C-Down and C-Left, bumpers to L/R, right trigger to Z-R, left trigger to Z, and both sticks to Joystick Mouse.
• Their key tip: start the level with keyboard and mouse first, then switch to the N64 pad.
• One player reports an NSO N64 controller being recognised as players 2 and 3 simultaneously. Single report, unresolved.
• Real N64 controllers work through third-party adapters, per two players naming specific converters.

Steam Input configs resetting to default has two reports and no answer yet.

Smaller Reports (Single Sources, Not Yet Patterns)

• Next Gadget keymap bug — one report, one reply. Related: binding two buttons to gadget selection crashed the first mission until v1017.
• No LAN mode — confirmed absent by players; online or local split-screen only.
• No simultaneous mouse and gamepad input — a request rather than a bug, raised specifically by Steam Deck and Steam Controller players who want trackpad aiming with pad buttons. No reply.
• Co-op objective not completing for the host on mission 3 — the developer has it. Escaping the jail cell, the first objective completes for the guest but never for the host, with Dana standing motionless; the reporting pair tried three times from different positions. The developer replied "Thanks I'll look at it," and v1020 does not mention it. If you hit this, hand hosting to the other player — the objective completes normally for guests.
• A crash a few minutes into the Tower level, error message flashing before the game closes to desktop, on an RTX 2060 with a controller and EAC on. The developer asked for a log through the in-game Discord link rather than the forum, which is the right route for any crash you can reproduce.
• Crash to desktop on the Castle outro cutscene after clearing the level on Secret Agent. One report, no reply. Note that v1024's crash fix was specifically for level initialisation, so neither of these two — one mid-level, one on the outro — is covered by it. If you can reproduce either, the log is the thing the developer actually needs.
• A missing texture on the Castle level now has two reports — one on Fedora Linux, one on Steam Deck, both above the player's head before entering the courtyard.
• Audio silently dropping after alt-tabbing, not restored by reinstalling. One report.
• Aim Mode sensitivity doing nothing on an analogue stick — values of 1 and 400 feel identical on an 8BitDo Pro 2. One report, and a more specific version of the controller-sensitivity complaint below.
• The Tower level mask is not missing. A player reported the second level's mask not appearing where the picture showed it, then posted "nvm im blind"; the developer replied cheerfully. Masks are findable collectibles with in-game location hints — if yours seems absent, look again before reporting it.

What Is Coming

The developer published a roadmap on August 16, and it is short. Asked directly whether development is finished apart from support, he answered:

"What you can expect is a final bonus mission (teased in the game itself), and official mod support. No timelines because I'm a solo dev and I'm always late."

That is the whole list: one bonus mission and official mod support, with no dates. Asked in the same thread to also address the recurring requests — quick saves, the Cypher requirement, blood, crouching — he did not reply. Treat those as unanswered rather than declined, but do not plan around them arriving.

The Supporter Edition is live (August 12): an upgrade pack containing the cosmetic Gilded Sparrow G5 and the original soundtrack. Buying it later costs no extra, so there is no reason to rush.

Still open on the developer's side: the Online Arena hotjoin cause — mid-match joining stays disabled until he finds it — and the reported memory leak. The Cypher progression system that dominates the general forum did get tuned: v1024 shipped balance changes and clarifications to the Story mode Act unlocks without publishing the numbers, and players have since posted before-and-after figures that suggest the requirement came down.

One Rumour Worth Killing

An August 17 thread opened with the claim that Cyphers had been removed from the game — the poster had cancelled a refund over it. They have not been. Two players in the same thread corrected it within the hour: one is currently sitting on a 26-Cypher requirement for Act 4, and another started a fresh save, cleared the first mission on Easy and still had to spend Cyphers to unlock episode 2.

The claim resurfaced in a second thread the next day and was corrected the same way, by a player who simply said "This isn't true. They're definitely still there." Two separate threads, two independent corrections, no patch note anywhere naming a removal — this rumour is spreading faster than it is being checked.

If you shelved this game over the Cypher gate and came back because you heard it was gone, the gate is still there — it just costs less than it did. What actually changed is covered on the missions and Cyphers page.

Multiplayer Content Is Locked Behind Challenges, and Nothing Says So

Not a bug, but it produces the same experience as one, and it comes up repeatedly from players who booted the game with friends and concluded the multiplayer was an afterthought.

Maps and options unlock by completing Challenges. The game does not communicate this, so the default view of the multiplayer menu looks like the whole offering. One player's account is representative: "it wasn't obvious there is content to be unlocked for MP & I thought mp was just after thought until i watched the live streams." The most-repeated fix request is simply to show the locked entries greyed out rather than hiding them.

Two practical consequences. If you want the full map pool available for a session with friends, someone has to grind Challenges first — and per a player who has finished most of the campaign on Secret Agent, the Challenges from the second set onward are considerably harder than the campaign difficulty they nominally sit alongside. If you only want to play against bots, most of what you would play is behind that same wall.

The developer has not responded to the request. Challenge par times themselves: Par Times Guide.