Best ZmjjKK VALORANT Settings for Crosshair & Aim (2026)
ZmjjKK's recorded VALORANT setup for Patch 13.10: 800 DPI with 0.395 sensitivity, the current crosshair profile code and import steps, video and minimap values, plus what to change on weaker hardware. Every value is dated, with the older 1600 DPI snapshot flagged as obsolete.
VALORANT moved to Unreal Engine 5 with Patch 11.02 on July 29, 2025, but it still runs on Direct3D 11 and offers no DX12 or Vulkan switch in the menu. That makes frame time unusually dependent on your CPU: most dips come from draw submission and simulation, not from the graphics card. ZmjjKK's recorded setup is a useful reference because it is built around that bottleneck — low material detail, no cast shadows, a stretched 4:3 image — and because every value below carries a date instead of pretending to be permanent.
1. Quick Settings Cheat Sheet
The profile was recorded on August 31, 2026 and checked again on October 25, 2026. Treat it as a snapshot, not a permanent statement about what he runs today.
2. Understanding VALORANT's Performance
Two bottlenecks decide how this game feels. The first is the renderer: Unreal Engine 5 arrived in Patch 11.02 on July 29, 2025, yet Direct3D 11 remains the only supported API, so there is no DX12 or Vulkan path to test and no reason to look for one in the settings menu. The second is the processor. VALORANT is frequently CPU-bound, which is why cutting resolution often returns less frame rate than the pixel count suggests.
- Draw calls and ability effects dominate. Smoke, molly and wall effects multiply the work submitted every frame, so fights near multiple utilities are where frame time spikes.
- VRAM is not the main limit. The official minimum is 1 GB of VRAM with 4 GB of system RAM, and Low textures keep you near that floor.
- Storage and Windows version matter. The install needs 35 GB, and Windows 11 additionally requires TPM 2.0 and UEFI Secure Boot.
- Shadows and bloom cost twice. They add GPU work and they change what you can see, so they are visibility settings as much as performance settings.
These are the vendor's reference builds, not tested benchmarks. Use them to place your own machine, then adjust one step at a time.
3. Best Video / Graphics Settings
The values below are his recorded profile, not a preset that transfers to every PC. If your graphics card is older than a GTX 1050 Ti, read the third column first: it tells you where to deviate before you copy anything else.
Two entries are easy to misread. Bloom stays On in his profile, and Improve Clarity stays On even though both cost GPU time. The first keeps ability effects legible, the second fights the blur of a low internal resolution, so neither should be switched off reflexively.
Pro Tip: Cast Shadows Off is the biggest visibility change in this table, not a performance afterthought. Shadow maps are what let a player silhouette vanish into a doorway. Turning them off costs very little image quality and removes a class of frame-time spikes when several agents use abilities at once.
4. Key Setting Deep Dives
4:3 Stretched Resolution: What Fill Actually Does
Fill stretches a 4:3 render across a 16:9 panel. The field of view stays fixed at 103 degrees and hitboxes do not change; only the HUD, crosshair and weapon model stretch with the image. That is the part most copied advice gets wrong: a wider-looking enemy is a wider-looking image, not a wider target.
The official guidance still recommends 16:9, and there is no competitive advantage to 4:3 beyond personal preference. What 4:3 does give you is a larger apparent target and, on some setups, slightly better visibility — lowering the resolution to make targets stand out is exactly the trade he is making.
Frame rate is the weaker argument. Because the game is often CPU-bound, the gain from 1280×960 is usually smaller than the roughly 40% pixel reduction implies. Measure it on your own machine before you commit to the blur.
If you are on a 1080p monitor with a mid-range card, native 16:9 is the safer default. Pick 1280×960 only if you prefer the stretched image and can live with softer edges, and do not expect the resolution change alone to fix a CPU-limited frame rate.
Anti-Aliasing at 1280×960: MSAA 4x vs Off
He runs MSAA 4x, which cuts against the usual "turn everything off" advice. At 1280×960 the edges of railings, wires and thin geometry crawl badly, and a crawling edge reads as movement at the corner of your eye. MSAA resolves geometric edges without blurring the entire frame, which matters when the image is already being upscaled.
The cost is fill rate. MSAA multiplies edge samples, so it is the first graphics option to touch on a minimum-spec GPU. Lower it before you touch texture quality: textures at Low cost you almost nothing in target clarity, while anti-aliasing at 4x can cost a noticeable slice of frame time on weak hardware.
Anisotropic filtering at 8x is a separate decision. It sharpens angled floor and wall textures at distance, which helps you read surfaces, and it is cheap on most modern cards — leave it alone unless you are chasing every last frame on integrated graphics.
Improve Clarity, Bloom and Experimental Sharpening
Improve Clarity is a sharpening pass, and it exists to fix the specific problem of a 1280×960 image on a 1080p panel. Keep it On. Older snapshots of his profile list it as Off; the newer record has it On, and that is the value used here, so a list that says otherwise predates the latest check.
Bloom adds glow around bright sources. It is not free, but it makes ability effects and muzzle flash easier to place, which is why he leaves it on while cutting almost everything else.
Experimental Sharpening stays Off. Running two sharpening passes on a low-resolution image produces halos around edges and makes thin targets harder, not easier, to pick out. If the image looks oversharpened, turn Clarity down before you touch anything else.
5. Controls, Audio & Visibility
Start with the arithmetic: eDPI is mouse DPI multiplied by in-game sensitivity. At 800 DPI and 0.395, that is 316 eDPI. The number exists so you can compare setups across different DPI values — it is not a target to hit.
316 eDPI sits at the top of the common professional range of 200–300, where the average is around 260, and inside the wider 200–400 band. It is not a value to copy blindly: desk depth, mouse weight, grip and posture all change how the same eDPI feels.
Watch the dates and the older numbers. An earlier snapshot recorded 1600 DPI at 0.1 sensitivity for 160 eDPI, and a 2024 record showed 800 DPI at 0.28 for 224 eDPI. Both predate the current profile and should not be mixed with it — if you convert 316 eDPI to 1600 DPI, the correct in-game value is about 0.1975, not 0.1.
The minimap is the one part of this profile that rewards a bigger value rather than a smaller one. A size near maximum is only useful if you actually glance at it between engagements; if it covers your peripheral vision, drop it a notch and keep the vision cones on.
6. Crosshair Profile Code and Import
His current profile code is below. Import it through the official in-game importer — no third-party tool, no config file, no file edits.
- Open Settings, then the Crosshair tab.
- Click the downward-arrow icon next to Crosshair Profile.
- Choose Import Profile Code.
- Paste the full string into the field and confirm.
- Name the profile and save it.
- Test it against a bright wall and a dark corner before you queue.
A compliance note before you go further: his public profile lists no launch options and no documented config edits, and you should not add any. VALORANT runs Vanguard, a kernel-level anti-cheat that starts with Windows and requires a reboot if it is disabled. Editing game files or running unknown "optimization" utilities can trigger it or breach the terms of service, and there is no performance setting in this guide that requires either.
He also rotates crosshairs when his form dips, so a single code is a snapshot rather than a permanent signature. Import it, live with it for a week, and change it if your eye keeps losing it.
7. Latency & Input Optimization
Reflex appears as On + Boost in an older snapshot of his profile and is missing from the newer listing, which may mean the row was dropped from the record rather than the setting being changed. Enable it if your GPU supports it; on a card without Reflex support the option will not appear, and that is not a problem to solve.
Do not enable VSync to fix tearing. Cap your frame rate slightly below your refresh rate instead, which keeps frame pacing stable without adding a queued frame. A 4000 Hz polling rate is also not a free upgrade: it only helps if your mouse and its receiver are rated for it, and it is pointless on a 60 Hz display.
8. System & Driver Tweaks
These are low-risk and reversible. Note your current values before changing anything, and keep a restore point if you are editing driver-level settings.
- Install the GPU driver cleanly. Use the vendor installer's clean-install option after removing the old driver, so no leftover control-panel profile overrides your in-game choices.
- Set Windows to High Performance. The balanced plan parks cores aggressively, which shows up as frame-time variance in a CPU-bound game.
- Confirm the refresh rate in Windows. The display often defaults to 60 Hz after a driver update, which silently caps everything above.
- Let shader compilation finish. The first match on a new map or patch stutters while shaders build; play a short warm-up before you judge a setting.
- Keep at least 35 GB free and close overlays. The install needs 35 GB, and capture or overlay tools add hooks that cost frame time.
9. How to Test Your Settings
- Pick one repeatable scene — a range session or a custom lobby with bots — and use it for every test.
- Record your current average frame rate and 1% low, the average of the slowest 1% of frames, before changing anything.
- Drop every graphics setting to its lowest value and note the frame rate ceiling your CPU allows.
- Raise one setting at a time, starting with the ones that affect visibility: shadows, then anti-aliasing, then bloom.
- Keep a change only if it holds across three runs; a single good match is noise.
Match your target to your display: 60 Hz needs a stable 60 FPS, 144 Hz wants 120–144, and 240 Hz wants 200 or more. A stable lower number beats a higher average with bad frame pacing every time.
