RatioGoldsmithMuse/valorant-fps-lag-fixer

What it does

Tick is a Windows desktop tool for VALORANT players whose game won't start, whose FPS collapses in fights, or whose ping spikes when peeking. It runs three kinds of checks and reports the cause in roughly a minute:

• Startup errors: you type the Vanguard or VALORANT error code (any format, e.g. van9003, VAN 81, val 44); Tick matches it against 19 codes and walks you through fixes, checking TPM 2.0, Secure Boot, Memory integrity (HVCI), IOMMU and the Windows build.
• FPS: a 60-second measurement through Intel's PresentMon reports average FPS and 1% low, then inspects refresh rate, monitor cable, integrated GPU, Game Bar recording, power mode, single-channel RAM and background apps.
• Lag: checks loss and jitter at the router and at the ISP, grades bufferbloat, lists background downloads and pings candidate server cities.

Software fixes are one-click and reversible; in-game settings are only listed, never edited. A restore point plus a change journal back the undo button, and no kernel driver is installed.

Quick start

1. Download Tick-1.6.4-portable-x64.exe from the latest release. It is a single portable file for Windows 10/11 x64 — no installer and no admin rights required.
2. Run it. The build is not code-signed yet, so SmartScreen may warn on first launch; choose More info → Run anyway.
3. For a startup error, type the code and follow the listed steps (the BIOS restart button runs shutdown /r /fw /t 0). For FPS or lag, start the 60-second test, review the findings and apply the software fixes you approve. Re-run the same test to compare before/after and use the Share button for the result card.

To build from source instead, you need Rust 1.85 or newer and the Tauri prerequisites:

git clone https://github.com/RatioGoldsmithMuse/valorant-fps-lag-fixer.git
cd tick
cargo test --workspace
cargo tauri build

The README does not state the output directory of cargo tauri build; check the Tauri build output for the resulting executable.

Constraints

• Windows 10/11 x64 only. The BIOS guidance is exact for ASUS boards; other boards get a generic hint to search the BIOS for "Secure Boot".
• Only errors that have a documented fix are handled. VAN 152 is a hardware ban and cannot be fixed; Tick says so rather than offering a workaround.
• Riot does not publish server addresses, so lag targets are public hosts in each city and may differ from the in-game ping by a few milliseconds.
• Your own changes are limited to Windows settings you approve; Tick never disables Defender, Windows Update, Memory integrity or Spectre mitigations, because Vanguard depends on some of them.
• Some old fan, RGB and overclocking tools ship blocked drivers (WinRing0x64.sys, RTCore64.sys); Tick names them so you can update them.
• FPS gain depends on what is found — a misrouted monitor cable costs far more than a power setting, and a correctly configured PC is reported as such.
• The project is MIT licensed; VALORANT, Riot Games and Riot Vanguard are Riot trademarks, and Tick is not affiliated with Riot.

HotRepo's take

The repo is Rust, MIT-licensed, and its rule data (errors, regions, drivers) sits in plain TOML files with cited sources, which makes the diagnostic logic auditable rather than a black box. On HotRepo it appeared on the Rust new-project list for 2026-11-01 with 110 stars gained in a window of about 11 hours from 2026-10-31 23:33 UTC to 2026-11-01 10:45 UTC, taking the repo to 110 stars and 3 forks; there is no recorded GitHub all-language daily rank, so this is a single new-list snapshot rather than a measured trend. The README's before/after 118 → 231 FPS example is the author's own demo, not an independent benchmark, and the unsigned portable build means early users are the ones bearing SmartScreen friction. For a game-adjacent diagnostic tool, the design choice worth watching is the negative one: it refuses to touch the game or anti-cheat and refuses to disable security features, which sets a clear boundary on what it will claim to fix.