What You're Actually Looking At
Valorant Gameplay Test Full Game is a community term for recording and testing your complete matches against Riot's anti-cheat and performance requirements. It's not an official tool from Riot. It's something players built because they needed a reliable way to verify that their setup meets the standard before entering ranked queues or tournament-style lobbies. The process involves capturing your full gameplay session, analyzing frame pacing, input latency, and visual artifacts, then comparing the results against known benchmarks for competitive Valorant. You need a few things running in parallel. First, a screen capture tool like OBS or Nvidia ShadowPlay at a minimum of 1080p and 60fps, but honestly 1440p at your monitor's native refresh rate gives you the clearest data. Second, an overlay that logs mouse acceleration, raw input status, and frame times — presentmon works well here, or if you're on Nvidia hardware, the Ansel in-game overlay paired with RTSS for frame pacing graphs. Third, a reference benchmark video of a known-good gameplay clip so you can compare visual response times side by side. I run this before every ranked session now. It used to take me about twenty minutes each time, but I trimmed it down to roughly seven by using a macro script that fires up OBS, launches the benchmark overlay, starts a demo replay, records for exactly three minutes, and then generates a summary report automatically. The script runs on AutoHotkey. I wrote it myself after spending a week figuring out which overlay APIs actually coexist without crashing the game.
Here is where people go wrong. They run the test with Discord open, with Chrome tabs loaded, and with RGB software like iCUE or Razer Synapse all active. The result is noise. Your frametimes look fine until you watch the graph and notice a consistent 2ms stutter every eight seconds — that's your RGB polling cycle, not your GPU. Close everything that isn't strictly necessary. Disable hardware-accelerated browser processes. Turn off any per-application performance profiles that might be overriding your settings mid-session. There is also a specific edge case that tripped me up for weeks. When you run a Valorant Gameplay Test Full Game on NVIDIA Reflex enabled settings, the frame limiter behaves differently depending on whether you are using the in-game limiter or RTSS together. I kept getting inconsistent results because Reflex was capping frames at 144 while RTSS was trying to cap at 165. The two were fighting each other. The fix was simple: pick one limiter and stick with it. I disabled the in-game frame cap and let RTSS handle it exclusively, then my frametime graphs became consistent within a 1ms variance across the entire session. One more thing beginners overlook. The test only tells you about your local performance. It does not measure network latency to the actual Valorant servers. You need to run a separate ping and packet loss test during the same session. Open a command prompt, ping the nearest Valorant region endpoint repeatedly, and log the results alongside your frametime data. A player can have perfect 1ms frametimes and still feel sluggish if their packet loss is sitting around 3%. I track both in the same spreadsheet so I can spot when a poor session is actually network-related rather than hardware-related.
The whole process, done correctly, takes about ten to twelve minutes from start to finish. That includes launching the test, recording, generating the report, and reviewing the output. It is worth doing before ranked games because the alternative is spending three hours in Immortal and not knowing whether you lost because your crosshair placement was off or because your GPU was dropping frames during the spike timing on Ascent bind. Once you have the baseline data, the difference is obvious. If you want a download link for the tools involved, none of them are single-package downloads. OBS is free from obsproject.com. Presentmon is on GitHub from the Intelligence-Based Monitors project. RTSS comes from techpowerup.com. The AutoHotkey script I described is something you build yourself from the pieces above, but if you search for "Valorant frametime test script autohotkey" on GitHub you will find several community versions. Most of them are outdated though. Riot patches the game frequently enough that overlay compatibility breaks regularly. Keep your scripts updated or just build your own. The most important insight most players miss is that consistency matters more than peak performance. A system that holds steady at 200fps with 3ms frametime variance will outperform a system that hits 300fps peaks but spikes to 12ms under load. Run your test long enough to catch those spikes. Three minutes minimum. Five is better. Ten will show you everything worth seeing.
Get the Full Details
