Neon Abyss 2 Cursor 60fps Lock: Why It Happens & Fixes

Why does the Neon Abyss 2 cursor look stuck at 60 FPS while the game itself runs faster? After the 1.0 launch on October 8, 2026, a player reported exactly this: the aim cursor was not respecting the unlimited FPS setting, and appeared to run with a 60 FPS cap even though the rest of the game rendered smoothly. There is also an official explanation for a related frame rate cap in multiplayer, tied to network data transmission.

This guide covers what is actually known about the 60 FPS cursor issue — the player report, the developer FAQ statement on frame rate limits, and the 1.0 settings that interact with it — plus the workarounds the community is currently trying. Where a fix has not been confirmed, we say so rather than invent one.

The 1.0 Report: Aim Cursor Capped While the Game Is Not

The clearest documentation of this issue comes from a Steam discussion posted shortly after the 1.0 release. The thread was originally about ultrawide support — a player who had beta tested during Early Access but dropped the game over the lack of ultrawide returned for launch, and the developers confirmed in the thread that 21:9 resolutions (2560×1080, 3440×1440, 3840×1600) had been added to the PC version.

In their reply, that same player added a second observation, quoted here in full because it is the definitive description of the bug:

"One thing I did notice though, was that the aim cursor wasn't respecting unlimited FPS like the rest of the game is. Can that please be looked into? The aim cursor looks like it's running at a 60 FPS cap."

The details matter for your own diagnosis. This is not general stutter, and it is not the whole game dropping frames — it is specifically the aim cursor (the crosshair you use to aim) updating at what looks like a fixed 60 updates per second while the game world runs uncapped. If everything on your screen is choppy, you have the broader stutter problem instead; if only the cursor is choppy, this is your issue. The thread showed four replies at the time of writing and no developer confirmation of a fix, so the current status of the bug is To be confirmed.

The Official Position on Frame Rate Limits

While the developers have not (as of writing) publicly responded to the aim cursor report specifically, they have addressed frame rate caps in the official FAQ, and it is the best available clue to what is going on. Asked "Why is the frame rate in the game locked?", the developers answered:

"We have limited the frame rate in the multiplayer mode to prevent network latency and lag caused by large amounts of data transmission. We are also researching how to optimize it so that the limitation can be lifted."

Two things follow from that statement. First, a frame rate cap in multiplayer is intentional: it exists to keep four-player co-op sessions from drowning in network synchronization overhead. If your gameplay feels capped at 60 FPS specifically during online co-op, that is by design, and no local setting will remove it until the team optimizes it away — which they say they are researching. Second, and more speculatively: a rendered element like a cursor updating on a fixed 60-cycle is consistent with the kind of logic-tick capping a developer applies to UI elements. That is our interpretation, not an official statement — the exact technical cause of the aim cursor cap is To be confirmed.

The practical takeaway: if you only notice the 60 FPS feel in multiplayer, do not burn an evening reinstalling drivers. The cap is documented, deliberate, and waiting on an optimization pass.

Settings Worth Checking First

Before assuming you have the bug, make sure it is not a settings artifact. Version 1.0 reworked how graphics and frame rate behave, and a misconfigured setting can mimic the symptom:

• Graphics quality and frame rate are now separate settings. Since 1.0 they are configured independently, so check both — a quality preset change can interact with your frame rate selection in ways Early Access settings did not.
• PC frame rate options are 60 / 120 / unlimited. If you left the game on the 60 FPS option, the entire game — not just the cursor — will run at 60. Switch to unlimited (or 120) and see whether the world speeds up while the cursor does not; that contrast is the signature of the bug.
• Vertical sync is handled per display conditions. If you have forced vsync in your GPU control panel on top of the in-game setting, that can introduce its own input lag on the cursor. Let the in-game setting govern, or test with the control-panel override off.
• Update the game itself. The aim cursor report came from launch day; later patches may have touched it. There is no published fix to confirm, which is precisely why it is marked To be confirmed.

Community Workarounds and What Not to Waste Time On

Because the cause appears to sit in the game's code rather than in user configuration, no reliable community workaround has been confirmed yet — claims that a particular driver, overlay tweak, or config edit fixes the aim cursor specifically are To be confirmed. What the community has established is what does not help: the reporter was already running the freshly updated 1.0 build with ultrawide support working fine, so this is not a case of an outdated install.

Given that, here is the sensible triage. If the cursor cap annoys you in single-player, test whether it persists across a short run with frame rate set to unlimited and vsync controlled by the game — if the world runs at 144+ and the cursor still visibly steps at 60, you have reproduced the reported bug. If it happens in multiplayer, it falls under the documented multiplayer frame rate limitation, and the only real answer is the optimization the developers say they are researching.

Either way, add your report to the existing Steam thread rather than starting a new one: the original reporter explicitly invited the developers to look into it, and a thread with many confirmations is far more likely to get attention than scattered duplicates. Meanwhile, if your actual complaint is broader choppiness — the whole game hitching, rooms stuttering on entry, or drops during heavy builds — that is a different, largely resolved problem, and our general stuttering guide covers its history and fixes.

Related Guides

• Neon Abyss 2 Cursor Stuttering: Causes & Fixes
• Neon Abyss 2 Config File Location: Find & Edit Settings
• Neon Abyss 2 Co-op: 4-Player Multiplayer Guide