A score hides how the run went
A benchmark gives you one number per drill. It cannot tell you whether you lost points by starting late, overshooting the target or letting the crosshair drift off a moving one. Those mistakes look different from each other and respond to different drills, which is the idea behind the flick vs tracking diagnosis. A recording keeps what the score throws away: where the crosshair was at each moment.
You do not need to record every run. One clip of a run that felt wrong is enough to start, and two clips from different weeks show whether the same mistake is still there.
Record the run
The trainer runs in a browser tab, so any screen recorder that can capture a window will do.
- Windows: Xbox Game Bar starts and stops a recording of the focused window with Win+Alt+R.
- macOS: Shift+Command+5 opens the screenshot toolbar, which can also record the whole screen or a selected area.
- OBS Studio: its replay buffer keeps the last stretch in memory and saves it on a hotkey, so you press the key right after a bad run instead of recording every attempt. NVIDIA's overlay has an instant replay that works the same way.
Record at the frame rate you play at if you can. A flick takes a fraction of a second, and a low frame rate leaves only a few frames of it to look at.
What to look for in the footage
Step through the clip a frame at a time. VLC does this with the E key, and most video editors have a frame-step button. Watch the crosshair, not the targets.
| In the footage | What it usually means | Train with |
|---|---|---|
| The crosshair lands past the target and comes back | Overshoot on a flick | FLICK |
| It stops short and needs a second correction | Undershoot, often from a hesitant start | SPIDERSHOT |
| Several frames pass between a kill and the next movement | Hesitation while choosing the next target | TARGET SWITCH |
| The crosshair trails a moving target by a steady gap | Tracking lag | TRACKING + REACTIVE TRACK |
| Small shakes while you hold on a target | Micro-precision | PRECISION |
Each drill opens from its mode link: Flick, Spidershot, Target Switch, Tracking, Reactive Track and Precision. Look for the same pattern in two or three separate clips before you change your training around it. One run can fail for reasons that have nothing to do with skill.
Cut the moment and make a GIF
You rarely need the whole run. Pick the two to five seconds around the mistake. A GIF plays in a chat message without a click and without a video player, which makes it a good format for this. Grabivo's video to GIF converter does the cut in the browser. You add the recording, pause the preview at the right frame and press "Use the paused moment" to set the start. Then you choose a length of up to 15 seconds, a width of 320, 480 or 640 pixels and a frame rate of 8, 10 or 15. The recording is read in the tab and is not uploaded.
A GIF stores every frame as a full picture with at most 256 colors, so a few seconds can weigh several megabytes. If the result is too big to post, shorten the slice first, then lower the width, then the frame rate. The converter suggests 480 pixels at 10 frames per second as a starting point. For a fast flick, cut length before you cut frame rate, because a low rate drops the frames you are trying to look at.
A GIF has no sound. If sound matters, such as a footstep you reacted to, share the video itself.
Post it with something to compare
A clip on its own gets vague replies. Add the mode, the score and your sensitivity as eDPI or cm/360, so another player can compare it with their own numbers. The sensitivity guide shows how to work out both. Then say what you think went wrong, so people can agree or point at something you missed.